Operations and administration commands

Operational commands inspect or change workspace, host, network, license, installed-version, and release state. Resolve exact syntax and effects through the machine inventory or day-shift commands describe "<command path>" --format json before acting.

Configuration and diagnostics

Exact roots: config, doctor, about, agent, and completion. Read-only inspection reports resolved configuration, runtime identity, scoped health, agent guidance, or shell integration text. Configuration edits and completion installation are explicit writes. Treat local configuration and diagnostic output as potentially sensitive.

Licensing

Exact root: license. Status and inspection are read-only; activation, installation, refresh, or removal can change host state and may use the network. Verify authorization, destination, confirmation, and rollback from the descriptor. See license management.

Managed versions

Exact root: version. Current/list inspection is read-only. Install and update can download and replace binaries; pin writes repository selection state; uninstall is destructive and may require --replace-with. Verify exact release identity and post-install day-shift --version evidence. See installation.

Workspace migration

Exact root: workspace migrate. Preview or --dry-run is required evidence before apply. Apply is an explicit multi-path write; never manually move .day-shift assets around a malformed or partially upgraded workspace. Stop on conflict or partial-state recovery evidence.

Prompts, templates, and manifests

Exact roots: prompt, template, and manifest. List, show, search, diff, and review report evidence. Edit, update, materialize, and manifest-update operations are explicit workspace writes and must preserve user ownership and merge boundaries. See prompt and template catalogs and customization.

Resume, archive, and release

Exact roots: resume, archive, and release. Resume inspection revalidates derived evidence; create/replace/cleanup changes coordination state. Archive previews are read-only and archive/apply operations move or record selected state. Release validation is evidence; manifest or publication commands can materialize assets, invoke network behavior, or create externally consequential release state.

day-shift workspace migrate preview --format json
day-shift prompt diff --layer user --format json
day-shift resume inspect --format json

These examples are evidence-only. Do not substitute an apply, update, cleanup, or release write without reviewing the matching descriptor and preview.

Shared failure and recovery contract

JSON output classifies usage, validation, environment, conflict, authorization, and unexpected failures and records writeOutcome. For network or host failures, confirm whether state changed before retrying. For destructive or external effects, honor confirmation and idempotency. For partial writes, follow the typed inspection or rollback action; never infer that retry is safe.