Consolidate and renumber architectural decision records

docs/roadmap/future.md

@@ -206,7 +206,9 @@ Execution, serving, and session operations remain application-owned. The
 [request preview proposal](promptkit-v0.19.0.md#preview-and-request-flags)
 exposes native preparation and rendering as an agreed operator inspection target;
 implementation has not started.
-Shared vocabulary is guidance under [ADR 0006](../adr/0006-command-grammar.md).
+The [architecture policy](../policy/architecture.md#command-and-application-ownership)
+recommends shared vocabulary; the [CLI reference](../cli.md#registered-command-syntax)
+owns implemented grammar.
 Backend replacement remains possible behind the accepted facade, subject to the
 published API/CLI contracts and deliberate compatibility decisions.
 

docs/roadmap/promptkit-v0.19.0.md

@@ -41,8 +41,8 @@ operations. Applications continue to own engine construction, domain inputs,
 credentials, execution, and their executable lifecycle.
 
 The [architecture policy](../policy/architecture.md),
-[optional-module decision](../adr/0010-optional-integration-modules.md), and
-[reporting decision](../adr/0014-invocation-reporting.md) govern implementation.
+[optional-module decision](../adr/0004-optional-integration-modules.md), and
+[reporting decision](../adr/0006-invocation-reporting.md) govern implementation.
 The [CLI reference](../cli.md) and public GoDoc remain the owners of implemented
 contracts. This roadmap records planned work, not new guarantees about upstream
 behavior or permanent limits on future features.
@@ -240,9 +240,10 @@ core. Never reconstruct inspection from mutable `Result.Config` or source files.
 Select source IDs from acquired inventory; native `Source(id)` is a convenience,
 not another provider requirement. Source IDs are local to one load.
 
-[OD-9](#od-9-independent-comparison-selector-bindings) replaces ADR 0012's
-inheritance while retaining its two-input/provider lifecycle. Domain defaults
-and caching remain application-owned.
+[OD-9](#od-9-independent-comparison-selector-bindings) replaces the
+[current comparison inheritance](../cli.md#compare-configuration-selections)
+while retaining the two-input/provider lifecycle. Domain defaults and caching
+remain application-owned.
 [OD-10](#od-10-comparison-assertion-outcomes) uses native differences for assertions;
 source/history differences alone and changed credential bytes behind unchanged
 references are not necessarily effective-value differences.
@@ -400,11 +401,14 @@ disclosure rules, or inspection evidence. This is an output conversion, not a
 replacement for upstream configuration loading or validation. No lossless YAML
 document model or second rendering pipeline is needed.
 
-When implementation lands, record the deliberate replacement of
-[ADR 0007](../adr/0007-native-yaml-reports.md)'s native-writer and mapping-order
-requirements in a superseding ADR and update current contracts. Retain the
-accepted ADR's decision text as history. The aggregate presentation decision below
-also replaces its separate-document framing.
+When implementation lands, update the
+[current display contract](../cli.md#show-effective-configuration) to replace
+native-writer and mapping-order requirements. The aggregate presentation decision
+below also replaces separate-document framing. These presentation changes follow
+the ownership boundary in [ADR 0006](../adr/0006-invocation-reporting.md); they do
+not require a separate successor ADR. The
+[alpha consolidation](../adr/README.md#alpha-consolidation) retired the former
+detailed report records without changing current behavior.
 
 This approach reduces new machinery by reusing standard serialization and
 centralizing the remaining conversion and rendering work. Exact internal
@@ -486,10 +490,10 @@ behavior: acquire all selected views and complete provider-required validation
 before report output begins; a failure prevents the combined display. The new
 shape does not introduce partial-success output.
 
-When implementation lands, supersede ADR 0007's ordered native-document framing
-and refine [ADR 0009](../adr/0009-configuration-scopes.md)'s combined-display
-ordering contract through a new ADR. This decision concerns aggregate display;
-it does not change scope discovery or acquisition ordering.
+When implementation lands, update the CLI display contract and affected tests
+for this aggregate shape. Scope discovery and acquisition ordering are unchanged.
+The capability model in [ADR 0003](../adr/0003-configuration-scopes.md) does not
+prescribe report framing or mapping order.
 
 ### Remaining core reporting implementation details
 
@@ -623,7 +627,7 @@ or field order.
    implementation approach. Keep boundary coverage with each change.
 6. **Update operator and consumer documentation.** The CLI reference owns
    syntax, report schemas, availability, and outcomes; GoDoc owns callback and
-   value contracts. Update the affected ADRs and architecture policy, and replace
+   value contracts. Keep architectural ownership references aligned, and replace
    the testing policy's old native-YAML/document-order guidance when the new report
    behavior lands. Extend maintained simple/composed examples to demonstrate
    the new CLI tasks using local fixtures, without adding application-internal
@@ -731,11 +735,13 @@ rather than prescribing one test per line or exact cosmetic snapshots.
 - [ ] Maintained simple/composed consumers demonstrate the new CLI tasks and
   failure workflow with deterministic fixtures. Code remains proportionate:
   thin projections, one shared rendering implementation, and focused tests.
-- [ ] Superseding ADRs record changes to ADR 0007/0009 reporting and ADR 0012
-  comparison. Update CLI/API contracts, release notes, and examples with the
-  implementation, including validation delivery timing. Incorporate the ownership
-  principles into architecture.md and replace obsolete native-YAML/document-order
-  guidance in testing policy. Current documentation must match the landed scope.
+- [ ] Update CLI/API contracts, release notes, and examples with the implementation,
+  including report framing, independent comparison selections, and validation
+  delivery timing. Incorporate the ownership principles into architecture.md and
+  replace obsolete native-YAML/document-order guidance in testing policy. The
+  consolidated ADRs own architectural rationale; these presentation and selector
+  changes need no separate successor records. Current documentation must match
+  the landed scope.
 - [ ] Final independent-module and aligned-workspace suites pass with dependency
   identities recorded. Deferred features remain outside this adoption.
 
@@ -1265,12 +1271,12 @@ not implicitly shared. Domain parsing stays in declared typed bindings; no
 generic selector language is introduced. Retain the two input preparations and
 checks, one shared invocation state, and existing provider lifecycle.
 
-This deliberately replaces the previous inheritance model, including existing
-config/overlay behavior and shared application selectors. When implementation
-lands, record the change in a superseding ADR for the affected decisions in
-ADR 0012, retaining its accepted decision text as history, and update current
-CLI/API contracts and examples. Exact helper signatures and flag collision
-handling remain implementation design tasks.
+This deliberately replaces the current inheritance model, including existing
+config/overlay behavior and shared application selectors. Update CLI/API contracts
+and examples when implementation lands. The input/state ownership in
+[ADR 0001](../adr/0001-command-dispatch-and-inputs.md) remains unchanged; selector
+policy does not need a separate successor ADR. Exact helper signatures and flag
+collision handling remain implementation design tasks.
 
 **Agreed collection scope:** leave explicit-empty selection for application-defined
 repeatable selectors to application-declared bindings in this release. Omission