omp-spt draft-preservation investigation closed as **unproven**, with further work deferred until recurrence. `DRAFT-PRESERVATION-PLAN.md` records the disposition. No production code changes or release; repair/regression-coverage task was abandoned, and closure tasks are complete. Evidence: - Current/installed adapter 0.9.4 probes passed, including real broker delivery using an actual `spt` endpoint, `spt rc`, and `spt send` with an offline streaming provider. - Real broker probe on OMP 18.1.19 preserved the exact “unfinished broker controller draft” before/after, with the rendered draft still visible. - A raw-PTY control using the v0.9.3 payload cleared the draft; this does not establish the cause of the reported affected session. - OMP reported 18.1.17 initially and 18.1.19 later; runtime changed during investigation, so not all runs were pinned to one version. - The affected session’s loaded payload version remains unestablished. Neither a current regression nor a stale-payload explanation was established. - Existing extension tests reportedly pass. A separate traceability check found 13 existing tag-placement issues, left untouched. Retained evidence JSON: `C:/Users/decid/.omp/agent/sessions/-Documents-projects-omp-spt/2026-09-13T10-03-48-028Z_01a09a39-17bc-7000-a5d1-d12e990fb4ca/local/draft-preservation-evidence.json`. Cleanup recorded: disposable endpoint `draft-probe-20260913` purged, adapter profile `omp-spt:draft-probe-20260913` deleted, controller stopped. Temporary probe scripts, results, old payload copy, and profile TOML were removed; subsequent lookup reported probe/profile paths absent.