Document import and facade boundaries

docs/roadmap/roadmap.md

@@ -1,6 +1,7 @@
 # Audit Remediation Roadmap
 
-Status: target accepted; execution is tracked in the [implementation plan](implementation.md).
+Status: target accepted; completed execution is recorded in the historical plan
+at `bb5540b:docs/roadmap/implementation.md`.
 Prepared: 2026-10-25. Planning baseline: `e1e94ee`.
 
 This roadmap describes the target state and related work for the 29 entries
@@ -14,9 +15,9 @@ It is intended for maintainers reviewing the remediation's scope and architectur
   independently reproduced by writing this roadmap.
 - This document owns the combined target state, work areas, and design intent.
   Finding IDs below provide traceability without repeating the full audit inventory.
-- The [implementation plan](implementation.md) owns concrete stages, private
-  implementation choices, edits, validation commands, and execution progress.
-  It carries the selected IDs through to completion evidence.
+- The historical implementation plan at
+  `bb5540b:docs/roadmap/implementation.md` records concrete stages, private
+  implementation choices, edits, validation commands, and completion evidence.
 
 The [configuration contract](../config.md), public Go declarations, and
 [architecture policy](../policy/architecture.md) remain the owners of behavior
@@ -227,11 +228,12 @@ count are not acceptance criteria for this work.
 
 ## Implementation Plan
 
-The [implementation plan](implementation.md) defines the sequential, Luna-scoped
-stages and their dependencies, including coordinated changes to descriptor state,
-history ownership/accounting, collection policy, acquisition, and replacement
-public coverage. It also owns validation commands and the complete finding-to-stage
-map. The audit remains the owner of original evidence and detailed acceptance cases.
+The historical implementation plan at `bb5540b:docs/roadmap/implementation.md`
+defines the sequential, Luna-scoped stages and their dependencies, including
+coordinated changes to descriptor state, history ownership/accounting, collection
+policy, acquisition, and replacement public coverage. It also records validation
+commands and the complete finding-to-stage map. The audit remains the owner of
+original evidence and detailed acceptance cases.
 
 ## Validation And Completion
 
@@ -244,27 +246,31 @@ matter and narrow fault injection for read/close failures. State platform limits
 
 Applicable development checks come from the [development guide](../development.md),
 including appropriate race coverage for changed ownership and lifetime boundaries.
-The implementation plan owns their execution. Existing audit results are baseline
-evidence, not validation of the eventual changes. No performance benchmark campaign is
-required by this roadmap, and no new benchmark results are claimed.
+The historical implementation plan owns their execution. Existing audit results
+are baseline evidence, not validation of the eventual changes. No performance
+benchmark campaign is required by this roadmap, and no new benchmark results are
+claimed.
 
 Completion means all 29 selected findings have implementation and acceptance
 evidence, the affected public behavior remains consistent with its contracts,
 and canonical internal documentation describes the resulting owners. The
-implementation plan owns execution status without duplicate progress inventories.
-Retire completed planning records under the normal documentation lifecycle.
+historical implementation plan records execution status without duplicate
+progress inventories. Retire completed planning records under the normal
+documentation lifecycle.
 
 ## Scope Boundaries And Decision Status
 
 All three audit scope questions are settled. No significant architectural or
-product decision remains open for this roadmap. The implementation plan records
-private design choices and sequencing, subject to the acceptance cases above.
+product decision remains open for this roadmap. The historical implementation
+plan records private design choices and sequencing, subject to the acceptance
+cases above.
 If that work exposes a need to change a public contract, bring the specific
 decision back for review rather than treating it as an implicit part of remediation.
 
 The glob preparation refactor (C03) and wider facade transport simplification
-(F07) remain the first two entries in [future.md](future.md), for consideration
-after this selected work is complete. Other deferred features, clone-traversal
-redesign, and broader performance experiments remain outside this effort. Keep
+(F07) have since been selected in the
+[internal-boundary roadmap](internal-boundaries.md). Other deferred features,
+clone-traversal redesign, and broader performance experiments remain outside
+this effort. Keep
 existing ownership boundaries and loading APIs; no ADR or architecture-policy
 change is proposed by this roadmap.