use-a-novel-clilisted

# Use the `a-novel` CLI The `a-novel` CLI is the single user-facing entrypoint for local-dev workflows. It replaces the deleted Makefiles and per-repo bash scripts (`go test` wrappers, `podman build`, `podman compose`, `publish.sh`) with one coherent command surface: ``` a-novel ├── test standalone — runs Go + pnpm tests in the working tree ├── build standalone — builds Go binaries, pnpm bundles, Podman images ├── publish standalone — release doc helpers (releases themselves run in CI) ├── repo standalone — GitHub repo config, rulesets, required checks ├── core daemon control (start, setup, kill, status, prepare-reinstall) ├── run daemon-backed verbs (services + targets) ├── secrets standalone — local encrypted secrets, injected into child envs ├── install standalone — rebuild + reinstall the CLI, state-preserving ├── claude standalone — launch Claude Code rooted at the stack └── version standalone — print the CLI version ``` `secrets`, `install`, `claude` and `version` complete the surface and have their own sections below; `cli/README.md` in the stack repo remains the exhaustive reference. **Always prefer `a-novel <verb>` over the equivalent raw command** when one exists. Makefiles are gone from every repo — `make` is never the answer. What the CLI doesn't cover lives in pnpm scripts (lint/format/generate, see "When NOT to use the CLI") so each repo's surface is exactly: `a-novel <verb>` + `pnpm