From cc65e2cb61775c24b12e210b9f1419ce5993e5bb Mon Sep 17 00:00:00 2001 From: gamer147 Date: Mon, 3 Aug 2026 20:26:31 -0400 Subject: [PATCH] Record v0.1.0 release acceptance --- docs/platform-portability.md | 7 +++++-- docs/remake-architecture-and-roadmap.md | 5 +++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/platform-portability.md b/docs/platform-portability.md index d093acb..48d234e 100644 --- a/docs/platform-portability.md +++ b/docs/platform-portability.md @@ -78,8 +78,11 @@ introduced. Promotion rechecks the clean source commit, archive checksum, and ac artifact download. It is retry-safe but fail-closed: a matching partial release can receive missing assets, while mismatched release identity or a same-name/different-size asset is never edited, deleted, or overwritten. The first hosted develop run containing promotion completed successfully at `f0f5f12` on 2026-08-03 and Gitea -reported the tag-only job as skipped, accepting the non-tag permission boundary. The remaining acceptance gate is -a deliberate first version tag and inspection of its five release attachments. +reported the tag-only job as skipped, accepting the non-tag permission boundary. The remaining acceptance gate +was a deliberate first version tag and inspection of its five release attachments. That gate passed with the +lightweight `v0.1.0` tag at `5fe3cd6` on 2026-08-03: the tag build and promotion job completed successfully, and +the Gitea release carries the archive, archive checksum, build metadata, payload ledger, and smoke log. The Linux +CI/CD path is therefore accepted end to end. ## Dependency inventory diff --git a/docs/remake-architecture-and-roadmap.md b/docs/remake-architecture-and-roadmap.md index 9b2766e..f0ad7a4 100644 --- a/docs/remake-architecture-and-roadmap.md +++ b/docs/remake-architecture-and-roadmap.md @@ -1027,8 +1027,9 @@ do not mix mechanical moves with semantic changes. collisions fail without edit, deletion, or overwrite. Pure creation/resume/refusal regressions and workflow lint pass locally. The first hosted develop run containing this job completed successfully at `f0f5f12` on 2026-08-03 and the promotion job was skipped, accepting the non-tag permission boundary. The remaining gate - is a deliberately chosen first `v*` tag and inspection of the resulting release/archive/evidence; no tag is - created by this slice. + then passed with lightweight tag `v0.1.0` at `5fe3cd6`: its hosted build and promotion completed successfully, + and the resulting Gitea release exposes all five expected archive/evidence attachments. This accepts the Linux + CI/CD path end to end; future version tags use the same build-once/promote-on-success route. **Not cleanup targets:** generated `build/` output, the two intentional solution files, historical `docs/superpowers/` plans/specifications, and fidelity-specific complexity that is directly covered by the