omh-decision-recall

# Decision Recall This is a Hermes-native `decision-recall` workflow skill. ## Why This Exists `decision-recall` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. ## Do Not Use When - The request is already handled by a narrower explicit skill with stronger evidence. - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. ## Examples Good example: - Prompt: Show rejected decisions for this project before we choose an alternative. - Expected behavior: Produce `show_rejected_decision_recall` with required context, wrapper actions, and not-evidence boundaries. - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. Bad example: - Prompt: Claim the recalled rejected decision is an approved memory write or proof the replacement ran. - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. ## Completion Checklist - The query, scope, tags, stale policy, and match limit are explicit. - Only reviewed rejected candidates are returned; expired candidates stay excluded. - Recall output is not presented as approv...