Command reference

This index is the coverage contract for the Day Shift CLI. The generated machine-readable command inventory is derived from the authoritative runtime descriptor registry and records every callable command path, alias, argument, option, capability, authorization rule, availability precondition, mutation posture, effect boundary, and representative invocation.

Command-family ownership

Every callable descriptor belongs to one of these reference lanes:

• Core lifecycle: specification intake, planning, work selection, task execution, implementation evidence, reconciliation, metadata, validation, and structural-pressure commands are covered by the core workflow command reference.
• Operations and administration: configuration, licensing, versions, diagnostics, agent context, workspace migration, manifests, prompts, templates, resume, archive, and release commands are covered by the operations command reference.
• Automation and extension: structured formats, projections, filtering, pagination, budgets, exit classification, descriptors, architecture, and extension rules are covered by the automation contract.

For command families whose detailed route is not yet published, use the generated inventory and day-shift commands describe "<command path>" --format json as the exact contract.

Shared automation controls

Structured surfaces can expose --format, --detail, --fields, --finding-severity, lane-specific --limit, --page-lane, --page-size, opaque --cursor, and --output-budget. Support is descriptor-specific: an option is callable only when the command descriptor or help output declares it. Incomplete or truncated output is protocol evidence, not a complete inventory.

Mutation posture

• Read-only commands inspect or validate and do not repair state.
• Preview commands calculate a candidate change while leaving changedPaths empty.
• Explicit-write commands require a selected write surface and scoped authority.
• Destructive commands remove or replace state and require their declared confirmation boundary.
• Externally consequential commands can affect network, release, license, or host state even when repository files do not change.

The inventory fields writeCapable, mutationPosture, authorization, confirmation, and effects are authoritative together; no single field should be used as a substitute for the complete effect contract.

Failure and availability

Descriptor preconditions, input validation, selection requirements, and authorization rules determine whether a command is available. JSON failures preserve a typed category, exit classification, retryability, write outcome, and recovery actions. A failed or rejected command does not grant authority to improvise a different write.

Related guidance: operating model and artifacts, workflow index, and troubleshooting.