opschain admin platform resume

Included from Basic tier

One verb, two postures:

• Bare (no flags) — lifts the estate-wide system quiesce via the v2 PlatformService.ResumeSystemQuiesce call: the write barrier reopens, schedulers and trigger firing restart, and both planes take work again. It also recovers an abandoned drain — a quiesce whose command was interrupted before the barrier closed.
• --plane <runners|agents> — resumes that halted plane via the v2 PlatformService.ResumePlatform call. A halt resume is deliberately narrow: it is per-plane (a full lockdown takes two resumes) and must name the active posture row it lifts with --posture <id>, so a resume drafted against a posture that has since been replaced is refused as stale rather than silently lifting a newer halt. The posture id comes from the halt's output or from admin platform status.

Flags

Flag	Meaning
--plane <plane>	Halted plane to resume: runners or agents. Omit (together with the posture flag) to resume a system quiesce instead.
--posture <id>	The active halt posture row id, from halt output or platform status (required with --plane, refused without it).
--server <url>	Server base URL (default: the active context / OPSCHAIN_SERVER).
--auth-token <token>	Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login).

Output is the server's response document — JSON, or YAML under -o yaml.

Exit codes

Code	Meaning
0	Resume applied.
1	Request failed, the server refused (e.g. a stale posture id), or the token was rejected.
2	Usage error — an inconsistent flag pair, or no server/credential resolvable.

Named errors

• --posture names a halt posture row and needs --plane; the system quiesce resume takes no flags — exit 2.
• resuming a halted plane must name its active posture row — pass --posture <id> (from halt output or 'admin platform status') — exit 2.
• a server is required — pass --server <url>, set OPSCHAIN_SERVER, or 'opschain context use <name>' — exit 2.
• this command needs a login or an admin token — run 'opschain login', pass --auth-token, set OPSCHAIN_ADMIN_TOKEN, or store one with 'opschain admin login' — exit 2.
• the server rejected the credential — run 'opschain login' again, or check the admin token — HTTP 401 (exit 1).

Examples

Lift a system quiesce:

opschain admin platform resume

Resume a halted runner plane:

opschain admin platform resume --plane runners --posture 01999b2c

See also

• opschain docs cli/admin-platform — the quiesce this lifts, documented on the group page.
• opschain docs cli/admin-platform-status — find the active posture row.
• opschain docs cli/admin-platform-attempt — per-attempt dispositions for work suspended during a halt.