Record dual-platform CI acceptance

docs/platform-portability.md

@@ -153,8 +153,11 @@ exactly two distributable archives:
 five-attachment boundary; detailed build metadata, payload ledgers, and logs remain inside each archive and in
 the retained workflow artifacts. The release notes will state that Linux received the dynamic package smoke and
 Windows received structural cross-target verification only. Source-only paired creation/resume/refusal tests
-pass. The first hosted develop run must still prove both build jobs green and promotion skipped before the user
+pass. The hosted develop run at `d657c63` completed both platform builds and correctly skipped tag promotion on
-selects a future tag; `v0.1.0` remains unchanged.
+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.
 
 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

docs/remake-architecture-and-roadmap.md

@@ -1085,15 +1085,17 @@ do not mix mechanical moves with semantic changes.
    completed both platform artifact jobs and skipped tag-only promotion, accepting the runner/toolchain/cache/
    build/upload path and the non-tag authority boundary. Slice 4 is now active.
 
-   **Slice 4 implementation completed 2026-08-03; hosted acceptance pending:** tag promotion now requires both
+   **Slice 4 hosted path accepted 2026-08-03:** tag promotion now requires both
    successful platform jobs and downloads their already-built artifacts into separate directories. The helper
    binds both archives to the same clean tag commit/RID, verifies their external hashes, compares external build
    metadata and payload ledgers with the copies inside each archive, requires Linux's dynamic smoke and Windows's
    AMD64/ABI/import report, and generates combined release checksums. Creation and retry expose exactly three
    public assets—Linux archive, Windows archive, and `RELEASE-SHA256SUMS`—while unexpected assets, release
    mismatches, and same-name/different-size collisions fail without mutation. Synthetic paired-artifact,
-   creation/resume/refusal, and workflow-dependency tests pass. The next gate is a hosted develop run with both
+   creation/resume/refusal, and workflow-dependency tests pass. The hosted develop run at `d657c63` completed
-   builds green and promotion skipped; only after that proof may the user deliberately select a future tag.
+   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.
 
    **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

docs/tools-reference.md

@@ -70,8 +70,9 @@ archive, the accepted Linux package smoke, and the Windows AMD64/ABI/import veri
 `RELEASE-SHA256SUMS` and publishes exactly three assets: the Linux `.tar.gz`, Windows `.zip`, and combined
 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 first hosted develop
+same-name/different-size collisions instead of editing, deleting, or overwriting them. The hosted develop run at
-run of this paired promotion contract remains pending; no new version tag is created as part of that proof.
+`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.
 
 | Tool | Purpose | Run | Reads → Writes |
 |---|---|---|---|