vibe-coding-master 0.6.15 → 0.6.17

package/dist/backend/services/harness-service.js

@@ -1656,7 +1656,7 @@ Required work:
 - Run .ai/tools/generate-public-surface from the target task worktree after module-index.json exists.
 - Add or update project-specific Project Context and Project Constraints in target CLAUDE.md above the VCM managed block.
 - Fill target docs/ARCHITECTURE.md with project-level module overview, responsibilities, relationships, dependency direction, project-wide constraints, and links to module-level architecture docs.
-- Create or update target module-level ARCHITECTURE.md files for clear module boundaries listed by module-index.json.
+- Create or update target module-level ARCHITECTURE.md files for clear non-root module boundaries with architectureDoc paths in module-index.json.
 - Fill target docs/TESTING.md with project-native validation levels, commands, validation selection rules, final-validation cleanup, test layout, integration/E2E case lists, generated-context freshness checks, and known testing gaps.
 - Review git status and git diff in the target task worktree.
 - Stage only allowed bootstrap harness changes and create a commit in the target task worktree.

package/dist/backend/templates/harness/vcm-harness-bootstrap-skill.js

@@ -17,7 +17,7 @@ This skill is an operating procedure. It does not replace the deterministic VCM
 1. Generate context when supported: run \`.ai/tools/generate-module-index\`, then run \`.ai/tools/generate-public-surface\` after \`module-index.json\` exists.
 2. Inspect the project:  read \`README.md\`, read \`CLAUDE.md\`, durable project docs, project manifests/config, source layout, tests, and existing validation commands.
 3. Fill project context: add or update non-managed project facts in \`CLAUDE.md\` above the VCM managed block.
-4. Fill durable docs: update \`docs/ARCHITECTURE.md\`, module-level \`ARCHITECTURE.md\` files, and \`docs/TESTING.md\` with detailed project-specific content.
+4. Fill durable docs: update \`docs/ARCHITECTURE.md\`, module-level \`ARCHITECTURE.md\` files for clear non-root module boundaries, and \`docs/TESTING.md\` with detailed project-specific content.
 5. Preserve user-authored content and VCM managed blocks.
 6. Review \`git status\` and \`git diff\`.
 7. Stage only allowed bootstrap harness changes and create a commit in the active task worktree.
@@ -29,7 +29,7 @@ This skill is an operating procedure. It does not replace the deterministic VCM
 - \`docs/ARCHITECTURE.md\`
 - \`docs/TESTING.md\`
 - \`docs/known-issues.md\` only for confirmed durable issues
-- module-level \`ARCHITECTURE.md\` files
+- module-level \`ARCHITECTURE.md\` files for clear non-root module boundaries
 - \`.ai/generated/module-index.json\`
 - \`.ai/generated/public-surface.json\`
 
@@ -55,7 +55,8 @@ This skill is an operating procedure. It does not replace the deterministic VCM
 
 ### Module-Level \`ARCHITECTURE.md\`
 
-- Create or update one module-level \`ARCHITECTURE.md\` for each clear module boundary.
+- Create or update one module-level \`ARCHITECTURE.md\` for each clear non-root module boundary with an \`architectureDoc\` path in \`.ai/generated/module-index.json\`.
+- Do not create a root-level \`ARCHITECTURE.md\` only because the root package exists.
 - Document module boundaries, responsibilities, allowed dependencies, important behavior, important public surface explanations, risks, and update triggers.
 - Keep complete public API listings in \`.ai/generated/public-surface.json\`; module docs should explain meaning and design intent, not duplicate the full generated index.