Prepare sensitivity dependencies once per recorded operation

docs/roadmap/remediation.md

@@ -8,7 +8,8 @@ Comparison baseline: `0dd16aa8a935645ae2847d32edd86461dc4618f0`
 Scope: the completed [implementation plan](implementation.md) and
 [interface remediation roadmap](interface-remediation.md). This report records
 remaining defects and newly introduced scalability problems; it does not change
-the selected architecture or public contracts. Completion is recorded per finding.
+the selected architecture or public contracts. All eight findings are complete;
+implementation and validation evidence is recorded per finding.
 
 ## Architecture And Review Evidence
 
@@ -387,7 +388,17 @@ should protect output equivalence without a timing assertion.
 
 ## 8. Sensitivity Preparation Expands One Dependency List Per Affected Path
 
-Priority: P2. Status: open.
+Priority: P2. Status: complete.
+
+Completion: ordinary dependency lists are expanded once per recorded target/
+attribution, and dependency candidates once per attribution, without descendant
+dependency-list copies. Classification supplies already computed inheritance
+links to candidate preparation, avoiding a second ordinary-edge construction.
+`TestResolutionSensitivityKeepsLogicalEdgesWithoutSubtreeDuplication` failed
+before the fix and now verifies the original edges, including a coalesced child
+record, and sensitivity isolation from unrelated paths. The full ordinary
+suite, full race suite, everyday check, and `git diff --check` passed. The
+original public redaction/history probes also now produce the expected results.
 
 Relevant code: `sensitivityCandidates`, lines 238–247, and
 `sensitivityDependencies`, lines 272–286, in