feat(agents-audit): land deferred generate display behaviors (META-157) - #23
Merged
qmarcelle merged 1 commit intoJul 25, 2026
Conversation
Two CLI behaviors deferred from the 0.4.4 release (PR #19, gate G2) because they change exit-code semantics and were out of that release's approved scope: - `generate --check --dry-run` now fires the drift gate (exit 1) instead of the dry-run branch silently winning and exiting 0. The JSON projection is still printed under --dry-run. - `generate` now surfaces the pre-existing `invalidFileMoved` result field: when a previous workspace.json was invalid and moved aside, the CLI reports where and that manual evidence could not be recovered. Regression tests watched red against pristine main's cli.ts (2 failing / 9 passing), then green after the implementation (11/11). Recovered from the triple-preserved 2026-07-22 snapshot (preserve/vr-639-640-worktree-2026-07-22 tag + docs/audits/worktree-reconciliation/2026-07-22/preservation/tracked-changes.patch).
qmarcelle
deleted the
feature/meta-157-agents-audit-cli-land-the-two-deferred-generate-display
branch
July 25, 2026 08:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lands the two
agents-audit generateCLI display behaviors that were deliberately excluded from the 0.4.4 release (PR #19, governing decision G2) because they're a semantics change (exit code) outside that release's approved scope:--check+--dry-rundrift-gate ordering. Previously--dry-runwas checked first, sogenerate --check --dry-runprinted the projection and exited 0 even on drift. Now the drift gate fires first (exit 1, "manual evidence is untouched"), and the JSON projection is still printed under--dry-run.invalidFileMovedrecovery messaging. Thegenerateresult has carried aninvalidFileMovedfield since 0.4.3, but the CLI never surfaced it. Now, when a previous.agents/workspace.jsonwas invalid and moved aside, the CLI prints where it went and that its manual evidence wasn't recovered.Recovered from the triple-preserved snapshot of
feature/vr-639-640-spec-cli-prereqs(2026-07-22 reconciliation): tagpreserve/vr-639-640-worktree-2026-07-22, patchdocs/audits/worktree-reconciliation/2026-07-22/preservation/tracked-changes.patch(SHA-256 verified), applied fresh on top of currentmain— the stale branch itself is not being merged.Closes META-157.
Test plan
main'scli.ts(2 failed / 9 passed) before the implementationpnpm -r build✅pnpm -r typecheck✅pnpm -r test✅ — 277 passed, 0 failed (spec 36, cli 6, rules 173, agents-audit 62)packages/agents-audit/only — no@workspacejson/specsemantics touched