Add outcome contracts for v0.9

plugins/vibeflow/skills/vibeflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vibeflow
-description: Audit and repair exported n8n workflow JSON with deterministic safety and contract checks. Use when reviewing AI-generated or customer-facing n8n workflows before deployment, investigating Vibeflow VF000-VF009 findings, adding kill switches or human handoffs, checking secrets, retries, and webhook exposure, or preparing workflow changes for CI and pull requests.
+description: Audit and repair exported n8n workflow JSON with deterministic safety and outcome-contract checks. Use when reviewing AI-generated or customer-facing n8n workflows before deployment, investigating Vibeflow VF000-VF013 findings, adding kill switches or human handoffs, checking secrets, retries, webhook exposure, money or customer side effects, recovery paths, or preparing workflow changes for CI and pull requests.
 ---
 
 # Vibeflow
@@ -19,7 +19,7 @@ Use the CLI as the source of truth. Do not infer that a workflow is safe from it
    For a released version without a checkout:
 
    ```bash
-   npx --yes github:domfelipe/vibeflow-n8n#4998605ed7dc12b9b867d69d7005d25778c7e109 check path/to/workflow.json
+   npx --yes github:domfelipe/vibeflow-n8n#v0.9.0 check path/to/workflow.json
    ```
 
 3. Read [references/policies.md](references/policies.md) when interpreting or repairing a finding.
@@ -32,6 +32,8 @@ Use the CLI as the source of truth. Do not infer that a workflow is safe from it
 - Never copy literal credentials into a workflow to silence `VF001`.
 - Never disable `VF006` for customer-facing agents without explicit user approval; an off switch must block inference and all AI responses.
 - Treat static analysis as a preflight, not proof of runtime correctness.
+- Treat `VF010` and `VF011` as outcome risks, even when the underlying node type is ordinary HTTP, database, or messaging.
+- Do not claim an outcome contract enforces runtime authorization, limits, audit durability, or recovery; verify those separately in the executing system.
 - Prefer fixing a shared upstream node over duplicating guards across branches.
 - Keep fixes local to the exported workflow until the user authorizes deployment.
 

plugins/vibeflow/skills/vibeflow/references/policies.md

@@ -12,5 +12,11 @@
 | VF007 | warning | AI Agent without a reachable external handoff action | Add a downstream ticket, chat, email, or equivalent human escalation action. |
 | VF008 | warning | Missing or excessive execution timeout | Set the workflow timeout between 1 and 3600 seconds. |
 | VF009 | warning | Unsafe retry policy | Add idempotency, bound attempts, and configure backoff. |
+| VF010 | error | Money or privileged action lacks verified policy evidence | Declare the action and connect dominating approval, durable audit, atomic idempotency, limits where applicable, failure notification, and recovery. |
+| VF011 | warning | Customer communication or destructive write lacks an outcome contract | Declare the impact and connect durable audit, atomic idempotency, failure notification, and recovery evidence. |
+| VF012 | warning | Connected error path terminates silently | Route the action's error output to a recognized operator alert, ticket, incident, or escalation node. |
+| VF013 | warning | High-impact write has no recovery contract | Declare compensation, rollback, or replay and reference the implementing node. |
 
 Configuration changes severity or domain vocabulary; it does not prove the suppressed risk is safe. Keep waivers visible in `.vibeflow.json` and explain them in the pull request.
+
+Outcome contracts are static evidence. Runtime systems must still authorize approvers, enforce limits and counterparties server-side, create durable audit entries before acting, deduplicate atomically, and test recovery behavior.