Document PromptKit catalogs and smoke testing
This commit is contained in:
@@ -33,7 +33,8 @@ operator or consumer need and an appropriate ownership/behavior decision:
|
||||
- JSON reports, shell completion, and output-file management or reloadable export.
|
||||
- Configuration mutation, generic value assignment, and exhaustive field-origin
|
||||
inventories.
|
||||
- Credential diagnostics and live provider probes.
|
||||
- Credential diagnostics beyond PromptKit's native smoke checks and additional
|
||||
live provider probes.
|
||||
- Additional component identity registration and domain artifact catalogs.
|
||||
- Additional library families, including possible FeedKit integration; families
|
||||
can define suitable verbs without requiring comparison or configuration scopes.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Dependency upgrades, discovery, and smoke testing implementation plan
|
||||
|
||||
Status: Stages 1–16 complete; Stage 17 is next.
|
||||
Status: Stages 1–17 complete; Stage 18 is next.
|
||||
|
||||
## Authority and baseline
|
||||
|
||||
@@ -829,6 +829,16 @@ is required.
|
||||
**Complete when:** current contracts describe implemented behavior under their
|
||||
canonical owners and historical references remain correctly scoped.
|
||||
|
||||
**Completed:** 2026-10-17. GoDoc, module summaries, the README, CLI reference,
|
||||
consumer guide, development commands, and internal inventory now describe the
|
||||
adopted source evidence, eight `FromEngine` callbacks, five catalogs, optional
|
||||
request validation, and native smoke behavior. Smoke examples and catalog
|
||||
commands were run against the maintained composed consumer; `go doc` confirmed
|
||||
the exported helper and request documentation. Local Markdown links/fragments,
|
||||
stale upstream revision references, and whitespace checks passed. Deferred-work
|
||||
scope and historical implementation-plan links were reconciled without changing
|
||||
historical API examples or release notes.
|
||||
|
||||
## Stage 18: Verify the complete target and finish
|
||||
|
||||
1. Format all changed Go files and inspect the full diff for unrelated changes,
|
||||
|
||||
@@ -3,7 +3,8 @@
|
||||
Status: accepted adoption and feature roadmap; implementation complete.
|
||||
Command placement, adapter composition, request construction, artifact syntax,
|
||||
and initial presentation are settled. This document defines the target and
|
||||
required work; the [implementation plan](implementation.md) sequences the work.
|
||||
required work; the [implementation plan](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/38b49f29fb3a8f22ff02528d2a0ed413e5c6ab1e/docs/roadmap/implementation.md)
|
||||
sequences the historical implementation work.
|
||||
|
||||
## Purpose
|
||||
|
||||
|
||||
@@ -8,7 +8,8 @@ architectural redesign was identified as necessary.
|
||||
Reviewed implementation commits after planning baseline `3218222`, through
|
||||
`420483b2d4659862626422b0577e39bc0a4c1a2d`, against the
|
||||
[accepted feature roadmap](promptkit-validation.md),
|
||||
[implementation plan](implementation.md), applicable ADRs, and repository policy.
|
||||
[implementation plan](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/38b49f29fb3a8f22ff02528d2a0ed413e5c6ab1e/docs/roadmap/implementation.md),
|
||||
applicable ADRs, and repository policy.
|
||||
The review covered production changes, new tests, the maintained consumer,
|
||||
dependency metadata/attribution, and updated documentation.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user