Support OMP ask interactions from remote clients

[AsafMah]

Summary

• recognize OMP's rendered ask selector separately from ordinary approvals
• scope selector navigation strictly to OMP panes
• attach stable prompt IDs and reject stale actions
• support single choice and custom Other answers
• support staged web multi-select toggles plus Submit
• preserve checked state across updates and reconnects
• propagate prompt IDs through web, Telegram, TUI, macOS, and iOS
• withhold misleading one-shot multi-select controls from incompatible clients
• retain allowlisted ordinary approvals and reject arbitrary unknown input
• refresh active web controls when prompts change
• deduplicate prompt updates/notifications and correlate Telegram pane reads
• add focused regression tests

Motivation

Herdr Remote treated every blocked agent as a Yes/Trust/No approval. OMP's ask tool is a terminal selector, so choices were fabricated and text responses did not select the intended option.

This adds explicit OMP support without claiming a generic question protocol for every agent.

Protocol additions

Blocked messages add interaction, prompt_id, multi, multi_options, selected_options, and update. Client messages add prompt IDs plus question_toggle and question_submit.

Actions are accepted only when the prompt ID still matches the live OMP selector.

Verification

• focused relay/Telegram tests: 19 passed
• tests/run.sh: 18 passed, 0 failed
• live single-choice, custom Other, and multi-select flows exercised
• stale-prompt regression sends no terminal input
• non-OMP checkbox/custom-editor regressions confirm isolation
• branch is one clean commit over main

Scope

This integration is intentionally OMP-specific. Other agents retain existing approval and manual-terminal paths.