omh-deliverable-package

# Deliverable Package This is a Hermes-native `deliverable-package` workflow skill. ## Why This Exists `deliverable-package` 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: deliverable-package turn this research into PPT and PDF with attachment status. - Expected behavior: Produce `prepare_deliverable_package` 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: deliverable-package claim the PDF was attached without observed file evidence. - 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 deliverable type, audience, source inputs, QA ladder, and delivery boundary are named. - Prepared generation, generated file, render QA, approval, attachment, and delivery are separate state...