Preserve composition conflict claimant order
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Interface Contract Remediation Implementation Plan
|
||||
|
||||
Status: in progress. Stages 1–16 are complete; Stages 17–18 remain pending.
|
||||
Status: in progress. Stages 1–17 are complete; Stage 18 remains pending.
|
||||
Baseline: `f6d54a094a2b5ada5748686620659399dce7ebf0`.
|
||||
Audience: a Luna coding agent executing the stages sequentially.
|
||||
|
||||
@@ -719,7 +719,10 @@ ordinary suite when buildable: `go test ./...`.
|
||||
## Stage 17 — Preserve Composition Conflict Ordering End To End
|
||||
|
||||
Finding 4. Owners: `canonicalDiagnostics`, composition diagnostic producers,
|
||||
root diagnostic conversion/rendering tests. Status: pending.
|
||||
root diagnostic conversion/rendering tests. Status: complete. Validation:
|
||||
`GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -run 'Diagnostic|Compose|Conflict' -count=1`,
|
||||
`GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test . -run 'TestFacadeCompositionConflictKeepsClaimantOrder' -count=1`,
|
||||
and `git diff --check` passed.
|
||||
|
||||
1. Implement the code-based ordering rule specified above. Verify every
|
||||
`CodeComposeConflict` producer; keep claimant order and leave single-related
|
||||
|
||||
Reference in New Issue
Block a user