Skip to content

History / Manual Override

Revisions

  • docs: split the manual-override detection tree into its three stages Rendered, the single tree ran about five screens tall and you scrolled through blank space between subgraphs. Each stage is now its own diagram with an explicit hand-off node, so a stage fits on screen and the chain is still traceable end to end.

    @jrhubott jrhubott committed Aug 12, 2026
  • docs: add a Manual Override page with the full decision tree Manual override had no page of its own — it was spread across the Automation settings table, a Troubleshooting symptom section, the Venetian timeouts section, and the Custom Position priority rule. This gives it one home, built around seven diagrams with the detection ladder as the centrepiece, layered so the internals sit below a divider. Documents the input-sensor and input-template triggers for the first time; they shipped in v2.30.0 and appear in no settings table anywhere. Also documents the preemption rule, where an ACP-routed move is refused outright when a higher-priority handler is winning. Fixes two errors found while writing it: the Runtime Services example claimed a custom slot at priority 80 ties with manual override (the rule is strictly-above), and the Automation table called the override duration a minimum. First page in the wiki to use mermaid classDef; confined to this page.

    @jrhubott jrhubott committed Aug 12, 2026