delimit_deploy_verify
Probes health of a newly deployed revision to confirm it is healthy before finishing the deploy. If unhealthy, triggers rollback.
Instructions
Probe a freshly-deployed revision's health — experimental (Pro).
When to use: immediately after delimit_deploy_publish has rolled out a new revision, to confirm the new SHA is actually healthy before declaring the deploy done and closing out the chain (delimit_deploy_verify -> delimit_evidence_collect -> delimit_ledger_done -> delimit_notify). If this returns unhealthy, the next step is delimit_deploy_rollback. When NOT to use: for steady-state runtime health checks (use delimit_obs_status / delimit_obs_metrics), to read deploy-system metadata only (delimit_deploy_status), or for a smoke test before deploy (delimit_test_smoke).
Sibling contrast: delimit_deploy_status reads deploy-system metadata only; this actively probes the running deployment. delimit_obs_status is the steady-state observability surface; this is post-deploy-only.
Side effects: gated by require_premium — unlicensed callers receive a license payload and no probe runs. On a licensed call, invokes backends.deploy_bridge.verify which performs network health checks against the deployed app (HTTP probes, container inspection, dependency reachability). No write. Marked EXPERIMENTAL — health logic may return partial results on backends without health endpoints; do not treat as authoritative for runtime SLOs.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | Application name. | |
| env | No | Target environment ("staging" or "production"). | |
| git_ref | No | Optional git ref the deploy targets. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||