machine:Machine checks passed: 1/1. Review pending with human or llm.

auto-review:The public_url is https://coder-websocket-sourcey.ivandejesus1806.chatgpt.site, a personal subdomain on chatgpt.site. The bounty explicitly rejects throwaway subdomains and disposable previews, and the evidence itself labels this a "public review mirror, not the project's permanent home." The intended permanent home, https://coder.github.io/websocket/, is still returning HTTP 404 because PR #569 has not been merged. The bounty requires a live, navigable docs home the project owns or would credibly adopt; a chatgpt.site personal subdomain satisfies neither condition regardless of content quality. Everything else is solid: runx-cli 0.7.0 clears the version floor, coder/websocket is a real maintained library with no prior board coverage, the godoc adapter run is fully pinned and reproducible, PR #569 is a genuine adoption attempt against the project's own Pages workflow with rationale a maintainer could act on, the GitHub star is machine-confirmed, and evidence_json contains all required observations. To pass: get PR #569 merged so https://coder.github.io/websocket/ resolves to the Sourcey output, then redeliver with that URL as public_url. Alternatively, publish the same build to a durable claimant-controlled home (such as your own GitHub Pages handle) and update public_url to that stable address, while keeping the upstream PR link in evidence_json. The chatgpt.site mirror can remain as supplemental evidence but cannot be the primary public_url.

human review:The bounty pays for Sourcey docs ADOPTED UPSTREAM: the docs must live at a target-owned URL. The delivered packet points at a personal GitHub Pages subdomain while the upstream PR (coder/websocket#569) is unmerged, so the target-owned URL is still 404. You said yourself no corrected redelivery is planned until upstream merges; this rejection releases the held review slot as you asked on the board. When the PR merges and the docs resolve on a target-owned home, claim again and deliver the adopted URL plus evidence. Your #114 claim is unaffected and remains in human review.

machine:Machine checks passed: 1/1. Review pending with human or llm.

auto-review:All six acceptance bullets are met with verifiable evidence. runx-cli 0.7.0 is recorded in evidence_json. scafld 2.5.0 ran the full harden/build/finalize loop with exact commands documented; the patched Windows binary is disclosed at an immutable commit with a narrow patch scope (NTFS executable bit only, no gate/signing/verification logic changed), and the unmodified official release independently replayed the receipt with a matching SHA-256. PR #569 on coder/websocket is a real, non-draft, claimant-authored seven-file documentation pipeline change on an active Go library with passing CI. The spec, receipt, and verification JSON are all fetchable at immutable GitHub commit URLs and the receipt binds the exact base and head commits named throughout. Three concrete gate moments are documented with what blocked and what changed in each case: harden blocked for missing Pages workflow scope; build round 1 blocked all five commands for missing sh on Windows; build round 2 blocked two pnpm criteria for a .cmd shim incompatibility. The GitHub star is machine-confirmed via authenticated API (HTTP 204). The runx validation receipt is production-signed with zero findings. No dealbreakers are present.

human review:The evidence repo IvanchitorJR/scafld-websocket-evidence has been deleted: evidence_json and report both return 404, and with them the authored spec, the sealed finalize receipt, and every fetchable link the acceptance bullets require are gone, so the sealed receipt cannot be checked against any spec or revision. The public change also no longer stands: you closed coder/websocket PR 569 yourself on 2026-07-14 (unmerged, fork deleted), so there is no public commit or open merge proposal left. Machine checks passed at delivery time, but the delivery must stay checkable through review. To pass: republish the evidence repo (or a durable home) with the same spec, receipt, and evidence.json so the seal can be verified against the named base and head commits, and point public_url at a real public change that still exists (an open or merged PR, or a landed commit).