vibe-coding-master 0.3.28 → 0.3.29
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/README.md +5 -5
- package/dist/backend/api/task-routes.js +2 -2
- package/dist/backend/gateway/gateway-service.js +24 -5
- package/dist/backend/services/claude-hook-service.js +43 -26
- package/dist/backend/services/message-service.js +9 -6
- package/dist/backend/services/project-service.js +2 -2
- package/dist/backend/services/session-service.js +44 -10
- package/dist/shared/constants.js +6 -2
- package/dist-frontend/assets/{index-x9I-bGUt.js → index-K34QFpWK.js} +29 -29
- package/dist-frontend/index.html +1 -1
- package/docs/gate-review-gates.md +13 -5
- package/docs/product-design.md +10 -9
- package/package.json +1 -1
package/dist-frontend/index.html
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
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-
|
|
7
|
+
<script type="module" crossorigin src="/assets/index-K34QFpWK.js"></script>
|
|
8
8
|
<link rel="stylesheet" crossorigin href="/assets/index-Cfum1Prr.css">
|
|
9
9
|
</head>
|
|
10
10
|
<body>
|
|
@@ -3,8 +3,9 @@
|
|
|
3
3
|
This document defines VCM Gate Review Gates.
|
|
4
4
|
|
|
5
5
|
Gate Review is an optional quality layer for complex tasks. It uses a fifth
|
|
6
|
-
role, `gate-reviewer`, powered by Claude Code. The role
|
|
7
|
-
|
|
6
|
+
VCM flow role, `gate-reviewer`, powered by Claude Code. The role uses the same
|
|
7
|
+
hook, Round, terminal, and translation path as the normal VCM roles, but it
|
|
8
|
+
does not participate in PM route-file dispatch.
|
|
8
9
|
|
|
9
10
|
## Gates
|
|
10
11
|
|
|
@@ -32,7 +33,8 @@ VCM owns:
|
|
|
32
33
|
- starting/resuming the project-scoped Gate Reviewer Claude Code session
|
|
33
34
|
- sending the gate prompt
|
|
34
35
|
- waiting for the report
|
|
35
|
-
-
|
|
36
|
+
- binding the project-scoped Gate Reviewer session to the current task for hook,
|
|
37
|
+
Round, and translation state
|
|
36
38
|
- sending the callback to PM
|
|
37
39
|
|
|
38
40
|
PM owns:
|
|
@@ -60,6 +62,11 @@ therefore name the current task and task worktree path explicitly. Prior
|
|
|
60
62
|
session memory can help orientation, but only current worktree evidence can
|
|
61
63
|
decide the gate.
|
|
62
64
|
|
|
65
|
+
When a task uses Gate Reviewer, VCM records the active task binding on the
|
|
66
|
+
project session. Hook events from the long-lived session are resolved through
|
|
67
|
+
that binding so Round state and translation output are written to the current
|
|
68
|
+
task.
|
|
69
|
+
|
|
63
70
|
Gate reports remain task-scoped:
|
|
64
71
|
|
|
65
72
|
```text
|
|
@@ -122,9 +129,10 @@ PM reaches gate
|
|
|
122
129
|
-> VCM checks global gate switch and task state
|
|
123
130
|
-> VCM starts or resumes project Gate Reviewer session
|
|
124
131
|
-> VCM sends short prompt with task/worktree/report paths
|
|
125
|
-
-> VCM
|
|
132
|
+
-> VCM binds Gate Reviewer to the current task
|
|
126
133
|
-> Gate Reviewer writes report
|
|
127
|
-
->
|
|
134
|
+
-> standard Claude hooks update Gate Reviewer activity/Round state
|
|
135
|
+
-> VCM validates report
|
|
128
136
|
-> VCM callbacks PM
|
|
129
137
|
-> PM continues or routes follow-up
|
|
130
138
|
```
|
package/docs/product-design.md
CHANGED
|
@@ -84,10 +84,11 @@ project-manager
|
|
|
84
84
|
|
|
85
85
|
### 4.1 Gate Review Gates
|
|
86
86
|
|
|
87
|
-
For complex tasks, VCM supports optional Gate Review Gates through
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
and
|
|
87
|
+
For complex tasks, VCM supports optional Gate Review Gates through a
|
|
88
|
+
`gate-reviewer` Claude Code role. Gate Reviewer is a VCM flow role with the same
|
|
89
|
+
hook, Round, terminal, and translation behavior as the core roles. Its session
|
|
90
|
+
is project-scoped and reusable across tasks, but each gate turn is bound to the
|
|
91
|
+
current task and task worktree so task evidence stays explicit.
|
|
91
92
|
|
|
92
93
|
```text
|
|
93
94
|
architect architecture plan
|
|
@@ -108,9 +109,9 @@ default to off.
|
|
|
108
109
|
|
|
109
110
|
When any gate is on, or when a Gate Reviewer session already exists, the task
|
|
110
111
|
workspace shows `Gate Reviewer` as a fifth terminal role. VCM sends a short gate
|
|
111
|
-
prompt into that session and
|
|
112
|
-
|
|
113
|
-
|
|
112
|
+
prompt into that project session and binds the session to the current task for
|
|
113
|
+
hooks, Round state, translation, and report polling. The role remains outside PM
|
|
114
|
+
route-file dispatch.
|
|
114
115
|
Architecture-plan findings return to architect, validation-adequacy findings
|
|
115
116
|
return to reviewer, and final-diff findings go to architect first for
|
|
116
117
|
assessment. Gate Reviewer role rules live in `.claude/agents/gate-reviewer.md`.
|
|
@@ -409,7 +410,7 @@ The split should stay close to 50/50 width. Both panes expand vertically to fill
|
|
|
409
410
|
|
|
410
411
|
## 8. Flow Pause Detection
|
|
411
412
|
|
|
412
|
-
VCM detects flow pauses from role hook events, not from terminal silence, message history, or pending route files. Claude Code roles report through `.claude/settings.json`;
|
|
413
|
+
VCM detects flow pauses from role hook events, not from terminal silence, message history, or pending route files. Claude Code VCM flow roles report through `.claude/settings.json`; Gate Reviewer follows the same hook path while VCM separately validates the assigned gate report.
|
|
413
414
|
|
|
414
415
|
Backend role state:
|
|
415
416
|
|
|
@@ -417,7 +418,7 @@ Backend role state:
|
|
|
417
418
|
- `Stop`: role becomes `idle` and records `lastTurnEndedAt`.
|
|
418
419
|
- `PostCompact`: refreshes role session metadata and records `lastCompactAt` without changing `running`/`idle`.
|
|
419
420
|
- `StopFailure`: first checks completion evidence. If the role already wrote an outgoing route file, VCM marks the role idle and dispatches normally. If not, VCM sends a recovery prompt to the same role without marking it idle.
|
|
420
|
-
- The role tab and flow pause state react to Claude Code hook events
|
|
421
|
+
- The role tab and flow pause state react to Claude Code hook events for all VCM flow roles, including Gate Reviewer.
|
|
421
422
|
|
|
422
423
|
Task-level Round state:
|
|
423
424
|
|