Give each correction repair branch its own outcome

This commit is contained in:
2026-11-16 14:36:07 +00:00
parent a0c70e8dce
commit e2710d869e
11 changed files with 309 additions and 233 deletions

View File

@@ -503,6 +503,22 @@ Check independent approved siblings, attempts/turn counts, actual branch
history and feedback, final-turn revalidation, and associated artifacts in
production coordination.
**Complete.** The runner checks repair capability before proposal dispatch.
Each proposal branch owns its history reference, attempt facts, and terminal
outcome. The section merges the returned evidence and approvals. Tests exercise
PromptKit coordination for independent histories, replacement prompts,
structural repair, final-turn revalidation, and retained siblings and
artifacts. The CLI build, full offline suite, and targeted race checks passed.
The three-correction CLI fixture used two repair branches and three repair
turns, with four revalidation requests and ten provider requests overall.
The default prompt sent 9,487, 13,385, and 9,483 repair request bytes in both
debug modes. Debug produced 39 files totaling 135,659 bytes in the observed
run, compared with zero files when disabled. The replacement prompt sent
6,303, 7,017, and 6,299 repair request bytes and produced 122,943 debug bytes
across 39 files. The fixture supplied no provider token usage. Temporary
measurement instrumentation was removed.
## Stage 15 — Give stage execution one commit boundary
Audit #14, #15 (evidence), #22 and #41 (failure facts).