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

Validate invocation reporting implementation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-26 03:59:28 +00:00
parent 96aa6b5ca0
commit 7c035ccc54
2 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Invocation reporting implementation plan
Status: Stages 1–19 complete. Stage 20 is next.
Status: Stages 1–20 complete.
## Objective and authority
@@ -760,7 +760,7 @@ notes, accepted ADRs, and deferred-work records remain unchanged.
## Stage 20: Validate the complete end state and finish
Status: pending.
Status: complete.
1. Format changed Go files with `gofmt`; review the complete diff for unintended
behavior changes, unselected restrictions, compatibility machinery, public
@@ -800,6 +800,16 @@ Status: pending.
validation results, any genuine limitations, and worktree status. Do not
declare a release or remove the roadmap/plan automatically.
Completion: `gofmt` left the changed Go files formatted. The root, ckconfig, and
ckprompt workspace suites pass; the root workspace-off suite and focused
reporter race suite pass. Maintained examples pass for core reporting, quiet
help/version, scoped PromptKit YAML, and aliases. The composed-example failure
test confirms an offline smoke report remains available alongside an injected
operational error and terminal context. The ignored `go.work` still includes
all three modules and was not committed. Final Markdown links and fragments and
staged and unstaged whitespace checks pass. All selected roadmap behaviors are
implemented; no release or publication action was performed.
## Completion criteria
The sprint is complete when the selected public API replaces the old paths;

7
docs/roadmap/reporting.md
View File

@@ -11,10 +11,9 @@ selected. The consumer API signatures, presentation-result model, provider
diagnostic boundary, fallback explanations, and rendering callback boundary
below are also selected. Architectural preparation is complete:
[ADR 0014](../adr/0014-invocation-reporting.md) is accepted, and the
[architecture policy](../policy/architecture.md) is aligned. Implementation has
started. Stages 1–19 are complete; final validation remains. The
[implementation plan](implementation.md) owns stage order and execution
instructions.
[architecture policy](../policy/architecture.md) is aligned. Implementation and
final validation are complete; Stages 1–20 are complete. The [implementation
plan](implementation.md) records the stage order and validation evidence.
## Purpose