vibe-coding-master 0.8.9 → 0.8.11

package/dist/backend/templates/harness/architect-agent.js

@@ -141,7 +141,7 @@ ${renderRoleMemoryRules("architect")}
 #### Code Scaffolding
 
 - Use the Agent tool to invoke \`vcm-architect-scaffold-worker\` in the foreground after the plan and Scaffold Manifest are complete. Give it the exact plan path and require it to return before this Architect turn continues.
-- Use one scaffold worker. Do not run it in the background or end the Architect turn while it is active.
+- Run at most one scaffold worker at a time. Do not run it in the background or end the Architect turn while it is active. If its report leaves scaffold items unfinished, verify the completed work and invoke another foreground scaffold worker with the previous report and exact remaining items. Continue until every item is complete or report the concrete failure to project-manager.
 - Review the worker commit, actual diff, callable surfaces, marker placement, ledger reconciliation, and L0 results yourself. Architect owns every final scaffold claim and must correct any worker error before marking planning complete.
 - Create or update only the minimum module/file scaffolding needed to make boundaries, callable surfaces, and placeholders unambiguous. Minimum limits depth (no business implementation), never breadth: every \`create\`, \`change\`, and \`delete\` item must be scaffolded.
 - When a required configuration, package manifest, or build-definition change cannot safely contain a \`VCM:CODE\` marker, complete and commit it directly as Architect-owned scaffold work. Record it in the Module/File Plan and Scaffold Build Evidence. Do not add it to the Scaffold Manifest.

package/dist/backend/templates/harness/vcm-propose-memory-skill.js

@@ -12,6 +12,11 @@ planning-session memory candidate and provides an exact path.
 - If VCM did not provide a path, do not create a proposal.
 - Propose only verified, durable, reusable project knowledge supported by task
   evidence.
+- Before proposing an add or update, check current durable documents, Harness
+  rules and skills, and the tool's help, usage, or error output. Cite the checked
+  source in Evidence. Do not duplicate existing knowledge in memory; propose
+  \`durable-doc\` only when the existing document is wrong or incomplete, or use
+  \`memory-reference\` when roles need a short pointer across tasks.
 - Target shared project knowledge to \`shared\`. Target knowledge used only by
   the current role to \`current-role\`.
 - For every add or update, explain why the memory is necessary, what future

package/dist/shared/types/session.js

@@ -23,16 +23,9 @@ export const CLAUDE_MODEL_OPTIONS = [
         source: "claude",
         available: true
     },
-    {
-        value: "claude-fable-5-1",
-        label: "Fable 5.1",
-        description: "Pinned Claude Fable 5.1",
-        source: "claude",
-        available: true
-    },
     {
         value: "fable",
-        label: "Fable Alias",
+        label: "Fable",
         description: "Claude Code provider-selected Fable",
         source: "claude",
         available: true
@@ -44,13 +37,6 @@ export const CLAUDE_MODEL_OPTIONS = [
         source: "claude",
         available: true
     },
-    {
-        value: "claude-opus-4-8",
-        label: "Opus 4.8",
-        description: "Pinned Claude Opus 4.8",
-        source: "claude",
-        available: true
-    },
     {
         value: "sonnet",
         label: "Sonnet",