Resolve candidate paths in traversal order
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Shared validation foundation remediation
|
||||
|
||||
Status: Remediation in progress; finding 1 addressed, findings 2–6 pending.
|
||||
Status: Remediation in progress; findings 1–2 addressed, findings 3–6 pending.
|
||||
|
||||
Reviewed committed implementation `f53354b`, covering the eight foundation
|
||||
commits after `0c7129a`, against the [implementation plan](implementation.md),
|
||||
@@ -63,6 +63,13 @@ and bounded even when testing the broken behavior.
|
||||
|
||||
## 2. P2: Path cleanup changes symlink traversal and checkout classification
|
||||
|
||||
**Resolution:** Addressed. Destination components and symlink targets are
|
||||
traversed in order, with parent traversal applied to resolved directories.
|
||||
Missing entries and regular-file traversal remain observable. Regression tests
|
||||
cover both destination and symlink-target parent components and confirm that
|
||||
neighboring files do not change classification.
|
||||
`go test ./internal/validation` passed.
|
||||
|
||||
**Owner:** [candidate destination resolver](../../internal/validation/tree.go),
|
||||
initial destination construction and construction after symlink expansion.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user