omh-meta-router

# Meta Router This is a Hermes-native `meta-router` workflow skill. ## Why This Exists `meta-router` exists to turn a leading /omh command into a live catalog lookup: it reasons over the imperative task, selects or chains concrete workflows, and keeps the decision inside the observed/prepared evidence boundary instead of guessing from memory. ## Do Not Use When - The /omh token is not the leading command token. - The message is a bare picker alias or an OMH catalog/entrypoint question — those belong to oh-my-hermes. ## Examples Good example: - Prompt: /omh migrate this service off the deprecated API and add tests - Expected behavior: Consult `omh recommend` on the remainder, then chain the recommended plan and executor workflows with explicit observed-vs-prepared evidence boundaries. - Why: A leading /omh command with an imperative remainder is a meta-routing request that reasons over the live catalog rather than a memorized list. Bad example: - Prompt: omh add dark mode - Expected behavior: Do not meta-route; a bare `omh` alias without a leading slash command is a picker/other-lane signal. - Why: Meta-routing triggers only on a leading /omh or ./omh command token, not on a bare alias. ## Completion Checklist - The selected workflow, confidence reason, evidence boundary, and user-facing next action are named. - Low-confidence or conflicting signals return a picker or clarification instead of forced routing. - Catalog answers are rendered without shell approval whe...