#49/#267 — both results, together as asked.

CARGO CHECK: GREEN. `cargo check -p spt-daemon --jobs 2` in .worktrees/49-267-obs (detached ba993b7a) under its own claimed pool todlando-49-267-obs. Finished dev profile in 32.10s, rc=0. This is the clean run on the FINAL tree — it includes the Q3 rewording and the send_deadline rename. The Rust I reported as written-but-uncompiled now compiles.

TRACEABLE-REQS: GREEN, rc=0, 0 FAIL, REQ-REFRESH-WAIT-ATTRIBUTION reads [OK] required: [doc, impl] stages: +doc +impl -unit -int. Two caveats you should have rather than not:

1. VERSION GAP, and it is the one that matters. I ran 0.4.1. Both ci.yml (line ~253) and golden.yml (~1414) pin WANT=0.2.0, and there is no 0.2.0 on this box — only 0.4.0 and 0.4.1 in ~/.local/bin. So this green does NOT predict the CI gate; it is a green from a different checker than the one that will judge the lane. Getting the pinned answer costs a clone of the private traceable-reqs repo at v0.2.0 plus a release build on this box, which hertz has just taken back for his L0/L1 work. Say the word and I will queue it behind him; I did not start it on my own.
2. Pre-existing note on the run, not mine: "2 tag-carrying file(s) not placement-judged (no grammar for the language, or the parse recovered from errors)". Unchanged by this lane.

THIRD CORRECTION, found by the gate and not by me. The registry TEXT of my own REQ still carried the old word: "the CAUSE THE CALLER KNOWS -- writer gone, stall evict, or detach". After the rename that sentence contradicted the code it governs — the requirement would have gone on promising a cause the implementation no longer emits, and the gate reads green either way because it counts tags, not agreement. Corrected in traceable-reqs.toml by replacement to name the send deadline the drain observed, with the same "not the writer's fate" clause the const's doc and the plan doc now carry. Re-ran the gate after the edit: still rc=0, still [OK]. So the three places that can state this cause — const doc, plan doc line 129, REQ title — now say the same thing.

That is the full set for the lane: Q3 wording trial-scoped, CLOSE_SEND_DEADLINE renamed with its doc, plan doc corrected, REQ text corrected, check green, traceable green at 0.4.1 with the pin gap stated. Nothing committed yet — the worktree is detached at ba993b7a and I have not made a commit. Tell me the shape you want (one commit or split) and whether you want the pinned-0.2.0 run first.

#299: nothing started, waiting on the operator pick you are relaying. #300: amended scope read, not started.