Reuse validation facts when attributing skipped edits

This commit is contained in:
2026-11-17 04:34:31 +00:00
parent ee1ac8fc89
commit cc0a420722
10 changed files with 172 additions and 55 deletions

View File

@@ -33,7 +33,9 @@ formats; [configuration](../config.md) owns settings; the
without affecting independent approvals.
7. Only fully approved proposals reach application. Corrections apply in
proposal-index order within their owning section. Existing replacement
policies and apply-time safety checks resolve stale conflicts.
policies and apply-time safety checks resolve stale conflicts. Skip
attribution uses available validation previews of the original text to
distinguish stale edits from defects in a proposal or repair response.
8. CLI encodes the final transcript and publishes active files through the
output session. `framework/processreport` builds one snapshot for YAML,
Markdown, and CLI totals. Debug evidence is captured separately when enabled.

View File

@@ -2,7 +2,7 @@
**Reviewed revision:** `e8c0708`
**Status:** Findings and remediation progress from review of the 20
**Status:** All fourteen findings addressed after review of the 20
[implementation stages](implementation.md) against the
[target roadmap](reliability-and-maintainability.md), including follow-up
audits of component interactions and algorithmic costs.
@@ -472,6 +472,11 @@ both initial and repair filtering, and an interrupted run with available origin.
### R14 — Reuse Original Applicability When Attributing Application Skips (P3)
**Complete.** Application still checks current text. Skip attribution
reuses known original applicability, and repair filtering indexes approved
operations once per affected unit. Tests distinguish stale conflicts from
original defects and verify attribution across multiple repairs.
**Affected plan:** Stages 8 and 17, item 3.
**Evidence:** [Application](../../internal/framework/proposals/apply.go#L59)