stado service

Invocation

stado service <COMMAND>

Purpose

Manage the services registry hosts run: list, status, restart, adopt, retire, deploy, logs, env

Required inputs and options

This command has no command-specific inputs or options.

Output and state effect

This command group selects one of the subcommands listed below; use its exact child invocation to perform an operation.

Refusals

Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.

Subcommands

directory — Where a service is reachable from here, and who may use it
catalog — The preconfigured Wisent services, ready to deploy by name: no declaration to write, no flags to know. `service deploy <name>` and `service ensure <name>` resolve these when nothing else declares the unit
list — Every registry-managed service across all hosts, with its state
bootout — Boot one exact launchd label or systemd unit out of its system or user scope
reap —
watch-spawn — Sit on HOST and name the parent of the next process matching a program, while that parent is still alive
label-print — Ask the host init system what it holds under one named unit
verify — Go to each consumer and check the endpoint it is told to use, and that the thing answering is the service that was declared
converge — Is the host running the version the registry declares for it?
onboarding-catalog — Registry-managed services carrying Echo onboarding product metadata
status — One service's state everywhere it is managed
refresh-image — Put one unit back on the file its `ProgramArguments` name, and prove it landed
repair-runner-runtime — Restore upstream signed macOS GitHub runner apphosts without restarting
restart — Restart one managed unit, without a full host-recovery pass
update — Move an already-managed service onto a new artifact version
release — Install and activate one service release, rolling back on failed readiness
show — What a managed unit actually runs: its program, arguments and unit file
stop — Stop one managed unit, including a process the unit no longer owns
secret-sync — Synchronize one Skarbiec field into a service's runtime env file
file-sync — Synchronize one local file into a managed service's target home
file-fetch — Copy one file OUT of a managed service's target home, byte-exact
env-set — Replace one key in a managed runtime env file or systemd definition
env-unset — Remove one key from a managed env file or systemd definition
env-show — Read a managed service's owner-controlled env file, duplicates and all
endpoint-check — Does this unit's env file agree with what is actually listening?
serving — Is the DECLARED unit the process on its own port?
grant-sync — Reconcile one Skarbiec consumer grant with an existing owner-only token file
token-file-sync — Write one Skarbiec item field into an owner-only raw bearer file
auth-check — Verify a managed service's bearer against a read-only loopback endpoint
adopt — Bring an existing launchd/systemd unit under management
onboarding — Attach central onboarding product metadata to a managed service
retire — Remove a service from management: bootout/disable and forget
handoff-release-control — Hand a placed logical service's lifecycle to its active signed release
remove — Remove a service entirely: withdraw its declaration, stop it, and delete its unit file from the host — the operation an operator means by "remove this service", which `retire` deliberately is not. The file path comes from the registry declaration, never from operator words. A host failure restores the declaration; a file-delete failure leaves the service retired and reports that partial state
deploy — Install a new unit under management: render, push, bootstrap, record
declare — Declare a service against the fleet's one contract
ensure — Assert the unit a host must be running, over ssh, idempotently
logs — Tail a managed unit's log over the approved channel
env — The effective environment a managed unit runs with, secrets redacted