v0.26.2

Dely 0.26.2 moves OMP Control from the waker to background wake. Before this release, OMP ran dely wait through a hidden waker terminal because its largest background-job timeout (3600 s) sat below the helper's 60-minute default deadline, so a long wait was killed before it ended.

• dely wait defaults to a 55-minute deadline (was 60). 3300 s sits under OMP's 3600 s job cap, so a long wait reaches the helper's own DEADLINE checkpoint instead of being killed by the harness. A killed job still wakes OMP, but with empty helper output and no log event — the shorter default is what keeps that empty wake from happening.
• OMP is controlWake: background. Its Control runs dely wait as a background job with the harness's largest timeout (3600 s); the README Control column carries that limit. No wait-bg, no notify, no pasted wake text on OMP.
• The waker stays for Codex, Grok, Antigravity and Pi, which cannot wake on background-job exit.

Verified live on the release head: an OMP Control ran a full delivery cycle to ACCEPT and push with background wake only, and the kill-before-deadline behaviour above was measured directly (~/dely-probe/checklist-omp-bg-1e894ad.md).

Known residuals: the 2026-10-11 decisions.md section still says the live cycle is "not yet measured" (it ran after that commit, on the same head); the probe's OMP Control ran on gemini-3.8-flash because Vertex refused the pinned Claude models; no real 3300/3600 s wait has been observed yet.

Decision record: docs/decisions.md, section 2026-10-11, closing the 2026-09-27 deferred item "controlWake: background for OMP".