Replay added configuration paths in explanations

docs/config.md

@@ -162,7 +162,10 @@ parser values. `Present=false` with empty YAML means absence or deletion; explic
 null is present and renders as `null`. The history starts with the canonical typed
 application-default or Go-zero baseline, then includes only relevant base sources in
 traversal order, the selected profile, supplied CLI records, and audited net
-resolution operations. Explicit equal writes remain visible. When input replay
+resolution operations. Overlapping parent/child resolution records are rendered
+as one net subtree event with combined reasons and dependencies, rather than
+pretending that the recorded assignments ran in lexical order. Explicit equal
+writes remain visible. When input replay
 differs from the final typed input, a `ChangeDecoding` event records the transition
 before domain resolution. Its origin retains the decoded path's source/default
 attribution; its reason identifies static-default retention and canonical decoding.

docs/roadmap/remediation.md

@@ -132,6 +132,11 @@ the effective value and origin without implying that a final-present path is abs
 
 ## 5. P2 — Replay newly created resolution paths
 
+Status: complete. Replay inserts new mapping entries/subtrees and coalesces
+overlapping parent/child net operations while retaining reasons and dependencies.
+Leaf/container regressions cover nested creation, removal and overlapping records.
+Full tests pass with the issue-8 TMPDIR workaround; vet, build and whitespace pass.
+
 Evidence: [explain.go](../../explain.go), `replaceHistoryPath`, returns immediately
 when a mapping entry is absent, even when the replacement is a newly created value.