From 0926125cbd53be1edfd5775b28c17ea0d8e085d4 Mon Sep 17 00:00:00 2001 From: gamer147 Date: Mon, 3 Aug 2026 23:08:29 -0400 Subject: [PATCH] Close out dual-platform release CI --- docs/platform-portability.md | 5 +++-- docs/remake-architecture-and-roadmap.md | 15 +++++++++------ docs/tools-reference.md | 5 +++-- 3 files changed, 15 insertions(+), 10 deletions(-) diff --git a/docs/platform-portability.md b/docs/platform-portability.md index 266eadf..7aaa110 100644 --- a/docs/platform-portability.md +++ b/docs/platform-portability.md @@ -156,8 +156,9 @@ Windows received structural cross-target verification only. Source-only paired c pass. The hosted develop run at `d657c63` completed both platform builds and correctly skipped tag promotion on 2026-08-03, accepting the paired non-tag path. Its core job initially failed before checkout on a transient runner DNS lookup for GitHub, then passed unchanged on retry; this was infrastructure availability rather than a -validation failure. The user must still select a future tag for the end-to-end release proof; `v0.1.0` remains -unchanged. +validation failure. The lightweight `v0.2.0` tag at `93d8236` then completed both platform jobs and promotion on +2026-08-03. The resulting Gitea release exposes exactly the Linux archive, Windows archive, and +`RELEASE-SHA256SUMS`, accepting the dual-platform CI/CD path end to end; `v0.1.0` remains unchanged. Code signing, an installer, Windows-on-Linux execution, and retroactively modifying the accepted Linux-only `v0.1.0` release are outside this effort. A future signing slice can use `osslsigncode` and protected credentials diff --git a/docs/remake-architecture-and-roadmap.md b/docs/remake-architecture-and-roadmap.md index 2701116..9a890eb 100644 --- a/docs/remake-architecture-and-roadmap.md +++ b/docs/remake-architecture-and-roadmap.md @@ -1094,13 +1094,16 @@ do not mix mechanical moves with semantic changes. mismatches, and same-name/different-size collisions fail without mutation. Synthetic paired-artifact, creation/resume/refusal, and workflow-dependency tests pass. The hosted develop run at `d657c63` completed both platform builds and skipped promotion as required; core validation also passed unchanged after retrying - a transient pre-checkout runner DNS failure. The remaining gate is a future tag deliberately selected by the - user. + a transient pre-checkout runner DNS failure. The user then selected lightweight tag `v0.2.0` at `93d8236`; + both platform jobs and promotion completed successfully on 2026-08-03, and the resulting release exposes + exactly the Linux archive, Windows archive, and `RELEASE-SHA256SUMS`. This accepts the Windows CI/CD effort + end to end. - **Completion gate:** one deliberately selected future tag produces a single Gitea release containing the - Linux `.tar.gz`, Windows `.zip`, and combined archive checksums; both archives bind to the tag commit, Linux - retains its dynamic packaged smoke, Windows passes all structural PE/payload gates, and neither platform job - receives release-write permission. Signing, installers, Wine, Windows runners, and mutation of `v0.1.0` remain + **Completion gate passed with `v0.2.0` on 2026-08-03:** one deliberately selected tag produced a single Gitea + release containing the Linux `.tar.gz`, Windows `.zip`, and combined archive checksums. Both archives bind to + the tag commit, Linux retains its dynamic packaged smoke, Windows passes all structural PE/payload gates, and + neither platform job receives release-write permission. Signing, installers, Wine, Windows runners, and + mutation of `v0.1.0` remain out of scope. **Not cleanup targets:** generated `build/` output, the two intentional solution files, historical diff --git a/docs/tools-reference.md b/docs/tools-reference.md index 339ab6c..ca56625 100644 --- a/docs/tools-reference.md +++ b/docs/tools-reference.md @@ -71,8 +71,9 @@ archive, the accepted Linux package smoke, and the Windows AMD64/ABI/import veri checksums. Detailed evidence remains inside each archive and in retained workflow artifacts. A retry resumes a matching partial release and uploads only missing files; it refuses mismatched releases, unexpected assets, or same-name/different-size collisions instead of editing, deleting, or overwriting them. The hosted develop run at -`d657c63` completed both artifact jobs and skipped tag promotion as required on 2026-08-03. No new version tag -was created as part of that proof. +`d657c63` completed both artifact jobs and skipped tag promotion as required on 2026-08-03. The subsequent +`v0.2.0` tag at `93d8236` completed both builds and published exactly the two archives plus +`RELEASE-SHA256SUMS`, accepting the promotion route end to end. | Tool | Purpose | Run | Reads → Writes | |---|---|---|---|