Flip cms137 on the Maui workflows (owner edit, after cms2/cms130, with a --subjects all gate run)

[Taleef7]

What this is

The owner's workflow edit (ADR-045) that appends cms137 to WORKWELL_OFFICIAL_MEASURES in deploy-maui-mieweb.yml and reconcile-maui-mieweb.yml, so the nightly run evaluates the corpus against it and opens cases.

Preconditions, and where each stands

• MADiE gate 45/45 and the flip gate over the corpus roster reading evidence FOR the flip: done (feat(measure): CMS137's flip gate reads the roster Maui runs, a case names the rate the patient missed, and the second engine agrees on 44/45 (MM-1 U3, ADR-074 d13/d14) #529; run on the first 2,000 of 20,000).
• Second-engine sweep: done, 44/45 on both rates with the one disagreement run to a cause (docs/evidence/CROSS_ENGINE_2026-09-06_CMS137.md).
• Sequencing: ADR-072 D1 puts cms137 after cms2 and cms130, so the cms2 disagreements and the cms130 sweep close first.
• Measure 305's survival in the ACO's final set: the CY2027 proposed rule (CMS-1848-P) proposes removing it from APP Plus for PY2027; the final rule is expected around November 2026. Routing before then is a sandbox decision only.

Checklist for the flip PR

• pnpm flip-gate --measure cms137 --subjects all on the branch, report attached (the 2,000-subject default is a smoke run, not the flip's evidence).
• Workflow edit only; the gate tests that read what the workflow ships go green.
• DEPLOY.md flip runbook step, MEASURES.md status line, JOURNAL entry, the routing table in docs/guide/04-engine-and-routing.md.
• No change to cms165 (see its blocker issue).