@archme/cli 0.5.4 → 0.6.0

package/dist/cli.js

@@ -12173,6 +12173,16 @@ var init_storyNaming = __esm({
 });
 
 // ../shared/scanPrompts.ts
+function buildStoryCoverageGate(opts) {
+  const preWrite = opts.noChangeSignal ? `
+
+**Decide before you write.** A write is durable once \`update_architecture\` returns; \`report_no_change\` retracts nothing and is rejected after a diff-phase write. The only correction is another call removing what you added \u2014 \`componentUpdates: [{ remove: ["<id>"] }]\`, plus any connection for it.` : "";
+  return `**A component may only be added if it is part of a user story.** When code sits below the altitude any story describes, leave the component out.
+
+**Never invent a user story to cover a component** if the user story is not true or architecturally significant. A contrived user story is permanent and degrades the graph. Omitting irrelevant user stories is desired behavior, not a concession: the graph holds what is architecturally relevant, not everything the code contains, and it is up to you to be a good steward of it.
+
+**After researching, if still in doubt about architectural relevance or significance, err on the side of no changes.**${preWrite}`;
+}
 function buildFormatRefStories(opts) {
   const draftBlock = opts.persistentDrafts ? FORMAT_REF_DRAFT_STORIES_BLOCK : "";
   const uncoveredSubFlowRule = opts.persistentDrafts ? CROSS_REF_UNCOVERED_DRAFT_STUB : CROSS_REF_UNCOVERED_REAL_STORY;
@@ -12241,10 +12251,25 @@ storyUpdates targeting:
   - Remove: storyUpdates: [{remove: ["old_story"]}]
   - Combined: storyUpdates: [{under: "auth", add: [{id: "new_flow", ...}], remove: ["old_flow"]}]`;
 }
-var ANCHOR_RULES, ANCHOR_DISCOVERY, ANCHOR_VERIFICATION, FORMAT_REF_COMPONENTS, FORMAT_REF_CONNECTIONS, FORMAT_REF_DRAFT_STORIES_BLOCK, CROSS_REF_UNCOVERED_DRAFT_STUB, CROSS_REF_UNCOVERED_REAL_STORY, FORMAT_REF_STORIES;
+var BUILD_METHODOLOGY, ANCHOR_RULES, ANCHOR_DISCOVERY, ANCHOR_VERIFICATION, FORMAT_REF_COMPONENTS, FORMAT_REF_CONNECTIONS, FORMAT_REF_DRAFT_STORIES_BLOCK, CROSS_REF_UNCOVERED_DRAFT_STUB, CROSS_REF_UNCOVERED_REAL_STORY, FORMAT_REF_STORIES;
 var init_scanPrompts = __esm({
   "../shared/scanPrompts.ts"() {
     init_storyNaming();
+    BUILD_METHODOLOGY = `You are a build sub-agent. You are part of a multi-agent system that builds a comprehensive visual architecture of a codebase \u2014 components, connections, and user stories that trace data flow end-to-end. Your role is to translate research findings into actual architecture: creating components backed by real code references, wiring connections between them, and building story sequence diagrams that trace how data flows through the system.
+
+# Rules
+
+- Only build what the research findings and code evidence support. Do not invent components, connections, or user stories that aren't backed by real code. If findings are insufficient, flag gaps rather than guessing.
+- Every connection MUST have a non-empty method
+- Keep component hierarchies nested (e.g., backend > api > routes)
+- Use at: "parent" to target nested scopes for connectionUpdates
+- External services must be created as components with \`role: "external"\` (and \`kind: "human"\` for human actors), then referenced by dot-path in sequences like any other component
+- Small utility modules are implementation details \u2014 omit unless architecturally significant
+- Components must exist before non-draft stories can reference them. Add components first, then wire stories.
+
+# Story Coverage Gate
+
+${buildStoryCoverageGate({ noChangeSignal: false })}`;
     ANCHOR_RULES = `Every component must have either \`anchors\` (non-empty array) or \`unanchored: true\`. No bare components.
 
 Pick the anchor kind based on how the component lives in code:
@@ -16107,7 +16132,9 @@ Whenever you perform multiple independent operations, invoke all relevant tools
 1. ${step1}
 2. Inspect the diff below and, if useful, read individual files from the local clone for additional context.
 3. **Decide scope.** If the change touches multiple stories or areas, dispatch sub-agents (see Sub-Agent Strategy below) to research and update them in parallel. For small, focused changes you can handle everything directly \u2014 use your judgement.
-4. Call \`update_architecture\` (or have build sub-agents call it) with the minimal additive changes that reflect the diff \u2014 components, connections, AND stories, not components alone. Update every affected story you confirmed above, and add a story via \`storyUpdates\` for any new user-facing behavior or journey (endpoint flow, UI feature, background workflow) that passes the granularity gate in New Story Guidance below. ${STORY_DESCRIPTION_EDIT_RULE} **Tag each write's \`phase\` (see Provenance below).**
+4. Call \`update_architecture\` (or have build sub-agents call it) with the minimal additive changes that reflect the diff \u2014 components, connections, AND stories, never components alone \u2014 see the Story Coverage Gate below **before** composing the payload: a diff that changes no story means no call at all. Update every affected story you confirmed above, and add a story via \`storyUpdates\` for any new user-facing behavior or journey (endpoint flow, UI feature, background workflow) that passes the granularity gate in New Story Guidance below. ${STORY_DESCRIPTION_EDIT_RULE} **Tag each write's \`phase\` (see Provenance below).**
+
+${STORY_COVERAGE_GATE}
 
 ${NEW_STORY_GUIDANCE}
 
@@ -17230,7 +17257,7 @@ ${signal} received, shutting down`);
   process.on("SIGINT", () => shutdown("SIGINT"));
   process.on("SIGTERM", () => shutdown("SIGTERM"));
 }
-var HEARTBEAT_INTERVAL_MS, CLAUDE_TIMEOUT_MS, CLAUDE_LARGE_DIFF_TIMEOUT_MS, SAFETY_SWEEP_MS, LOG_STDOUT_CAP_BYTES, LOG_STDERR_CAP_BYTES, PRE_SPAWN_TOKEN_MIN_LIFETIME_MS, SUPABASE_URL, SUPABASE_ANON_KEY, ARCHME_DAEMON_CLIENT_ID, ARCHME_MCP_BASE_URL, CLONE_BASE_DIR, DAEMON_ID, LEASE_SECONDS, inFlight, cancelled, killReasons, activeCleanups, cloneMutex, shuttingDown, daemonVersion, pauseUntilMs, resumeTimer, currentSched, MAX_CONCURRENT_JOBS, ctxByJob, deviceByJob, DEFAULT_CLONE_BASE_DIR, INLINE_PATCH_BYTE_CAP, GIT_SHA_RE, CURATOR_PREAMBLE, CORE_PRINCIPLES, NEW_STORY_GUIDANCE, STORY_DESCRIPTION_EDIT_RULE, PHASE_GUIDANCE, BASE_RULES, DIFF_RULES, finite, channelSeq, MultipleAccountsError, __testDispatch;
+var HEARTBEAT_INTERVAL_MS, CLAUDE_TIMEOUT_MS, CLAUDE_LARGE_DIFF_TIMEOUT_MS, SAFETY_SWEEP_MS, LOG_STDOUT_CAP_BYTES, LOG_STDERR_CAP_BYTES, PRE_SPAWN_TOKEN_MIN_LIFETIME_MS, SUPABASE_URL, SUPABASE_ANON_KEY, ARCHME_DAEMON_CLIENT_ID, ARCHME_MCP_BASE_URL, CLONE_BASE_DIR, DAEMON_ID, LEASE_SECONDS, inFlight, cancelled, killReasons, activeCleanups, cloneMutex, shuttingDown, daemonVersion, pauseUntilMs, resumeTimer, currentSched, MAX_CONCURRENT_JOBS, ctxByJob, deviceByJob, DEFAULT_CLONE_BASE_DIR, INLINE_PATCH_BYTE_CAP, GIT_SHA_RE, CURATOR_PREAMBLE, CORE_PRINCIPLES, STORY_COVERAGE_GATE, NEW_STORY_GUIDANCE, STORY_DESCRIPTION_EDIT_RULE, PHASE_GUIDANCE, BASE_RULES, DIFF_RULES, finite, channelSeq, MultipleAccountsError, __testDispatch;
 var init_run = __esm({
   "src/daemon/run.ts"() {
     "use strict";
@@ -17297,6 +17324,9 @@ You are curating the architecture diagram, not just transcribing the change. The
 
 - **Code is the source of truth.** Docs, comments, READMEs, commit messages, and PR descriptions can point you at *where to look*, but every architectural claim must come from reading the actual code paths end-to-end. Do not spot-check or paraphrase what a doc says \u2014 verify the behavior by tracing the code itself. If the doc and the code disagree, the code wins; if you cannot find the code, treat the claim as not-present.
 - **Each edit lands in a diff view.** The user reviews every change in a diff, where a capitalized letter or a reworded sentence shows up just as loudly as a new component. Keep that lens on as you work: each edit is going to land in someone's review queue. Aim for changes that are worth their visual weight \u2014 if the meaning has not shifted, the words probably should not either. This is judgement, not a rule; missing a real change to avoid a small one is the worse failure.`;
+    STORY_COVERAGE_GATE = `## Story Coverage Gate
+
+${buildStoryCoverageGate({ noChangeSignal: true })}`;
     NEW_STORY_GUIDANCE = `## New Story Guidance
 ${STORY_GRANULARITY_GUIDANCE}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@archme/cli",
-  "version": "0.5.4",
+  "version": "0.6.0",
   "description": "Map your codebase into a living architecture diagram: run `archme init` in a repo to scan it, `archme daemon start` to keep it current on every commit.",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",