Record item scope scheduling completion

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implementation Plan: Import Discovery and Dependency-Ready Ordering
 
-Status: Stages 1–5 complete; 14 implementation stages remain.
+Status: Stages 1–6 complete; 13 implementation stages remain.
 
 ## Authority, baseline, and execution
 
@@ -342,6 +342,14 @@ Acceptance: nested items, helper-supplied IDs, main items, multiple unequal
 branches, physical coordinates, sensitivity, history chronology, and item
 conflict paths pass engine and public tests. Run the focused race suite.
 
+Completion: implemented in commit `af43d6f` (`Schedule item-local import
+scopes`). Verified with `go test ./internal/engine -count=1`,
+`go test -race ./internal/engine`, `go test . -count=1`, `go vet ./...`,
+`go build ./...`, the local documentation-link test, and `git diff --check`.
+`./scripts/check.sh` reaches the consumer examples and currently fails only on
+prompt-catalog ordering expectations assigned to Stage 18. Stage 7 onward
+remains.
+
 ## Stage 7 — Schedule underlay forests and preserve tier boundaries
 
 In `load_request.go`, acquire all roots in a strict underlay group before