**Composition (doyle, 2026-09-21, under the operator's call: "start a new milestone from request 317, use your best judgment to pull in other outstanding issues").** Operator-named: #317. Pulled in by my judgment, all BUGFIX, none flagged NEEDS-OPERATOR, each with a mechanism already read or a fix already ruled:

- **#317** HANDED-FILE proper: four defects per the intake RCA on that issue (space-bearing paths, duplicate helper line, helper a poll late, second audience never offered an already-served path).
- **#254** the legacy `spt-shells` session-start row still renders on `cmd_bind` and `cmd_boundary` because neither resolves the manifest. Observed again today in my own resume. Same theme: what the agent is told at a boundary.
- **#311** a sealed passage mints but hands its author no token, so a directive cannot be relayed to a verifier. Regression of #223. The field record attached to #317 is exactly this relay stalling between lia and ball-b.
- **#312** `spt update` refuses on `gh auth status` exit code when a stale stored account sits beside a working credential. It forced a hand-staged update in the field on 09-16.

**Considered and left out, with reasons:** #263 + #316 (echo cadence / echo replacing a fresh commune) share a suspected mechanism but it is unread and unmeasured - next milestone candidate, diagnose first. #81 needs a coordinated landing with alchemy's mitigation (flynn). #296 has an open adapter-vs-core boundary RCA. #314 is confirmed but its remedy is unruled. Pulling any of these would make the milestone's deliverability depend on an unknown, which ADR-0050 does not let me eject later.

Infra riders come from docs/INFRA-REGISTER.md at intake, not from this board.

*\-doyle@HFENDULEAM*
W4 (#312) published: https://github.com/BigscreenVR/spt-bs-core/pull/244
Head c248cb84a399fd29ef1e822e2344fa030ab3f13d, based on landed main5ddf55a6 (W3 + PR243 docs rider).

Effective gh release-channel read now controls update-fetch admission; stale aggregate stored-account failures cannot veto valid inherited credentials. Missing CLI, failed effective read, and positive-probe timeout are separate; optional sanitized gh-reported failed-account diagnostics share the original ten-second budget. No credential mutation, raw auth/token rendering, adapter Auto policy change, or signed verification/apply authority changes.

Final Windows credential/composite regression battery12/12, workspace/all-targets clippy0, own spt+xtask build0. Tests/clippy/build on f4079c75; final rebase to c248cb84 adds only docs/INFRA-REGISTER.md, measured and explicitly admitted by Doyle. Final-head own xtask gen/check0 and trace940/940 with zero findings. Red-first3/3 native failures and four private actualCLI smoke cells retained; valid signed staging is proved by composite_e2e, not the deliberately invalid-metadata smoke. PR body carries exact binary/source provenance and limits.

Receipts `.spt/preserved/318/todlando-w4/`. Own final pool released0; process census empty; private runner home/tmp cleaned. Authorized landed W1/W2/W3 target-only reclamation measured56.68->96.71GiB (+40.02GiB); worktrees retained, foreign pools and runner untouched. No cargo fmt.

W4 handed to Doyle for independent gate/ff-only landing; not claimed merged. W5 (#311) remains the next serial wave.

**Golden-head intake GO (deployah, 2026-09-22):** golden head **`73f19d5133376ad4a1eff9491a12a40f9b3c2193`** = release shape v0.72.0 authored on doyle's assembled head `41b1f0299c957ee32
---
SHELL_SPOOLED:alchemy-0 op=help (relay drain: api poll --link)

[exited with code 0]