Picked T732 back up after a prior chat session froze before saving its scope work. Verified nothing was lost platform-wide (checked handoff-10.md, LEGACY-10.md, memory-pipeline, Server/Admin own DBs - no trace existed), then redid the work fresh. Cross-checked Server[40]'s afternoon closes first (T730/T727/T740 closed, T736 reconfirmed, T735/T738 partial-fixed pending a delete primitive) and Admin[00]'s T739 close - per USR369 direction not to duplicate Server's active T034/T042/T573/T720 work. Live-tested web-fetch.php action=search (T730's subject) - confirmed fixed, 11 real multi-source results returned. Found ORIENT-REG.md's web-fetch.php status block was now stale (still said action=search STILL BROKEN) - applied SOP-GOVDIFF v1 method, corrected in place with full T730 fix detail and a pointer to the SOP, verified via read-back (byte match). Then answered T732's 4 open scope questions in SOP-GOVDIFF.md Part 2 (bumped v1.0 to v1.1): (1) scope = the 7 platform REG files, not per-system gov files; (2) rejected free-form-prose parsing (confirmed via direct sample these files are prose not markup) in favor of a lightweight inline GOVDIFF tag convention living inside the REG file itself, not a separate external mapping table that could itself drift; (3) on-demand only for v1, no scheduler exists yet; (4) reuse existing memory-pipeline + T-code infrastructure, no new dashboard tile. Both file writes (ORIENT-REG.md, SOP-GOVDIFF.md) verified via read-back diff before considering done. T732 moved from unscoped to scoped-and-ready-for-a-build-decision; build itself not started, would be Server[40] lane once USR369 confirms.