From f173fdbc1bc598063d00ccf87ec0c441354c6d88 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Sat, 17 Oct 2026 15:54:19 +0000 Subject: [PATCH] Keep upgrade adapters and examples focused --- docs/roadmap/upgrades.md | 34 +++++++++++++++++++++++++--------- 1 file changed, 25 insertions(+), 9 deletions(-) diff --git a/docs/roadmap/upgrades.md b/docs/roadmap/upgrades.md index 3c66d0f..b76616a 100644 --- a/docs/roadmap/upgrades.md +++ b/docs/roadmap/upgrades.md @@ -17,6 +17,11 @@ resource identity and resolution, validation, inspection evidence, and diagnosti meaning. Applications choose their inputs, policies, defaults, credentials, artifacts, and runtime construction. +Keep adaptation proportionate to that ownership. Reports are direct projections +of upstream data, with small presentation DTOs where YAML naming and formatting +need them. Preserve native values and meanings rather than introducing a +parallel semantic model or normalization layer. + The [architecture policy](../policy/architecture.md), accepted [ADRs](../adr/), and [release policy](../policy/release.md) govern this work. Upstream contract changes flow through the owning integration; they do not justify reimplementing @@ -181,12 +186,13 @@ about installed provider catalogs and the former built-in standard/auto profiles CommandKit must not silently reintroduce those catalogs. The owning application chooses files, embedded inputs, programmatic mappings, and collections. -The maintained composed consumer should demonstrate valid explicit composition -and useful root/qualified identities without requiring a model service. Update -its campaign configuration, loader, request builder, fixtures, and examples to -the direct-definition format. Collections are available through native -`CollectionInput` and configuration sources; applications need not use them to -adopt v0.16.0. +Keep the maintained composed consumer migration small: update its configuration, +loader, request builder, and fixtures as needed for direct definitions and the +new interfaces, without requiring a model service. Use a small configuration to +illustrate the relevant wiring and identities; a comprehensive collections +example or migration framework is not required. Collections are available +through native `CollectionInput` and configuration sources; applications need +not use them to adopt v0.16.0. Configured references retain their native exact identities. Mounting a source does not rewrite backend/profile references or extend profile inheritance beyond @@ -208,6 +214,10 @@ These capabilities remain independently optional; one missing inventory does not disable other operations. Reuse the existing construction, registration, typed input/state, configuration selection, and diagnostic machinery. +Forward native namespace filters and resource-kind selections to their respective +APIs. PromptKit performs identity resolution and inventory membership selection; +the adapter translates the selected CLI syntax into those native inputs. + The namespace behavior has two distinct owners: - An application loader may return a native `WithNamespaces` engine view. That @@ -237,6 +247,12 @@ success; native invocation errors receive the normal operational failure classification. Present native observations without deriving an additional readiness verdict or adding warnings about perceived upstream limitations. +Use a focused report-delivery path that preserves a returned report alongside +its native error, including cancellation. The existing success-only inspection +writer cannot be reused unchanged for that case. Adapt delivery within the +current outcome model; this work does not require a general diagnostics +framework. + Smoke testing runs when its command is explicitly invoked. Configuration, requirements, help, and release operations retain their own existing behavior. OD-4 records its inclusion in the current delivery scope; a separate feature @@ -288,9 +304,9 @@ Verify that command inputs and context reach the intended native APIs, including ID-only prompt requests, default/explicit listing filters, and smoke requests. Verify faithful representation of upstream-returned source evidence, optional labels, inventories, diagnostics, and errors, together with CommandKit's optional -command availability, -invocation lifetimes, outcome classification, and output delivery. Include smoke -report-plus-error delivery and error identity in this boundary coverage. +command availability, invocation lifetimes, outcome classification, and output +delivery. Include smoke report-plus-error delivery and error identity in this +boundary coverage. These checks establish CommandKit's access to the capabilities. They should not test whether ConfigKit correctly places or composes sources, checks versions,