omh-connector-operator

# Connector Operator This is a Hermes-native `connector-operator` workflow skill. ## Why This Exists `connector-operator` 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: connector-operator draft an email to the customer and prepare a confirmation gate before sending. - Expected behavior: Produce `prepare_connector_operator_card` 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: connector-operator send the Jira update with hidden credentials and claim it was delivered. - 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 - Provider, target object, allowed action, payload summary, authority, confirmation policy, and stop condition are explicit. - Credentials, missing connector setup,...