vibe-coding-master 0.6.10 → 0.6.12
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.
|
@@ -671,7 +671,6 @@ export function createSessionService(deps) {
|
|
|
671
671
|
...current,
|
|
672
672
|
claudeSessionId: sessionIdentity.claudeSessionId,
|
|
673
673
|
transcriptPath: sessionIdentity.transcriptPath,
|
|
674
|
-
cwd: input.cwd ?? current.cwd,
|
|
675
674
|
activityStatus: isTurnEnd ? "idle" : isCompact ? current.activityStatus : "running",
|
|
676
675
|
lastHookEventAt: timestamp,
|
|
677
676
|
lastTurnEndedAt: isTurnEnd ? timestamp : current.lastTurnEndedAt,
|
|
@@ -797,7 +796,6 @@ export function createSessionService(deps) {
|
|
|
797
796
|
...current,
|
|
798
797
|
claudeSessionId: sessionIdentity.claudeSessionId,
|
|
799
798
|
transcriptPath: sessionIdentity.transcriptPath,
|
|
800
|
-
cwd: input.cwd ?? current.cwd,
|
|
801
799
|
activityStatus: isTurnEnd ? "idle" : isCompact ? current.activityStatus : "running",
|
|
802
800
|
lastHookEventAt: timestamp,
|
|
803
801
|
lastTurnEndedAt: isTurnEnd ? timestamp : current.lastTurnEndedAt,
|
|
@@ -17,6 +17,17 @@ export function renderProjectManagerHarnessRules() {
|
|
|
17
17
|
- Do not overload the user with file names, function names, logs, or implementation details unless they are necessary for the user's decision.
|
|
18
18
|
- Do not oversimplify findings. Preserve the cause, impact, risk, and required next step so the user can understand why the flow is blocked or why approval is needed.
|
|
19
19
|
|
|
20
|
+
### PM Managed Mode
|
|
21
|
+
|
|
22
|
+
PM Managed Mode applies only when the user explicitly asks to complete the current task in this mode.
|
|
23
|
+
|
|
24
|
+
- PM must drive the task to completion according to the user's request.
|
|
25
|
+
- PM must not delay, narrow, reinterpret, skip, or deviate from the requested task without explicit user approval.
|
|
26
|
+
- Questions about how to complete the task are managed inside the VCM flow. This includes workload, phasing, implementation approach, module boundaries, dependencies, internal services, permissions, validation, debugging, replanning, and review fixes.
|
|
27
|
+
- Simple or technical execution questions should be routed to Architect or the responsible role for decision.
|
|
28
|
+
- Ask the user only when the task cannot proceed without user intent or real-world authorization: unclear or conflicting requirements, required external accounts/secrets/test environments/data access, real cost, production permission, sensitive data access, durable-doc conflict, or a proven need to change the requested outcome.
|
|
29
|
+
- When PM asks the user, the flow must stop and wait for the user's explicit instruction before continuing.
|
|
30
|
+
|
|
20
31
|
### Routing
|
|
21
32
|
|
|
22
33
|
- Use the routes defined in \`CLAUDE.md\`.
|