comment #272
**GOLDEN-HEAD INTAKE (deployah, 2026-09-08) — #272 WEBSERVE.** Assembled head `fd296557`, shaped head `2f422990` (the sha the golden ref carries and the tag will point at).

**1. Greenlit-form parity: PASS — checked against the greenlight SNAPSHOT, not a reconstruction.** Baseline = this issue's INTAKE comment of 2026-09-06T10:24:57Z: ride #248 #249 #246 #265 #268 #147 #266, #17 as the closing rider, #148 detached to BACKLOG, #271 SHELVED. Live board at intake: all eight riders present at `state: ACCEPTANCE`; #148 still BACKLOG, #271 still SHELVED — both greenlight-time rulings, not drops from the greenlit set, so neither needs a drop discharge. **Zero requests dropped, zero requests added.**

The riders the gater named are NOT added requests and need no discharge, recorded here so the reading is on the record rather than in chat: XFER retirement was ruled AT greenlight (round-2 comment, operator AGREE; the intake comment carries it as a #246 close rider) and rides at `21c14703` + `fd296557`; the IR-76 driver pre-flight was likewise a greenlight close rider and rides at `8d7b8289` + `7c435564`; hertz's two W3 drift-gate riders are test/CI material inside W3, not Requests.

**2. Release shape: the head was NOT release-shaped; the driver shaped it before the golden ref (IR-54).** Measured at `fd296557`, not assumed: `Cargo.toml` first version line read `version = "0.67.1"` and `CHANGELOG.md`'s first section heading read `## [Unreleased]`. Version material authored on top: 0.68.0, Cargo.lock refreshed workspace-only (14 first-party line pairs by diff, zero third-party pins touched), `## [0.68.0]` section, regenerated docs, `xtask check` OK. Bump level justified by observable behavior, not by wave count: `/` now redirects to a node-prefixed index, docs gain a canonical `/<node>/docs/` with the bare paths kept as aliases, every non-empty send carries new envelope material, and an access surface is retired.

**3. Changelog audited against the COMMIT RANGE, mechanically (IR-28) — and the audit found four gaps the milestone narrative would not have.** `git log v0.67.1..fd296557` (57 commits, 21 in the feat/fix class) was matched row by row against the notes. Four bugfixes ride this range from outside milestone #272 and had no changelog line: **#277** (message/activity positions restarting once a log passes 256 KB), **#276** (the automatic summary overwriting an agent's own unread saved context), **#279** (an engine-room probe line printed on a machine with no engine room), **#280** (relay-delivered messages missing from incoming history — already covered). Each now has a user-facing line. The remaining unmatched rows are intra-wave fixes to code that first ships in this release, and are accounted for as such.

**4. Counter and compatibility, established at the explicit sha before the run.** Next release counter = **104**, decoded from v0.67.1's published signed metadata (`version: 103`, `product_version: 0.67.1`), not recalled. Update-set compatibility constants unchanged at the candidate, proven by diff: `BROKER_RESOURCE_ABI = 1` and `brain_ipc_version: 1` both equal the published envelope's values, and `crates/spt-daemon/src/release.rs` changes by exactly one line in the range (a helper's visibility), leaving `SUPPORTED_PLATFORMS`, `KNOWN_TARGET_TRIPLES`, `BUILTIN_RELEASE_KEYS` and `DEFAULT_CHANNEL` untouched.

**5. Never-executed cells: the hand-off arrived without the list, was bounced rather than filled here, and the artifact was then delivered and verified.** Branch `never-executed-272` @ `0a122453`; the file's sha256 matches the gater's stated hash byte-for-byte. **172 test cells added since the last golden (`04e32c8c`, v0.67.1); every one of them has its FIRST CI EXECUTION at this golden run** — 112 have ridden a thin GitHub job, 60 have executed only in local gate batteries and rigs, and none of the 172 has ever run in a golden workflow. Triage consequence, stated before the run rather than after a red: a failure on any of these is structural-until-shown-otherwise, mechanism first, no rate argument and no same-sha rerun.

Golden CI runs on the shaped sha next; the run's id will be pinned by full sha at push time.

*-deployah@HFENDULEAM*