run

/flow:run — single-shot trigger executor

When a FlowTrigger's target needs to run NOW (manual invocation, loop iteration, hook fire), /flow:run trigger <id> is the entry point. It validates the trigger against safety policy, checks concurrency, and dispatches the target command exactly once.

Required Skills

• trigger-policy — enforce mode (every invocation).

Pre-flight

ENABLED=$("$(__fr="${CLAUDE_PLUGIN_ROOT:-}";[ -x "$__fr/bin/cascade-resolve.sh" ]||__fr=$({ echo plugins/flow;ls -d "$HOME"/.claude/plugins/cache/synapti-marketplace/flow/*/ 2>/dev/null|sort -Vr;echo "$HOME/.claude/plugins/marketplaces/synapti-marketplace/plugins/flow"; }|while read -r __p;do [ -x "${__p%/}/bin/cascade-resolve.sh" ]&&{ echo "${__p%/}";break;};done);echo "$__fr")/bin/cascade-resolve.sh" \
  --default "false" '.flow.triggers.enabled')
[ "$ENABLED" != "true" ] && { echo "flow.triggers.enabled is false"; exit 0; }

Subcommand: /flow:run trigger <id>

1. Read .flow/triggers/<id>.trigger.yaml. Error if not found.
2. Check metadata.enabled: true. Error if disabled.
3. Invoke Skill(trigger-policy) in enforce mode. Abort on violation (Tier 3 deny, recursion deny, etc.).
4. Check concurrency.policy:
   • skip_if_running (default) — if a previous run for this trigger is in flight (check .flow/runs/ for runs with metadata.trigger= and state.status=active), exit 0 with a notice.
   • queue — queue the run (currently logs a journal artifact; full queue semantics not implemented).
   • cancel_previous — find any in-flight runs and transition them to cancelled before starting.
5. Set env var FLOW_TRIGGERED_RUN=true (target commands consult this for recursion policy enforcement).
6. Invoke target.command from the trigger YAML.
7. After target completes, append a trigger-fired artifact to the linked decision journal.

Recursion enforcement

When FLOW_TRIGGERED_RUN=true:

• The target command's pre-flight check refuses to create / enable / modify triggers (unless recursion_policy.triggered_runs_may_* is true, which requires explicit AskUserQuestion at trigger-creation time).
• The target command's tier classification has merge and release hard-overridden to confirm regardless of trigger settings.