Resolve absolute destinations inside the candidate checkout
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Shared validation foundation remediation
|
||||
|
||||
Status: Remediation in progress; findings 1–4 addressed, findings 5–6 pending.
|
||||
Status: Remediation in progress; findings 1–5 addressed, finding 6 pending.
|
||||
|
||||
Reviewed committed implementation `f53354b`, covering the eight foundation
|
||||
commits after `0c7129a`, against the [implementation plan](implementation.md),
|
||||
@@ -175,6 +175,13 @@ complete message wording as a contract.
|
||||
|
||||
## 5. P2: Absolute paths inside the checkout are classified as outside
|
||||
|
||||
**Resolution:** Addressed. Absolute destinations and symlink targets within the
|
||||
captured repository directory map to candidate paths before component
|
||||
traversal. Absolute paths with similar external prefixes remain outside.
|
||||
Regression tests also retain symlink-before-parent semantics and demonstrate
|
||||
that removed committed files resolve while live-only files remain missing.
|
||||
`go test ./internal/validation` passed.
|
||||
|
||||
**Owner:** [candidate destination resolver](../../internal/validation/tree.go),
|
||||
the absolute-destination and absolute-symlink branches.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user