Plan the native ConfigKit migration

This commit is contained in:
2026-11-17 20:41:34 +00:00
parent 4a0e3c83db
commit 65d0e518e5
2 changed files with 383 additions and 317 deletions

View File

@@ -7,10 +7,10 @@ authoring and inspection features useful to operators. Align configuration
semantics with other ConfigKit consumers. Existing Narratio assembly conventions
are migration inputs rather than compatibility requirements for this work.
This roadmap defines the target and required changes. A subsequent implementation
plan will define staged work for the agreed target. This pass adds documentation
only. The earlier [v0.5.0 roadmap](config.md) and
[implementation plan](implementation.md) describe the completed baseline.
This roadmap defines the target, user intent, and required changes. The
[implementation plan](implementation.md) defines the work needed to reach that
target. The earlier [v0.5.0 roadmap](config.md) records the completed adoption
that forms the current baseline.
The ownership boundary in [ADR 0003](../adr/0003-assign-configuration-ownership.md)
continues to apply: ConfigKit resolves configuration before its final handoff;
@@ -200,7 +200,7 @@ does not update rendering or diff. Integrate this distinction explicitly:
record domain resolution within a supported resolver when its inputs are
available there; where later campaign resolution remains appropriate, create
a completed native inspection result from the finalized safe domain projection
using the public mapping-source API. That result describes application-derived
using ConfigKit's public loading APIs. That result describes application-derived
values; retained authoring results supply actual file provenance.
Use native comparison rather than maintaining a second general mapping-diff