Retire completed roadmaps before the next release

docs/roadmap/future.md

@@ -6,14 +6,6 @@ plans, or release commitments. Adopting a candidate requires an explicit design
 decision and a separate plan. Significant architectural exclusions and their rationale belong
 in ADRs; this document does not maintain a list of rejected proposals.
 
-## 1. Separate glob entry preparation from traversal
-
-Implemented in the [internal-boundary roadmap](internal-boundaries.md#glob-entry-preparation) (C03).
-
-## 2. Simplify redundant facade-to-engine transport
-
-Implemented in the [internal-boundary roadmap](internal-boundaries.md#facade-to-engine-transport) (F07).
-
 ## 3. Recursive body merging for identified records
 
 Status: deferred. The implemented
@@ -91,3 +83,22 @@ evidence are preserved in Git history at `8e91a2b` under `docs/roadmap/`.
   across loads without introducing aliasing?
 - What cache lifetime and concurrency design would make schema reuse worthwhile
   without excessive retained memory?
+
+## 6. Public path comparison
+
+Status: deferred pending a concrete consumer need. This preserves A2 from the
+completed API review at `68400ff:docs/roadmap/review.md`.
+
+`Path.String()` is a JSON Pointer spelling, not a complete semantic identity:
+an explicit numeric mapping key and a sequence index can share it. The public
+type is opaque and currently non-comparable.
+
+If consumers need comparison, consider a small exact-representation operation
+rather than exposing mutable segments or introducing a pattern language. A
+proposal must distinguish exact segment representation, including parsed versus
+explicit segments and invalid state, from resolution against a document. Pointer
+string equality must not be presented as semantic equality.
+
+Keeping `Path` solely as an opaque query/building value remains an alternative.
+No current contract changes or implementation commitment follow from this entry;
+a comparison operation can be added compatibly later.