From 1a8f1cc3a5d5a193f31b527e127ee576b1336f94 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Mon, 19 Oct 2026 20:29:36 +0000 Subject: [PATCH] Record directory link discovery completion --- docs/roadmap/implementation.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index 56b759e..4d74bd1 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -1,6 +1,6 @@ # Implementation Plan: Import Discovery and Dependency-Ready Ordering -Status: Stages 1–11 complete; 8 implementation stages remain. +Status: Stages 1–12 complete; 7 implementation stages remain. ## Authority, baseline, and execution @@ -480,6 +480,14 @@ Acceptance: host filesystem behavior and a focused link-aware native fixture pass; plain native filesystems still load without new capability requirements. All success/failure paths close library-owned directory and root handles. +Completion: implemented in commit `9b99463` (`Follow links safely during +directory discovery`). Verified with directory-selection tests, the full engine +suite and race suite, native resource-close tests, `go vet ./...`, `go build +./...`, and `git diff --check`. Host traversal uses root-relative link inspection; +native traversal uses `fs.ReadLinkFS` when available and leaves plain native +filesystems usable. `./scripts/check.sh` still fails only on prompt-catalog +sequence-order expectations reserved for Stage 18. Stage 13 onward remains. + ## Stage 13 — Integrate glob filtering and final candidate accounting Adapt `glob.go` to the common selection pipeline. Keep path wildcards and