schedulingctl command reference

Registry Scheduling authoring and local operator tooling.

Contract status

This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.

Usage

schedulingctl [OPTIONS] <COMMAND>

Commands

Command	Description
api	Send one raw HTTP request using a saved Scheduling connection
connection	Manage named Scheduling API connections
serve	Run the production Scheduling service with the selected runtime
init	Create a complete Registry Scheduling authoring project in a new directory
check	Check a project and, with —runtime-config, a runtime file, offline, and print effective defaults
test	Run every fixture’s replay cases offline
explain	Explain the checked policy offline: what the runtime would publish
package	Write the checked policy into a new package directory the runtime verifies
plan	Report what apply would do to a deployment’s database, writing nothing
apply	Activate the verified package on a deployment’s database
status	Report the active package and the activation ledger of a deployment’s database
records	Apply the live environment records of a deployment
intents	List delivery intents a deployment’s dispatcher has stopped carrying

Options

Option	Always required	Default	Values	Environment	Description
--format <FORMAT>	No	human	human, json	n/a	Emit the selected command’s report in this format
-h, --help	No	n/a	n/a	n/a	Print help
-V, --version	No	n/a	n/a	n/a	Print version

Generation contract

After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.