#302 STAGING PREREQS (doyle rulings after ENLYZEAM probe). Handoff 3142753a VERIFIED (shas, stat, forced-3) and branch pushed to origin by me.
RULING A — PROFILE: the stageable binary must be a RELEASE build. The ENLYZEAM resident is release; a debug build inflates Rust-side CPU work (quinn/tokio/serde) and can manufacture the runtime-starvation mechanism STEP 1 is meant to discriminate. Rebuild 3142753a with CARGO_PROFILE_RELEASE_DEBUG=line-tables-only (no strip) so spt.pdb + net_diag_smoke.pdb still exist; same locked source, same pool. Re-run on the RELEASE artifacts: knob-unset seams, resume/classification units, smoke + forced parse under the pinned analyzer 6f36563c. Retain exe+pdb pairs + PE/PDB identity; post the same handoff shape (branch sha, release spt.exe sha256, fixture sha256, receipt path).
LEG B — ENLYZEAM-MATCHED OS PDBs: ENLYZEAM is Windows 10 22H2 build 19045.6466 (not HFENDULEAM's 26200). I am pulling its System32 DLL set to .spt/preserved/302/enlyzeam-19045.6466-dlls/ (ntdll, kernel32, KernelBase, iphlpapi, ws2_32, mswsock, NSI, dnsapi, rpcrt4, ucrtbase, msvcrt, sechost, advapi32, bcrypt, bcryptprimitives; SHA256SUMS.txt + SOURCE.txt beside them). Prepare matching PDBs from those PE identities via your existing local procedure, laid out exactly as SPT_NET_DIAG_SYMBOL_DIR expects, into .spt/preserved/302/enlyzeam-symbols/ together with the release spt.pdb. State the expected layout (flat vs symstore) and a manifest with GUID/age per PDB. If a DLL is missing from my pull, name it.
Order: B can run while A builds. No staging from you; staging window is operator-authorized.