Reuse parsed sensitivity paths

docs/roadmap/implementation.md

@@ -468,6 +468,12 @@ separate design/evidence and do not block this sequence.
 
 ### Final evidence and outcomes
 
+- Post-review Stage 9 completion: sensitivity collection now reuses existing
+  valid parsed paths without reparsing; later projections still replace typed
+  history paths. Repeated parsed contributions and both numeric mapping/sequence
+  transitions are covered. Focused sensitivity/inheritance/rendering tests,
+  `./scripts/check.sh`, and `go test -race ./internal/engine` passed.
+
 - Reviewed planning baseline `0c77deed05417edb32f42c7bf24df2fdc2581a25`,
   production baseline `48619de024d794cf41e90b171b7fcbe609dcd437`, and the
   complete implementation diff through `799ebab5a6f15e8252474b8cb7ea164ef503f390`.

docs/roadmap/remediation.md

@@ -17,7 +17,11 @@ The older, completed ReleaseKit review record remains in Git history at
 
 ## 1. Complete parsed-path reuse in sensitivity collection (P2)
 
-Status: Open.
+Status: Complete. Parsed accumulator paths are reused, while typed historical
+paths still receive the later parsed replacement. Repeated root/escaped/numeric
+contributions and both numeric mapping/sequence transitions are covered.
+Focused sensitivity/inheritance/rendering tests, `./scripts/check.sh`, and
+`go test -race ./internal/engine` passed.
 
 Affected: [secret.go](../../internal/engine/secret.go), `addSecretPath`
 (lines 85–89); implementation Stage 9, item 3.