Record hosted Windows artifact acceptance

docs/platform-portability.md

@@ -138,7 +138,9 @@ own manifest-keyed cache/workflow artifact. Windows installs Ubuntu MinGW-w64 GC
 and PE inspector, calls only `tools/build-windows-x64.sh`, and retains the ZIP plus its external hash, build
 metadata, payload ledger, and static verification report for 30 days. It has no secrets, Wine, EXE execution, or
 release authority. Source-only workflow regressions pin those rules and preserve the current Linux-only
-`publish-release` dependency; the first hosted dual-job develop result remains the acceptance gate.
+`publish-release` dependency. The first hosted dual-job develop run at `9d3ab30` succeeded on 2026-08-03: both
+platform artifact jobs completed and the tag-only promotion job was skipped. The Windows hosted artifact path is
+therefore accepted; dual-platform promotion is the remaining CI/CD slice.
 
 The next promotion slice will require both jobs, download both already-built archives, verify their commit/build
 evidence, and publish two distributable release assets:

docs/remake-architecture-and-roadmap.md

@@ -1073,7 +1073,7 @@ do not mix mechanical moves with semantic changes.
    stable, and an optional Windows-host run of the packaged EXE reported the 548-opcode/FFmpeg-ABI-3 smoke marker.
    Slice 3 is now active: add the read-only hosted Windows artifact job while retaining the accepted Linux job.
 
-   **Slice 3 implementation completed 2026-08-03; hosted acceptance pending:** the existing artifact workflow
+   **Slice 3 completed and hosted-accepted 2026-08-03:** the existing artifact workflow
    now has independent `ubuntu-latest` Linux and Windows jobs under inherited read-only contents permission.
    Windows provisions MinGW-w64 GCC/binutils, restores only its manifest-keyed editor/FFmpeg/template inputs,
    calls the accepted `tools/build-windows-x64.sh`, and uploads the ZIP, external archive hash, build metadata,
@@ -1081,7 +1081,9 @@ do not mix mechanical moves with semantic changes.
    authority. A core-gated source-only workflow regression pins that boundary and deliberately proves that
    `publish-release` still needs only `linux-release` during this slice. Acceptance requires the first hosted
    develop run to leave promotion skipped and complete both platform jobs; slice 4 then replaces the Linux-only
-   promotion contract with dual-archive verification and publication.
+   promotion contract with dual-archive verification and publication. The develop run at `9d3ab30` then
+   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.
 
    **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

@@ -57,7 +57,8 @@ FFmpeg archive and selectively installed release template. Linux uploads its `.t
 `BUILD-INFO.json`, `SHA256SUMS`, and `WINDOWS-VERIFICATION.json`; it does not execute the EXE. Both artifacts are
 retained for 30 days and failures retain bounded evidence for seven days. Both build jobs inherit read-only
 repository permission and have no secrets, private game corpus, or release/package publication authority. The
-first hosted dual-job result remains pending until this workflow change reaches `develop`.
+first hosted dual-job develop run at `9d3ab30` succeeded on 2026-08-03: both platform artifacts completed and
+the tag-only promotion job was skipped. This accepts the Windows artifact job and its non-tag authority boundary.
 
 Only a successful `v*` tag run enables the dependent promotion job. It downloads that same workflow artifact
 rather than rebuilding, checks out only the release tool, and receives job-local `releases: write` plus