omh-automation-blueprint

# Automation Blueprint This is a Hermes-native `automation-blueprint` workflow skill. ## Why This Exists `automation-blueprint` exists so Hermes can make recurring operational work feel native and scheduled without OMH becoming a hidden cron runner, transport bot, source retriever, or executor. ## Do Not Use When - The user needs a one-off report or deck; use `report-package` or `materials-package`. - The user asks to review incident metrics once; use `reliability-review`. - The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted. ## Examples Good example: - Prompt: automation-blueprint every weekday run an uptime check and send a Slack digest only if status changes. - Expected behavior: Prepare hermes_ops_blueprint/v1 with schedule intent, Slack delivery policy, silence rule, research/report skills, missing evidence, and next confirmation. - Why: The request is recurring, delivery-shaped, and must stay prepared until host automation and gateway delivery are observed. Bad example: - Prompt: automation-blueprint prove the Slack digest was delivered this morning. - Expected behavior: Ask for observed Hermes/gateway delivery evidence or report the delivery as not_observed instead of claiming it happened. - Why: A blueprint can prepare the scheduled operation, but it cannot prove runtime execution or delivery. ## Completion Checklist - Confirm the workflow target, evidence boundary, and stop condition are...