Validate representative ReleaseKit consumers
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# ReleaseKit audit implementation plan
|
||||
|
||||
Status: Stages 1–10 complete; Stage 11 next.
|
||||
Status: All implementation stages complete.
|
||||
Baseline: `e4be7fa` (2026-10-06). The [audit](audit.md) records the evidence,
|
||||
product goals, and selected direction. This document owns implementation order
|
||||
and completion criteria for that work.
|
||||
@@ -568,6 +568,27 @@ migration, and remaining deployment work. Every F1–F8 finding has an implement
|
||||
resolution and appropriately scoped evidence. Review and commit the final
|
||||
changes with a clean worktree.
|
||||
|
||||
**Completed:** The source-only consumer publication fixture runs one meaningful
|
||||
compatibility check against its committed note and module, then confirms the
|
||||
annotated tag on a local Git remote. A separate binary consumer fixture builds
|
||||
`buildinfo` binaries for selected Linux targets, checks native version output,
|
||||
and delivers both binaries plus `SHA256SUMS` to a local HTTP Gitea fixture.
|
||||
PromptKit and Narratio were reviewed read-only on 2026-10-06; the product
|
||||
roadmap records retained settings, runtime and policy/procedure adaptations,
|
||||
and projected deletion ranges. No sibling repositories were changed.
|
||||
|
||||
The final documentation review reconciled GoDoc, CLI/configuration references,
|
||||
consumer guidance, Woodpecker examples, the internal inventory, and product
|
||||
roadmap. The pre-release API migration is `Validate` to `AdditionalChecks` and
|
||||
`DeliveryRequest.Build` to `*BuildSpec`, with `Prebuilt` for retained artifacts;
|
||||
JSON `checks` remains the ordered additional-check setting. No new product
|
||||
decision was required. The completed stages address F1–F8; real source
|
||||
publication, an immutable tool pin, credentials, workflow activation, and live
|
||||
Gitea/Woodpecker verification remain deployment work.
|
||||
|
||||
The full offline suite and API boundary check pass with Go 1.25.0. Go formatting,
|
||||
documentation whitespace, and changed local-link checks pass.
|
||||
|
||||
## Open Questions
|
||||
|
||||
No unresolved product choice is required to implement these stages. The
|
||||
|
||||
Reference in New Issue
Block a user