vibe-coding-master 0.4.17 → 0.4.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/backend/api/translation-routes.js +12 -0
- package/dist/backend/gateway/gateway-service.js +0 -1
- package/dist/backend/services/task-service.js +23 -10
- package/dist/backend/services/translation-service.js +64 -11
- package/dist/backend/services/translation-worker-service.js +19 -2
- package/dist/backend/templates/harness/gate-review.js +1 -1
- package/dist-frontend/assets/{index-D0LBjl2L.css → index-D1LTJ-sY.css} +1 -1
- package/dist-frontend/assets/index-D3MQlBYf.js +95 -0
- package/dist-frontend/index.html +2 -2
- package/docs/gateway-design.md +3 -3
- package/docs/product-design.md +5 -5
- package/package.json +1 -1
- package/dist-frontend/assets/index-B79szIZT.js +0 -95
package/dist-frontend/index.html
CHANGED
|
@@ -4,8 +4,8 @@
|
|
|
4
4
|
<meta charset="UTF-8" />
|
|
5
5
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
6
6
|
<title>VibeCodingMaster</title>
|
|
7
|
-
<script type="module" crossorigin src="/assets/index-
|
|
8
|
-
<link rel="stylesheet" crossorigin href="/assets/index-
|
|
7
|
+
<script type="module" crossorigin src="/assets/index-D3MQlBYf.js"></script>
|
|
8
|
+
<link rel="stylesheet" crossorigin href="/assets/index-D1LTJ-sY.css">
|
|
9
9
|
</head>
|
|
10
10
|
<body>
|
|
11
11
|
<div id="root"></div>
|
package/docs/gateway-design.md
CHANGED
|
@@ -35,9 +35,9 @@ Product rules:
|
|
|
35
35
|
- VCM stores the latest PM reply for each task in local Gateway state. When
|
|
36
36
|
`/start` enables Gateway and the current task has a cached PM reply, Gateway
|
|
37
37
|
returns that reply immediately so the phone user sees the current task state.
|
|
38
|
-
-
|
|
39
|
-
|
|
40
|
-
|
|
38
|
+
- Gateway does not change the desktop `Pause alert sound` preference. The
|
|
39
|
+
desktop pause dialog remains a fixed local UI signal, and Weixin is the mobile
|
|
40
|
+
notification path.
|
|
41
41
|
- Gateway may push PM replies to Weixin whenever it is enabled, even when the PM
|
|
42
42
|
turn was started from the desktop UI rather than from Weixin.
|
|
43
43
|
- When translation is enabled, Chinese input is translated to English before it
|
package/docs/product-design.md
CHANGED
|
@@ -318,15 +318,15 @@ The old `Dirty: yes/no` label is not used. The UI uses `Working tree: clean` or
|
|
|
318
318
|
`Settings` contains:
|
|
319
319
|
|
|
320
320
|
- `Theme` button, cycling through `System`, `Light`, and `Dark`.
|
|
321
|
-
- `
|
|
322
|
-
- `Try alert` button, firing the
|
|
321
|
+
- `Pause alert sound` button, on by default, controlling only the audible pause reminder.
|
|
322
|
+
- `Try alert` button, firing the fixed pause alert dialog and, when sound is enabled, the alert sound for local verification.
|
|
323
323
|
- `Messages` button, opening a modal list of role messages.
|
|
324
324
|
- `Events` button, opening a modal list of runtime UI events for the current task.
|
|
325
325
|
|
|
326
326
|
The default theme mode is `System`, which follows the OS/browser color-scheme preference. The entire application chrome, sidebar, forms, modals, status badges, and workspace panels must support both light and dark rendering. Embedded terminals keep their terminal-native dark styling.
|
|
327
327
|
|
|
328
|
-
When
|
|
329
|
-
`Try alert` must work even when no flow has just stopped advancing so the user can verify browser
|
|
328
|
+
When a role flow stops advancing, VCM always shows the fixed in-app pause alert dialog. When `Pause alert sound` is on, VCM also plays a short, soft, two-note local chime. If the flow lasted less than 2 minutes, the chime plays 3 times, 1.4 seconds apart, and stops. If the flow lasted 2 minutes or longer, the chime repeats until the user confirms the dialog. The alert sound must reuse one browser audio context after user activation instead of creating a fresh context for each repeat, because Safari can block repeated timer-driven playback when every repeat looks like a new autoplay attempt.
|
|
329
|
+
`Try alert` must work even when no flow has just stopped advancing so the user can verify browser dialog and sound behavior.
|
|
330
330
|
Safari may still require the user to manually set `Safari > Website Settings > Auto-Play > Allow All Auto-Play`; Chrome is the recommended browser for reliable repeated alert sound.
|
|
331
331
|
|
|
332
332
|
There is no separate `Pause orchestration` or `Resume orchestration` control in the GUI. The current product model is one on/off toggle in the role console toolbar.
|
|
@@ -779,7 +779,7 @@ App-level settings:
|
|
|
779
779
|
Stored app-level settings include:
|
|
780
780
|
|
|
781
781
|
- UI theme mode: `system`, `light`, or `dark`
|
|
782
|
-
-
|
|
782
|
+
- pause alert sound preference
|
|
783
783
|
- Claude Code permission request handling preference
|
|
784
784
|
- global translation preferences
|
|
785
785
|
- recent repository paths
|