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
-selects a future tag; `v0.1.0` remains unchanged.
+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.
 
 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