audit: claude-shakedown 2026-07-09 dossier + San execution prompt #6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "audit/claude-shakedown-2026-07-09"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Branch:
audit/claude-shakedown-2026-07-09→mainReviewer: Jigo (per PR-2 Q9 precedent: San preflight, Jigo review, J7 gate)
Files:
documents/audits/claude-shakedown-2026-07-09.md(new),prompts/san-execute-shakedown.md(new). No canonical docs modified — all fixes land via the Lane A hardening PR that San will open.What this is
The external Claude shakedown deliverable per
prompts/claude-shakedown.md, plus the operational prompt that turns its accepted findings into kanban cards.Dossier headline (full detail in §4.3)
0.0.0.0:8000— an unmade stop/keep decision.board-schema.mdlacksforbidden_paths+report_back_channel, so external-workers §4 is structurally unenforceable; no transition rules despite wolf-solo move authority.:6380absent from both the spec component table and the runtime-state port map while P8 works its ACLs.Plus: answers to the 9 PR-2 open questions (5 settled from docs, 3 need J7, 1 answered by precedent), reconstruction of the 4 deferred Jigo minors (3 should land pre-Sprint 0), 7 ranked recommendations, and §4.7 false-negative accounting (no approval bypasses, no committed secrets, no second control plane, no paused-component allocation found).
Merge gates
prompts/san-execute-shakedown.mdagainst SanNote on
documents/New top-level tree per shakedown §0 ("audit is ephemeral until promoted") — deliberately outside canonical
specs//docs/. If you'd rather not introduce it,docs/audits/works with a one-word edit; ADR-0003 boundary purists may prefer keeping ephemera out ofdocs/though.