deps-runner
Purpose
Dependency-PR verification and merge pipeline, partitioned into 6 sequential ICM stages:
scan/context → preflight baseline → risk-eval (single cohesive stage, ALL groups) →
build-test → merge-decision → report. Each stage runs in isolated context; the critical
judgement (risk evaluation) gets a clean-context stage of its own. Behaviorally equivalent
to the monolithic deps-runner skill, just stage-partitioned.
This skill runs in the OPERATOR session and owns its worker lifecycle. Stages that
require a repo environment (preflight, build-test) spawn and drive a repo devbox worker via
the gateway worker API (see pylot-cli skill, § Workers). Stages that only need gh CLI
(scan-context, risk-eval, merge-decision, report) run inline in the operator session.
This procedure is SEQUENTIAL. There is NO fan-out and NO parallel Task launches. Risk evaluation runs as ONE stage over every dependency group — never one subagent per group. The ICM win here is clean-context isolation of the judgement step plus resume-from-stage, not parallelism.