generated from john/python-template
Jim LancasterandCopilot App
626b5d4b10
Three gaps surfaced by implementing the 2026-08-23 review's recommendations. 1. Recommendations were never verified the way claims were. The report's fix for the error path leak would have stripped root-cause data from evidence records, because the review traced one consumer of AppError.message and missed that format_error_detail writes it to ExecutionAttempt.error_detail. Adds workflow step 9 (validate recommendations against consumers), a Blast Radius field on findings, and the worked example so the failure mode is concrete. 2. Fixes that sit between competing invariants were not flagged. The atomicity recommendation did not note that per-page durability and terminal-status atomicity pull in opposite directions, so the obvious simplification silently breaks multi-page durability. Recommendations must now name both invariants, the test guarding each, and the over-correction to avoid. 3. Severity could not express reachability. Two findings were latent behind a default setting and a single-instance deployment, which is a sequencing constraint: they must be fixed before the change that makes them live. Adds an explicit Reachability field with Live / Latent / Theoretical. Verified: meta contract guards and traceability tests pass. Co-authored-by: Copilot App <[email protected]>