Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
fix(map): refuse ignored inputs before stamping main [C7,A1]
Corey Olsonbb1175d4d4a4
diff --git a/docs/api.md b/docs/api.mdindex 4223af7d..bca33720 100644--- a/docs/api.md+++ b/docs/api.md@@ -75,7 +75,7 @@ For example: `flow: review wait average 61 min (1 measured; > 60 min); bottlenec`merged <id> <commit>` records only a commit reachable from the primary checkout's branch that contains the item's submitted commit or has the same stable patch id as the item's change from its claim base. Other commits are refused with `NOT_MERGED`; `--note "why"` records an exceptional receipt and keeps the note in that item's `merged` event.-`map --json`, `map <module or function> --json`, and `map --for <item> --json` return the same envelope: `main` is the scanned primary-main commit and `map` is the rendered overview, card, or bounded item slice. Ordinary text output is that same map text. The scanner reports unobserved effects as `not detected`; the map is source context, not proof that an effect cannot occur.+`map --json`, `map <module or function> --json`, and `map --for <item> --json` return the same envelope: `main` is the scanned primary-main commit and `map` is the rendered overview, card, or bounded item slice. Ordinary text output is that same map text. Fresh scans require `src/`, `bin/`, and `test/` to match committed main: changed, untracked, and ignored entries in those directories refuse the scan. Ignore rules alone do not refuse it. A cached committed map does not incorporate later working-tree changes. The scanner reports unobserved effects as `not detected`; the map is source context, not proof that an effect cannot occur.<!-- api-command-shapes:start -->`status --json` and local API state carry `ruleCounts`: `approved`, `gated` (approved rows naming a gate), `ungated`, `proven`, `unproven`, and `contradicted`. Proof requires a green configured full-gate receipt on the current trunk whose supported test selection includes the row's test files. Opaque or unsupported coverage remains unproven. Contradicted counts approved rows whose gate files failed on the trunk in the last seven days; it is independent of proven, so a row can count in both after a later green. The API refreshes this window when evidence ages out, even without a board move.diff --git a/src/code-map.js b/src/code-map.jsindex 1f3f182d..9c0af050 100644--- a/src/code-map.js+++ b/src/code-map.js@@ -324,7 +324,7 @@ function requireSourcePin(root, commit) {|| gitText(root, ['rev-parse', 'main']) !== commit) {throw new Error('the primary source checkout is not at the requested main commit');}- if (gitText(root, ['status', '--porcelain', '--untracked-files=all', '--', 'src', 'bin', 'test'])) {+ if (gitText(root, ['status', '--porcelain', '--untracked-files=all', '--ignored=matching', '--', 'src', 'bin', 'test'])) {throw new Error('src/, bin/ or test/ differs from the committed main source');}}