v3.1.0

A cleanup release, headlined by the root-cause fix for the OMP launch crash (#72).

• Removed the custom-editor ownership + animated rainbow highlight (#101). The keyword trigger no longer owns the host editor, so there's no WorkflowEditor.render() to throw — regardless of which editor build the host bundles. 3.0 only mitigated this with a defensive fallback; 3.1 removes the coupling at the root. The keyword trigger itself is unchanged; the rainbow highlight and Backspace-one-shot-disarm are gone (under 3.0's authorize-not-force semantics, their "you're about to force a workflow" warning purpose was obsolete).
• Merged /workflows-progress-max into /workflows-progress max <N> (#102) — one command instead of two.
• Library API note: removes the internal exports WorkflowEditor / RAINBOW / colorizeWorkflow / tokenizeAnsi (rainbow-rendering internals; no user-facing behavior change).

Verified end-to-end on real Pi (0.80.10): the extension loads after the editor removal, the workflow tool runs, and the keyword trigger arms. Requires pi ≥ 0.80.8.

---

What's Changed

• refactor!: drop custom-editor ownership + rainbow highlight (root-causes #72/#64) by @QuintinShaw in #101
• feat: merge /workflows-progress-max into /workflows-progress by @QuintinShaw in #102
• chore: tidy two leftovers from the editor-ownership removal (#101) by @QuintinShaw in #103

Full Changelog: v3.0.0...v3.1.0