base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Assemble configuration families and inputs

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 01:34:25 +00:00
parent 1e1eca4a88
commit 809a36bc46
4 changed files with 543 additions and 233 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Implement the optional integration modules and captured registration API
Status: implementation in progress. Stages 1 through 8 are complete; subsequent work follows the ordered roadmap.
Status: implementation in progress. Stages 1 through 9 are complete; subsequent work follows the ordered roadmap.
Execute the stages in order. Each stage is sized as a separate Luna coding-agent
assignment. This document authorizes no publication or changes to sibling
repositories.
@@ -447,10 +447,20 @@ invocation-local preparation path.
needs no placeholder input/state types or forwarding wrapper. A nil loader
retains a config/app construction error.
**Completion evidence:** metadata-only suites, no scopes, partial capabilities,
all preflight, unused bindings versus invalid adapters, scope-aware validation,
independently initialized pointer inputs, preserved initialized inapplicable
fields, shared state once, and no callbacks on discovery/help/version.
**Completion evidence — complete:** `Command` eagerly captures the suite,
operation capabilities, scope metadata, selector applicability, callbacks, and
retained scope issues into a root-only `config` declaration. It validates named
scope presence/uniqueness, reserved `all`, operation values, enabled acquisition
wiring, and selector scope references. Generated inspection commands capture
only selector bindings used by scopes that support that operation; metadata-only
suites still provide ordered `config scopes` discovery and do not initialize
suite input/state or call providers. Shared preflight resolves format, scope,
aggregate availability, and explain pointers before per-scope input factories.
Each selected scope receives a fresh input, only its applicable original flags,
and scope-aware validation; successful inputs remain on the invocation-local
plan for the report handlers. `AppCommand` uses the same suite factory and
retains a nil original loader issue. Package execution checks wait for the
operation handlers and replacement of the relocated prototype tests.
## Stage 10: Port configuration reports with operation-specific timing