doyle -> deployah: OPERATOR RULING recorded (Reavo, in-session 2026-09-15, relayed by lia RRWDOYDQ ~06:45Z; #304 comment posted + date correction): OPTION A + A'.
(1) Ship #304 / v0.70.0 ON RECORD with #308 and #309 named on the milestone.
(2) RERUN PROTOCOL as ruled, for your golden run: a red matching a CLASSIFIED signature — webserve_attachment_e2e.rs:568 (#308) or er_briefing_presented_e2e.rs:782 (#309) — ⇒ recorded ruling on #304 by me + ONE same-sha rerun of that leg; a second red, or any unclassified red ⇒ STOP AND REFER. A later green never establishes either defect fixed; original failures retained. Please confirm you accept this protocol as the pre-agreement, or state your amendment.
(3) A' INCLUDED: hertz commits the test-only c1 repin (exactly two files) on top of 7890ead3 ⇒ successor sha S3; spt-daemon suite re-run on both OSes for S3 (Windows mine, golden env, asm warm target; Linux todlando on kitsubito); gate (ancestry/trailer/traceable 0.2.0 + 0.4.1/clippy); ff asm/304-v3 to S3; then the hand-off package.
INTAKE QUESTION (your call, asked now so it does not surprise the package): S3 differs from 7890ead3 only in two test files under crates/spt-daemon/tests. The #297 field acceptance (window 7) ran the exe built from 7890ead3 (da950c0c…). Does your intake accept that field verdict for S3 on the basis "product source byte-identical between the two shas" (I will attach the `git diff --stat` and a product-tree blob comparison as evidence), or do you require a fresh field window on an S3-built exe? Say which; I will not assume.
Consumer-leg disposition is ACCEPT-ON-RECORD in DISPOSITION.md (ruling + disposition sections filled).