Verify the complete native CLI cutover and record roadmap completion

This commit is contained in:
2026-11-20 05:17:05 +00:00
parent bd7136ceeb
commit f5573f7c8f
7 changed files with 281 additions and 11 deletions

View File

@@ -723,6 +723,44 @@ current documentation links resolve. Migration examples match the built CLI.
## Stage 9: Verify The Complete Native Cutover
**Status: Complete.** Verified the assembled native CLI on Go 1.27.4 with
`go test ./... -count=1`, `go test -race ./... -count=1`, `go vet ./...`,
and `go build ./cmd/scriptorium`. Formatting, diff whitespace, module tidiness,
shell syntax, maintained examples, and local Markdown links/anchors pass.
The maintained discovery configuration now has an end-to-end controlled-provider
test covering support/review inventories, requirements before artifacts exist,
concrete validation, preview/run context agreement, and independent native app
and framework comparisons. Existing checkout tests verify both optional entry
spellings and discovery on later invocations. Additional checks cover rejected
legacy surfaces, partial output, diagnostic delivery failure, and real child
process interrupt/SIGTERM cancellation reaching a provider request.
Built Linux amd64 and arm64 with Go 1.27.4, `CGO_ENABLED=0`, `-trimpath`,
and `-s -w` plus version/revision linker metadata. The amd64 binary reports
the injected `verification` identity and full source revision
`bd7136ceebbdc7498e9a768ce8abbe0cbb00318f`; arm64 was cross-built, not executed.
The binary also exposes help, native scope discovery, and Bash/Zsh/Fish
completion without loading configuration or contacting a provider.
Selected releases remain CommandKit v0.7.0
(`b57bfe176cff05a892e6cb07ebb5f350239e55d4`), ckconfig v0.9.0
(`9962368f0c1ea1f6ad010638e94621091105d745`), ckprompt v0.10.0
(`c9a56e1b15f2169881a91fca4e1f4a1c475e057a`), ConfigKit v1.2.1
(`51ef3144158db1a09fabdbd1c7ae59908c84923b`), and PromptKit v0.23.3
(`804a4d32b23aa2e7973400bb0a322a7016574c9f`). Module and linked-runtime
inspection confirms no replacements, workspace, vendoring, or linked maintainer
tools; attribution follows the linked dependencies, including conditional
Windows mousetrap. Public native adapters, request bindings, reporters,
`RenderReport`, and typed outcomes remain the selected integration APIs.
The final implementation audit against this plan and ADRs 0004–0006 found no
remaining required work. HTTP/report implementation and accepted ADRs remain
unchanged; no compatibility surface, post-resolution config rewriting, extra
readiness gate, workflow state, snapshot promise, or transactional delivery was
added. Embedded framework configuration, dynamic-resource completion, the
optional format accessor, and HTTP redesign remain outside this migration.
No release was published and no commits were pushed.
1. Finish any deferred stage checks against the complete application. Use real
ConfigKit, PromptKit, and CommandKit with deterministic provider substitutes
at the external boundary. Tests remain offline and independent of real keys.