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

Expose configuration metadata and findings

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-07 04:32:24 +00:00
parent 0183022a28
commit da120c2dd4
15 changed files with 179 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/cli.md
View File

@@ -297,8 +297,9 @@ example config scopes
example config scopes --format yaml
```
Text output uses one `scope: operation, operation` line per scope. YAML uses a
`scopes` sequence with explicit `name` and `operations` fields. Scope order is
Text output uses one `scope: operation, operation` line per scope and lists any
declared optional features. Structured output uses a `scopes` sequence with
`name`, `operations`, and any supported `features`. Scope order is
`app`, then `promptkit`, then other names alphabetically. A metadata-only scope
can be listed without an acquisition callback. Discovery does not construct a
runtime context or acquire configuration. It reports the intersection between

5
docs/consumers/guide.md
View File

@@ -249,7 +249,10 @@ adapts a typed ConfigKit loader without calling it during construction.
The `config` family provides scope discovery, validation, safe effective configuration display,
source inventory, path explanation, and ConfigKit-backed comparison for the
capabilities declared by its scopes. The [CLI reference](../cli.md#configuration-scopes)
owns operator syntax and report details.
owns operator syntax and report details. `Scope.Features` declares optional modes; acquired
`View.Metadata` and `View.Findings` carry native path metadata and diagnostic
records when available. `Findings.Messages` contains presentations associated
with those records, while `Acquired.Diagnostics` carries independent messages.
## PromptKit configuration, definitions, and requirements

7
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Shared reporting and PromptKit v0.20.0 implementation plan
Status: implementation in progress; Stages 1–13 complete.
Status: implementation in progress; Stages 1–14 complete.
## Scope, authority, and execution
@@ -491,6 +491,11 @@ conflicts. Metadata/help/completion remain independent of engine acquisition.
## Stage 14: Metadata and failed-acquisition evidence facets
**Complete.** Scope feature discovery and native metadata, findings, and
failed-load source snapshots are available to subsequent operation modes.
The root, ckconfig, and ckprompt workspace suites passed with Go 1.27.0,
including wrapped failures and independent diagnostic delivery.
Extend [ckconfig contracts](../../integrations/ckconfig/contracts.go) with
`Scope.Features ScopeFeatures`: `PathDiscovery`, `PathShow`, and `Overrides`
booleans. These describe optional modes within existing commands, not new