Share repair histories while debug artifacts wait for indices
This commit is contained in:
@@ -49,6 +49,8 @@ used to interpret response references. Each interaction retains its available
|
||||
prepared request, response, and failure evidence. Ledger mapping preserves empty
|
||||
proposed and applied replacements and distinguishes unavailable candidates from
|
||||
interrupted work.
|
||||
While final proposal indices are pending, repair request snapshots share their
|
||||
unchanged message prefix. Each written request contains its full history.
|
||||
|
||||
The sink groups concurrent write failures by role, artifact operation, and cause.
|
||||
Warnings report the count and an affected path. The writer still attempts other
|
||||
|
||||
@@ -397,6 +397,12 @@ proposal, validation, and application as the existing independent views.
|
||||
|
||||
### R12 — Avoid Queuing Full Repair Histories in Debug Capture (P3)
|
||||
|
||||
**Complete.** Pending repair requests share their immutable history
|
||||
prefixes. Each write retains the exact request and final proposal index.
|
||||
An ordered collector test compares two real coordinator snapshots with the
|
||||
written requests, checks ledger paths, and verifies that a later request
|
||||
still writes after a capture failure. Repeated race checks passed.
|
||||
|
||||
**Affected plan:** Stages 3, 14, 16, and 18.
|
||||
|
||||
**Evidence:** [Prepared capture](../../internal/framework/llm/adapter.go#L151)
|
||||
|
||||
Reference in New Issue
Block a user