Inspect hosted assets against build manifests

This commit is contained in:
2026-10-05 19:56:32 +00:00
parent 717d6d0d04
commit 692a503c26
9 changed files with 695 additions and 13 deletions

View File

@@ -1,6 +1,6 @@
# ReleaseKit staged implementation plan
Status: In progress. Stages 1–12 are complete; later stages remain pending.
Status: In progress. Stages 1–13 are complete; later stages remain pending.
Date: 2026-10-05
@@ -758,7 +758,7 @@ request paths, payloads, and authentication without using real credentials.
## Stage 13: Inspect asset and manifest content
Status: Pending. Depends on Stage 12.
Status: Complete. Depends on Stage 12.
1. Generate the expected binary manifest from the declared build result. Add
attachment discovery and streaming hash comparison of existing assets.

View File

@@ -2,11 +2,11 @@
This is a proposal based on a review of PromptKit, ConfigKit, Audita, Notarius,
Narratio, and Scriptorium on 2026-09-29. The implementation plan records the
current implemented boundary; the internal Gitea page client is implemented,
while asset delivery, facade/CLI integration, and broader integrations remain
planned. The public facade architecture is accepted in
[ADR 0001](../adr/0001-public-facade.md) and is implemented for runtime version,
candidate validation, and source publication.
current implemented boundary; the internal Gitea page and asset-inspection
client is implemented, while asset delivery, facade/CLI integration, and
broader integrations remain planned. The public facade architecture is
accepted in [ADR 0001](../adr/0001-public-facade.md) and is implemented for
runtime version, candidate validation, and source publication.
The [implementation plan](implementation.md) owns ordered stages, execution
instructions, acceptance checks, and progress toward this target state.
@@ -57,8 +57,9 @@ The [architecture policy](../policy/architecture.md) owns the adopted
responsibility and dependency rules, including the runtime version boundary.
The root `releasekit` package provides the public facade for candidate
validation, source publication, and selected-target builds. The internal
Gitea page client is implemented; delivery orchestration remains planned. The
separate public `buildinfo` package provides lightweight runtime version access.
Gitea page and asset-inspection client is implemented; delivery orchestration
remains planned. The separate public `buildinfo` package provides lightweight
runtime version access.
Each facade owns its public named types and documented contracts. Public
operations, inputs, outcomes, errors, and callbacks express deliberately