Migrate maintained examples to invocation reporting

This commit is contained in:
2026-10-26 03:44:19 +00:00
parent b6f22462d3
commit 6264a87183
8 changed files with 204 additions and 19 deletions

View File

@@ -1,6 +1,6 @@
# Invocation reporting implementation plan
Status: Stages 1–16 complete. Stage 17 is next.
Status: Stages 1–17 complete. Stage 18 is next.
## Objective and authority
@@ -642,7 +642,7 @@ explanation, then exits with status 1 as expected.
## Stage 17: Migrate maintained integration consumers
Status: pending.
Status: complete.
Primary directories:
[ckconfig example](../../integrations/ckconfig/examples/simple) and
@@ -664,6 +664,16 @@ Validation: both example packages compile in their owning modules and run
without external services. Confirm custom commands and integration commands
share the same reporting flags and terminal behavior.
Completion: migrated both example-owned handlers to invocation reporters and
explicit explanations with optional causes. The ConfigKit consumer demonstrates
a provider schema warning in verbose mode, ordinary report output, and quiet
suppression. The composed consumer retains aliased help and offline smoke usage;
its tests cover a native report with an independent provider warning, terminal
context, and an operation error, plus quiet custom-command success and domain
failure. Both integration modules pass `GOTOOLCHAIN=local go test ./...`,
including both example packages. Representative verbose ConfigKit, quiet
ConfigKit, aliased quiet help, and offline PromptKit smoke commands also pass.
## Stage 18: Reconcile the full test suite and architectural boundaries
Status: pending.