vibe-coding-master 0.4.4 → 0.4.6

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.
@@ -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-Bck3Mfz8.js"></script>
8
- <link rel="stylesheet" crossorigin href="/assets/index-12kW1cl6.css">
7
+ <script type="module" crossorigin src="/assets/index-CeiRFzg5.js"></script>
8
+ <link rel="stylesheet" crossorigin href="/assets/index-CYmBA_er.css">
9
9
  </head>
10
10
  <body>
11
11
  <div id="root"></div>
@@ -502,7 +502,7 @@ For `.gitignore`, VCM uses hash comments:
502
502
 
503
503
  VCM must preserve all user-authored content outside the managed block.
504
504
 
505
- Harness changes are applied only in the active task worktree. VCM refuses to run harness operations when that worktree has Git-visible changes, writes the harness update, stages the changed harness files, and immediately creates a harness commit. Review Diff shows the latest active task commit diff, not an unstaged worktree diff. If the review is wrong, the user can revert the commit, modify and commit a follow-up, or ask Harness Engineer to revise the harness.
505
+ Harness changes are applied only in the active task worktree. For deterministic fixed-harness updates, VCM refuses to run when that worktree has Git-visible changes, writes the harness update, stages the changed harness files, and immediately creates a harness commit. For AI bootstrap work, Harness Engineer runs in the active task worktree and creates its own commit; VCM tracks status and shows the latest active task commit diff for review.
506
506
 
507
507
  Role sessions get VCM behavior from `CLAUDE.md` and `.claude/agents/*.md`, not from a pasted startup context.
508
508
 
@@ -830,6 +830,9 @@ Project-scoped local files:
830
830
  .ai/vcm/bootstrap/session.json
831
831
  ```
832
832
 
833
+ Project-scoped tool sessions keep their durable state in the base repository,
834
+ but their execution cwd is the active task worktree.
835
+
833
836
  External Claude transcripts:
834
837
 
835
838
  ```text
@@ -405,10 +405,11 @@ VCM should run bootstrap through the project-scoped `harness-engineer` session,
405
405
  not through a separate temporary terminal or invisible background task:
406
406
 
407
407
  - run the deterministic fixed installer first
408
- - start or resume the `harness-engineer` role in the connected repository root
409
- - send a prompt that explicitly requires using `vcm-harness-bootstrap`
408
+ - start or resume the project-scoped `harness-engineer` role with execution cwd set to the active task worktree
409
+ - send a prompt that explicitly requires using `vcm-harness-bootstrap` and creating the bootstrap commit
410
410
  - persist the bootstrap run marker under `.ai/vcm/bootstrap/session.json`
411
411
  - mark the bootstrap run complete when the `harness-engineer` Stop hook arrives
412
+ - do not create the bootstrap commit in VCM; Harness Engineer owns that commit
412
413
 
413
414
  The UI should expose both stages: fixed install status and bootstrap completion
414
415
  status. A failed or disconnected Harness Engineer session should be restartable
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vibe-coding-master",
3
- "version": "0.4.4",
3
+ "version": "0.4.6",
4
4
  "description": "Local GUI session cockpit for Claude Code role sessions.",
5
5
  "type": "module",
6
6
  "files": [