schedulingctl command reference
Registry Scheduling authoring and local operator tooling.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.34.0 and catalog SHA-256 521175a69262e60df96745886392348e5bb8d82e63cdd24bdf4baa80d46e5ff4. Hidden implementation commands are omitted.
schedulingctl [OPTIONS] <COMMAND>Commands
Section titled “Commands”| Command | Description |
|---|---|
init | Create a complete Registry Scheduling authoring project in a new directory |
check | Validate the authored policy 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 verified policy package manifest beside the authored policy |
records | Apply the live environment records of a deployment |
intents | List delivery intents a deployment’s sweep has stopped carrying |
Options
Section titled “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
Section titled “Generation contract”Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.