Complete interface contract remediation

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Interface Contract Remediation Implementation Plan
 
-Status: in progress. Stages 1–17 are complete; Stage 18 remains pending.
+Status: implemented. Stages 1–18 are complete.
 Baseline: `f6d54a094a2b5ada5748686620659399dce7ebf0`.
 Audience: a Luna coding agent executing the stages sequentially.
 
@@ -743,7 +743,13 @@ root diagnostic regression.
 ## Stage 18 — Integrated Verification And Documentation
 
 Owners: integrated engine/facade, documentation, audit and plan status.
-Status: pending.
+Status: complete. Validation:
+`GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -run 'TestHistorySelectionMatchesDeepSidesOfAncestorShapeChange|TestMetadataFinalizationRegistersResolutionInventoryAndRoots|TestOverrideEqualReplacementStillAppearsInHistory|TestCLIHistoryEvidenceKeepsCheckpointsAndConditionalReconciliation|TestInheritanceHistoryPreservesCancellationAndSupersededDirective|TestRecordInheritanceHistoryPreservesChildIdentity|TestMappedSequenceHistoryReplacesWholeRecordsAndKeepsDisplacedEvidence|TestExplanationReplaysResolutionAdditionsAndOverlappingIntent|TestHistoryResolutionRetainsOriginalShapeAttributionBehindReplayGroup|TestExplainReplaysCLIResolutionContainersAndSafeHistoricalValues' -count=1`,
+`GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test . -run 'TestFacadeResolutionPresenceUsesDynamicEntryShape|TestPublicHistoryUsesResolutionShapeAttribution|TestPublicHistoricalPathsEnumerateContextualShapes|TestFacadeCompositionConflictKeepsClaimantOrder' -count=1`,
+`env GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off ./scripts/check.sh`,
+`env GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test -race ./...`,
+and `git diff --check` passed. The check script required gofmt alignment in
+`internal/engine/resolution_index_test.go`, which was applied mechanically.
 
 1. Run all deferred focused checks. Review representative ordinary and layered
    public loads for agreement among final configuration, entry/final presence,

docs/roadmap/interface-remediation.md

@@ -1,7 +1,7 @@
 # Interface Contract Remediation Roadmap
 
-Status: target settled, including shared history ownership; implementation has
-not begun.
+Status: implemented. The shared history owner and all four audit corrections
+are complete; validation is recorded in [implementation.md](implementation.md).
 Planning baseline: `1f64673` (v0.10.2 implementation plus documentation changes).
 
 This roadmap covers the four findings in the [interface audit](interfaces.md).
@@ -330,6 +330,5 @@ The selected common underlying model addresses both concerns. This accepts a
 larger internal refactor than a local shape-filtering fix.
 
 No significant open decision remains at roadmap level. Private representation,
-indexing, and helper choices belong in the implementation plan. This roadmap
-records future implementation ownership; it does not revise accepted ADRs or
-declare the model implemented.
+indexing, and helper choices are recorded in the completed implementation plan.
+This roadmap does not revise accepted ADRs.

docs/roadmap/interfaces.md

@@ -2,13 +2,14 @@
 
 Reviewed baseline: `01b08e76a3fecc22c4414437bfeaa07b4b7a85aa`.
 
-Status: four open findings. This is an audit record, not an implementation plan.
-No production code or repository tests were changed.
+Status: all four findings resolved. This remains an audit record, not an
+implementation plan; resolution evidence is recorded with each finding.
 
 The [interface remediation roadmap](interface-remediation.md) describes the
-settled target, required changes, and dependencies, including a shared internal
-history model for metadata history and explanation. Implementation remains pending.
-This audit retains the findings and reproduction evidence.
+settled target and its dependencies, including a shared internal history model
+for metadata history and explanation. The completed implementation and
+integrated validation are recorded in [implementation.md](implementation.md).
+This audit retains the findings and original reproduction evidence.
 
 ## Scope and evidence
 
@@ -36,7 +37,9 @@ existing contracts rather than introduce new API restrictions or guarantees.
 
 ## 1. Resolution presence queries confuse explicit keys with sequence indexes
 
-Priority: P2. Status: open.
+Priority: P2. Status: resolved. Evidence: `TestFacadeResolutionPresenceUsesDynamicEntryShape`,
+the engine resolution/provenance/default regressions, and the integrated checks
+recorded in [implementation.md](implementation.md).
 
 Relevant code:
 
@@ -82,7 +85,9 @@ documented treatment of invalid schema paths.
 
 ## 2. Resolution can transfer explicitness to a different semantic path
 
-Priority: P2. Status: open.
+Priority: P2. Status: resolved. Evidence: the engine resolution/metadata/provenance
+regressions, the full engine suite, and the integrated checks recorded in
+[implementation.md](implementation.md).
 
 Relevant code: `applyResolutionMetadata`, `applyResolutionFieldOrigins`, and
 `refreshResolutionFields` in
@@ -122,7 +127,10 @@ repair this publication path.
 
 ## 3. Metadata history mixes numeric-key and sequence-index definitions
 
-Priority: P2. Status: open.
+Priority: P2. Status: resolved. Evidence: `TestPublicHistoryUsesResolutionShapeAttribution`,
+`TestPublicHistoricalPathsEnumerateContextualShapes`, shared history-selection
+and explanation regressions, and the integrated checks recorded in
+[implementation.md](implementation.md).
 
 Relevant code:
 
@@ -163,7 +171,9 @@ and compare metadata history with explanation.
 
 ## 4. Diagnostic canonicalization breaks composition claimant ordering
 
-Priority: P3. Status: open.
+Priority: P3. Status: resolved. Evidence: `TestFacadeCompositionConflictKeepsClaimantOrder`,
+the engine diagnostic-order regression, and the integrated checks recorded in
+[implementation.md](implementation.md).
 
 Relevant code: `compositionConflictDiagnostic` in
 [compose.go](../../internal/engine/compose.go) and `canonicalDiagnostics` in