Troubleshooting

Start with the exact release version, the command output, and any local validation evidence. Avoid mixing assets from latest and a versioned release directory.

For divergent prompts, templates, manifests, materialized output, or partially upgraded workspace metadata, use Upgrade prompt and template customizations before authorizing force or migration.

The command is not found

Confirm that the installer placed the command directory on PATH. Open a new shell so startup files are reloaded, then run day-shift --help. If the installer reported a destination outside your current PATH, add that directory according to its output.

Checksums or manifest metadata do not match

Stop using the artifact. Download the archive or installer, manifest, and checksum file from the same exact /downloads/<version>/ directory, then verify again. Do not treat a mutable latest pointer as immutable evidence.

The wrong license is selected

Run:

day-shift license status --format json

Inspect the resolved user-local license path. Use --license-file <path> for a one-off check without writing configuration.

Managed reminder regions remain

First confirm that the installed license verifies and suppresses reminders. Then preview and apply cleanup:

day-shift license cleanup-reminders --dry-run
day-shift license cleanup-reminders

The CLI appears to need the website

Normal installed CLI behavior is local-first and offline-capable. Website access is needed for public downloads, purchases, signed-file delivery or recovery, and documentation—not for ordinary repository workflows.

For account, purchase, entitlement, recovery, or promised response questions, use the website’s support entry point; those policies are not defined by this troubleshooting guide.