@thegetty/quire-cli 1.0.0-rc.44 → 1.0.0-rc.46

package/src/lib/11ty/paths.js

@@ -0,0 +1,103 @@
+import { fileURLToPath } from 'node:url'
+import fs from 'fs-extra'
+import path from 'node:path'
+
+const __filename = fileURLToPath(import.meta.url)
+const __dirname = path.dirname(__filename)
+
+/**
+ * Eleventy configuration paths
+ * @see https://www.11ty.dev/docs/config/#configuration-options
+ *
+ * Resolve the absolute path to the Eleventy configuration module,
+ * `eleventyRoot` is _relative_ to `main.js`, the CLI entry point.
+ * Both `input` and `output` are _relative_ to the `config` module.
+ *
+ * @todo
+ * - refactor the paths module as a concern of the `lib/quire` module
+ * - refactor resolving an absolute path to the correct eleventy version root;
+ *   this needs to use the correct `quire-11ty` version for the project
+ *   and correctly resolve the path to the target of the 'latest' symlink
+ */
+const cliRoot = path.resolve(__dirname, path.join('..', '..'))
+const eleventyConfig = '.eleventy.js'
+const version = 'latest'
+
+export const projectRoot = process.cwd()
+
+/**
+ * Absolute path to the latest installed version of `quire-11ty`
+ * @todo use version read from the project `.quire-version` file
+ */
+const libQuirePath = path.resolve(__dirname, path.join(cliRoot, 'lib', 'quire', 'versions', version))
+
+/**
+ * Absolute path to the current version of `quire-11ty`
+ * Nota bene: to get a relative path to the `eleventyRoot`,
+ * for example when the version is specified is 'latest',
+ * it must be set to the real path to the symlink target.
+ *
+ * @todo refactor how and *when* the eleventyRoot is determined:
+ *  - we only need eleventyRoot for cli commands that run 11ty
+ *  - paths module is a concern of the `quire` module
+ *  - global quire-cli installation
+ *  - local quire-cli installation
+ *
+ *  For an excellent developer experience, the quire-11ty code should be
+ *  installed into an `11ty` or `quire-11ty` directory in the `projectRoot`
+ *  this will allow us to more easily manage symlinks for local development
+ *  using unpublished `quire-11ty` code.
+ *  @example
+ *  ```sh
+ *  blargh/
+ *    .git/
+ *    .gitignore
+ *    .node-version
+ *    .quire-version
+ *    11ty@ --> /Users/mph/Code/Getty/quire/packages/11ty
+ *    content/
+ *    CHANGELOG.md
+ *    LICENSE
+ *    README.md
+ *    package.json
+ *    package-lock.json
+ *  ```
+ *  Installing to a directory will allow more cleanly `eject` and `uneject`
+ *  using a symlink or single directory `rm -rf`.
+ *  Should the `11ty` directory be a dot directory to hide the complexity from
+ *  users or should it be visible to be more explicit when project is ejected?
+ */
+const getEleventyRoot = () => {
+  // try {
+  //   return fs.readdirSync(projectRoot).includes(eleventyConfig)
+  //     ? projectRoot
+  //     : fs.realpathSync(libQuirePath)
+  // } catch (error) {
+  //   throw new Error(`[CLI:11ty] Unable to read project directory for eleventy config ${error}`)
+  // }
+  return projectRoot
+}
+
+export const eleventyRoot = getEleventyRoot()
+
+const inputDir = path.join(projectRoot, 'content')
+
+export default {
+  /**
+   * An abolsute path to eleventy config module
+   */
+  config: path.join(eleventyRoot, '.eleventy.js'),
+  /**
+   * Paths _relative to_ the eleventy config module
+   */
+  input: path.relative(eleventyRoot, inputDir),
+  output: path.relative(eleventyRoot, path.join(projectRoot, '_site')),
+  epub: path.relative(eleventyRoot, path.join(projectRoot, '_epub')),
+  /**
+   * Paths _relative to_ the `input` directory
+   */
+  data: '_computed',
+  includes: path.relative(inputDir, path.join(eleventyRoot, '_includes')),
+  layouts: path.relative(inputDir, path.join(eleventyRoot, '_layouts')),
+  public: './public',
+}

package/src/lib/README.md

@@ -1,330 +0,0 @@
-# CLI Library Modules
-
-This directory contains domain-specific modules that encapsulate the core functionality of the Quire CLI. Each module is designed around a single responsibility and provides a façade for its domain.
-
-## Architecture Overview
-
-```
-                                    Commands Layer
-                    ┌───────────────────────────────────────────────────┐
-                    │  build  preview  new  pdf  epub  info  doctor    │
-                    └────────────────────────┬──────────────────────────┘
-                                             │
-                    ┌────────────────────────┴──────────────────────────┐
-                    │                   lib/ modules                    │
-                    └───────────────────────────────────────────────────┘
-
-     ┌─────────────────────────────────────────────────────────────────────────┐
-     │                           Domain Modules                                │
-     │  ┌────────────┐  ┌──────────┐  ┌────────────┐  ┌──────────┐  ┌────────┐  │
-     │  │ project/   │  │  11ty/   │  │   pdf/     │  │  epub/   │  │doctor/ │  │
-     │  │            │  │          │  │            │  │          │  │        │  │
-     │  │ - paths    │  │ - api    │  │ - pagedjs  │  │ - epubjs │  │-checks │  │
-     │  │ - config   │  │ - cli    │  │ - prince   │  │ - pandoc │  │-format │  │
-     │  │ - detect   │  │          │  │            │  │          │  │        │  │
-     │  │ - version  │  │          │  │            │  │          │  │        │  │
-     │  └────┬───────┘  └────┬─────┘  └────┬───────┘  └────┬─────┘  └───┬────┘  │
-     └───────┼───────────────┼─────────────┼───────────────┼─────────────┼──────┘
-             │               │             │               │             │
-             │      ┌────────┴─────────────┴───────────────┴─────────────┘
-             │      │
-     ┌───────┴──────┴──────────────────────────────────────────────────┐
-     │                     Installation Module                         │
-     │  ┌──────────────────────────────────────────────────────────┐   │
-     │  │                      installer/                          │   │
-     │  │  - initStarter (clone starter, setup project)            │   │
-     │  │  - installInProject (install @thegetty/quire-11ty)       │   │
-     │  │  - latest (resolve version from npm)                     │   │
-     │  │  - versions (list published versions)                    │   │
-     │  └──────────────────────────────────────────────────────────┘   │
-     └───────────────────────────────┬─────────────────────────────────┘
-                                     │
-     ┌───────────────────────────────┴─────────────────────────────────┐
-     │                    Infrastructure Modules                       │
-     │  ┌────────┐  ┌────────┐  ┌────────┐  ┌─────────┐  ┌──────────┐  │
-     │  │  npm/  │  │  git/  │  │ conf/  │  │ error/  │  │ logger/  │  │
-     │  │        │  │        │  │        │  │         │  │          │  │
-     │  └────────┘  └────────┘  └────────┘  └─────────┘  └──────────┘  │
-     │  ┌───────────┐  ┌───────────┐                                   │
-     │  │ reporter/ │  │  ui/      │                                   │
-     │  │           │  │ (prompt)  │                                   │
-     │  └───────────┘  └───────────┘                                   │
-     └─────────────────────────────────────────────────────────────────┘
-```
-
-## Module Reference
-
-### Domain Modules
-
-These modules encapsulate specific business domains of Quire.
-
-#### `project/`
-**Purpose:** Project-level concerns including paths, detection, configuration, and version management.
-
-| Export | Description |
-|--------|-------------|
-| `paths` (default) | Singleton for path resolution |
-| `Paths` | Class for custom path instances |
-| `DATA_DIR` | Path to data files directory (`content/_data`) |
-| `PROJECT_MARKERS` | Files that identify a Quire project |
-| `REQUIRED_DATA_FILES` | Required data files (`publication.yaml`) |
-| `SOURCE_DIRECTORIES` | Directories monitored for changes |
-| `detect(dirpath)` | Check if directory is a Quire project |
-| `loadProjectConfig(projectRoot?)` | Load and validate project config |
-| `getVersion(projectPath?)` | Read `quire-11ty` version from project |
-| `setVersion(version, projectPath?)` | Write `quire-11ty` version to project |
-| `getVersionsFromStarter(projectPath)` | Read versions from starter package.json |
-| `readVersionFile(projectPath)` | Read raw version file contents |
-| `writeVersionFile(projectPath, info)` | Write version file contents |
-
-**Dependencies:** `conf/`, `fs-extra`
-
-#### `11ty/`
-**Purpose:** Eleventy build system integration via API or CLI.
-
-| Export | Description |
-|--------|-------------|
-| `api` | Programmatic Eleventy control |
-| `cli` | CLI-based Eleventy execution |
-| `paths` | Re-exported from `project/` |
-| `Paths` | Re-exported from `project/` |
-
-**Dependencies:** `project/`
-
-#### `pdf/`
-**Purpose:** PDF generation using Prince or Paged.js.
-
-| Export | Description |
-|--------|-------------|
-| `default` | Factory returning configured PDF generator |
-
-**Implementations:** `prince.js`, `paged.js`
-
-**Dependencies:** `project/`
-
-#### `epub/`
-**Purpose:** EPUB generation using Pandoc.
-
-| Export | Description |
-|--------|-------------|
-| `default` | EPUB generator façade |
-
-**Dependencies:** `project/`
-
-#### `doctor/`
-**Purpose:** Diagnostic checks for Quire environment and project health.
-
-| Export | Description |
-|--------|-------------|
-| `default` | Object with all check functions and arrays |
-| `checks` | Flat array of all diagnostic checks |
-| `checkSections` | Checks organized by section (Environment, Project) |
-| `runAllChecks()` | Run all checks, return flat results array |
-| `runAllChecksWithSections()` | Run all checks, return results by section |
-| `checkNodeVersion()` | Verify Node.js >= 22 |
-| `checkNpmAvailable()` | Verify npm in PATH |
-| `checkGitAvailable()` | Verify git in PATH |
-| `checkQuireProject()` | Detect project marker files |
-| `checkDependencies()` | Verify node_modules exists |
-| `checkDataFiles()` | Validate YAML files in content/_data/ |
-| `checkStaleBuild()` | Compare source vs build timestamps |
-
-**Sub-modules:**
-
-| File | Description |
-|------|-------------|
-| `formatDuration.js` | Human-readable time duration formatting |
-
-**Duration Formatting:**
-
-The `formatDuration` function converts milliseconds to the most appropriate time unit:
-
-| Duration       | Example Output  |
-|----------------|-----------------|
-| < 1 minute     | "45 seconds"    |
-| < 1 hour       | "30 minutes"    |
-| < 1 day        | "5 hours"       |
-| < 1 week       | "3 days"        |
-| < 1 month      | "2 weeks"       |
-| < 1 year       | "3 months"      |
-| >= 1 year      | "2 years"       |
-
-**Data Files Validation:**
-
-The `checkDataFiles` function validates YAML files in `content/_data/`:
-
-| Validation | Description |
-|------------|-------------|
-| Required files | Checks `publication.yaml` exists |
-| YAML syntax | Parses each file and reports syntax errors |
-| Schema validation | Validates against JSON schemas in `schemas/` |
-| Duplicate IDs | Detects duplicate `id` values in arrays |
-
-**Dependencies:** `project/`, `npm/`, `git/`, `validators/validate-data-files`
-
-#### `installer/`
-**Purpose:** Installation of `@thegetty/quire-11ty` into Quire projects.
-
-| Export | Description |
-|--------|-------------|
-| `installer` | Object with all installer methods |
-| `initStarter(starter, projectPath, options)` | Clone and setup starter project |
-| `installInProject(projectPath, version, options)` | Install `@thegetty/quire-11ty` package |
-| `latest(version?)` | Resolve version from npm registry |
-| `versions()` | List all published `@thegetty/quire-11ty` versions |
-
-**Dependencies:** `project/`, `npm/`, `git/`
-
-### Infrastructure Modules
-
-These modules provide cross-cutting concerns and external tool integrations.
-
-#### `npm/`
-**Purpose:** NPM operations façade.
-
-| Export | Description |
-|--------|-------------|
-| `default` | Singleton npm façade |
-| `init(cwd, options?)` | Run `npm init` |
-| `install(cwd, options?)` | Run `npm install` |
-| `pack(spec, dest, options?)` | Run `npm pack` |
-| `cacheClean(cwd?)` | Run `npm cache clean` |
-| `view(pkg, field?)` | Query package info |
-| `show(pkg, field?)` | Query package versions |
-| `version()` | Get npm version |
-| `isAvailable()` | Check npm in PATH |
-| `fetchFromRegistry(pkg)` | Direct registry API call |
-| `getCompatibleVersion(pkg, range)` | Resolve semver range |
-
-**Dependencies:** `execa`, `node-fetch`
-
-#### `git/`
-**Purpose:** Git operations via simple-git.
-
-| Export | Description |
-|--------|-------------|
-| `default` | Configured simple-git instance |
-
-**Dependencies:** `simple-git`
-
-#### `conf/`
-**Purpose:** CLI configuration persistence and schema-aware helpers.
-
-| Export | Source | Description |
-|--------|--------|-------------|
-| `default` | `config.js` | `Conf` singleton instance |
-| `isValidKey(key)` | `helpers.js` | Check if key exists in schema |
-| `getValidKeys()` | `helpers.js` | Sorted array of all schema keys |
-| `coerceValue(key, value)` | `helpers.js` | Coerce CLI string to schema type |
-| `formatValidationError(key, value)` | `helpers.js` | Format error with enum/description hints |
-| `getDefault(key)` | `helpers.js` | Get default value for a key |
-| `getKeyDescription(key)` | `helpers.js` | Get schema description for a key |
-| `formatSettings(store, options)` | `helpers.js` | Format all settings for display |
-
-Uses a barrel export (`index.js`) rather than a wrapper class to keep pure helper functions separate from the stateful `Conf` singleton. This avoids circular dependencies with the logger module and keeps helpers directly testable without mocking.
-
-**Dependencies:** `conf`
-
-#### `logger.js`
-**Purpose:** Logging abstraction.
-
-| Export | Description |
-|--------|-------------|
-| `default` | Logger instance (loglevel) |
-
-**Dependencies:** `loglevel`
-
-#### `reporter/`
-**Purpose:** Progress reporting for long-running operations.
-
-| Export | Description |
-|--------|-------------|
-| `default` | Reporter façade |
-
-#### `error/`
-**Purpose:** Centralized error handling and formatting.
-
-| Export | Description |
-|--------|-------------|
-| `formatError(error, options)` | Format error for display |
-| `handleError(error, options)` | Handle single error (format, log, exit) |
-| `handleErrors(errors, options)` | Handle multiple errors (batch validation) |
-
-**Features:**
-- Consistent error formatting with suggestion, docs URL, file path
-- Debug mode shows error codes and stack traces
-- Conditional `--debug` hint (controlled by `showDebugHint` property)
-- Exit code management per error category
-
-**Dependencies:** `logger/`
-
-#### `ui/`
-**Purpose:** Display and interactive prompt
-
-_Future feature: Not yet impemented._
-
-## Design Patterns
-
-### Singleton façade
-Most modules export a singleton instance as the default export:
-```javascript
-import npm from '#lib/npm/index.js'
-await npm.install('/path/to/project')
-```
-
-### Optional Parameters with Defaults
-Functions that operate on projects default to `cwd` when path not provided:
-```javascript
-// Uses current working directory
-setVersion('1.0.0')
-
-// Uses explicit path
-setVersion('1.0.0', '/path/to/project')
-```
-
-### Re-exports for Convenience
-Modules re-export commonly used dependencies:
-```javascript
-// 11ty/ re-exports paths from project/
-import { paths } from '#lib/11ty/index.js'
-```
-
-## Import Aliases
-
-Use these aliases for imports:
-
-| Alias | Path |
-|-------|------|
-| `#lib/` | `src/lib/` |
-| `#src/` | `src/` |
-| `#helpers/` | `src/helpers/` |
-
-Example:
-```javascript
-import npm from '#lib/npm/index.js'
-import { installer } from '#lib/installer/index.js'
-import paths, { loadProjectConfig } from '#lib/project/index.js'
-```
-
-## Testing
-
-Each module has associated test files:
-
-| Pattern | Purpose |
-|---------|---------|
-| `*.spec.js` | Unit tests (interface contracts) |
-| `*.test.js` | Integration tests (with mocked dependencies) |
-
-Tests use:
-- **AVA** for test runner
-- **esmock** for ESM module mocking
-- **sinon** for stubs and spies
-- **memfs** for in-memory filesystem
-
-## Adding a New Module
-
-1. Create directory: `lib/<module-name>/`
-2. Create entry point: `index.js` with façade pattern
-3. Export singleton or factory as default
-4. Add tests: `index.spec.js` and/or `index.test.js`
-5. Update this README with module documentation

package/src/lib/conf/README.md

@@ -1,121 +1,104 @@
-## CLI Configuration Module
+## CLI Configuration Manager
 
-The `conf/` module manages reading and writing (persisting) settings for the Quire CLI using the [`conf`](https://github.com/sindresorhus/conf) package.
+This `quire-cli/lib/config` module manages reading and writing (persisting) options for the Quire CLI using the [`conf`](https://github.com/sindresorhus/conf) package.
 
 `conf` stores the config in the system default [user config directory](https://github.com/sindresorhus/env-paths#pathsconfig). For example, on macOS, the config file will be stored in the `~/Library/Preferences/@thegetty/quire-cli` directory.
 
 > Changes are written to disk atomically, so if the process crashes during a write, it will not corrupt the existing config.
 
-### Module Structure
+### Configuration
 
+`logLevel` The default logging level for the Quire CLI output; default `'info'`.
+
+`projectTemplate` A default project starter template to use when creating new projects; default `'quire-starter-default'`.
+
+`quirePath` The relative path to `quire-11ty` installed in the project directory; default `./11ty`. When set to `null`, `quire-11ty` is installed to the CLI `lib/quire/versions/<version>/` directory.
+
+```sh
+❯ quire config quire-path '.'
 ```
-conf/
-├── index.js         Barrel export (config singleton + helpers + format)
-├── config.js        Conf singleton instance
-├── helpers.js       Pure schema-aware validation and coercion
-├── format.js        Display formatting with optional chalk styling
-├── defaults.js      Default configuration values
-├── schema.js        JSON Schema definitions
-├── migrations.js    Version migration functions
-├── config.test.js   Integration tests for Conf instance
-├── helpers.test.js  Unit tests for validation/coercion helpers
-└── format.test.js   Unit tests for display formatting
+
+`quireVersion` The default version of `quire-11ty` to install when creating new Quire projects; default `'latest'`.
+
+```sh
+❯ quire config quire-version '1.0.0'
 ```
 
-### Architecture: Barrel Export vs Singleton Wrapper
+`telemetry` Send anonymous data about Quire usage; default `false`.
 
-The module uses a **barrel export** pattern (`index.js`) rather than wrapping the `Conf` singleton in a class. This is a deliberate design choice:
+```sh
+❯ quire config telemetry --enabled
+```
 
-- **`config.js`** exports the `Conf` singleton that owns mutable state (the on-disk JSON store, file watching, schema validation, migrations). This is a thin wrapper around the `conf` package.
-- **`helpers.js`** exports pure functions (`isValidKey`, `coerceValue`, `formatValidationError`, etc.) for schema-aware validation and coercion. These import only `schema.js` and `defaults.js` (pure data), keeping them free of transitive dependencies.
-- **`format.js`** exports display formatting functions (`formatSettings`, `getKeyDescription`) that depend on `chalk` for optional coloured output. Separated from `helpers.js` to isolate the chalk dependency from the pure validation/coercion functions.
-- **`index.js`** re-exports all three, providing a single import path for consumers.
+```sh
+❯ quire config telemetry --disabled
+```
 
-A wrapper class was considered but rejected for three reasons:
+`updateChannels` A list of distribution tags to use when checking for version updates; default `['latest']`. To show notifications for pre-releases version updates include `'pre-release'` in the array of channels. This can be set using the configuration `--pre-release` command flag.
 
-1. **No shared state.** The helpers operate on schema/defaults (static data), not the config store (runtime state). Binding them to the singleton would create a false coupling.
-2. **Circular dependency avoidance.** The logger imports `config.js`. If helpers were methods on the config singleton, importing them would trigger the full `Conf` instantiation chain. By depending only on `schema.js` and `defaults.js` (pure data modules), `helpers.js` stays free of transitive dependencies.
-3. **Testability.** Pure functions are directly testable with simple import + assert — no esmock, no sinon, no constructor stubbing. Compare `helpers.test.js` (pure function tests) with `config.test.js` (integration tests requiring esmock to mock the `Conf` constructor).
+```sh
+❯ quire config update-channels
+Quire configured to check for updates tagged 'latest'
+```
 
-### Exports
+```sh
+❯ quire config update-channels --add 'pre-release'
+Quire configured to check for updates tagged 'latest', 'pre-release'
+```
 
-```javascript
-// Barrel import — config singleton + named helpers
-import config, { isValidKey, coerceValue } from '#lib/conf/index.js'
+```sh
+❯ quire config update-channels --rm 'pre-release'
+Quire configured to check for updates tagged 'latest'
+```
+
+`updateInterval` Interval at which to check for updates to the Quire CLI and project's `quire-11ty` version; default `'DAILY'`.
 
-// Direct import — config singleton only (used by logger, etc.)
-import config from '#lib/conf/config.js'
+```sh
+❯ quire config update-interval
+Quire configured to check for updates DAILY
 ```
 
-| Export | Source | Description |
-|--------|--------|-------------|
-| `default` | `config.js` | `Conf` singleton instance |
-| `isValidKey(key)` | `helpers.js` | Check if key exists in schema |
-| `getValidKeys()` | `helpers.js` | Sorted array of all schema keys |
-| `coerceValue(key, value)` | `helpers.js` | Coerce CLI string to schema type |
-| `formatValidationError(key, value)` | `helpers.js` | Format error with enum/description hints |
-| `getDefault(key)` | `helpers.js` | Get default value for a key |
-| `getKeyDescription(key)` | `format.js` | Get schema description for a key |
-| `formatSettings(store, options)` | `format.js` | Format all settings for display (with optional chalk styling) |
+```sh
+❯ quire config update-interval WEEKLY
+```
 
-### Display Formatting
+`versionFile ['.quire-version']` The default file name for the `quire-11ty` version file.
 
-`formatSettings` accepts an options object controlling output:
+```sh
+❯ quire config version-file '.blargh'
+```
 
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `configPath` | string | — | Path shown in header (e.g. `quire-cli configuration /path/to/config`) |
-| `showInternal` | boolean | `false` | Include `__internal__`-prefixed keys |
-| `useColor` | boolean | `false` | Apply chalk styling (bold header, cyan keys, dim descriptions) |
+### Quire CLI `config` Command
 
-When `useColor` is `true`, output uses:
-- **Bold** for the header line
-- **Cyan** for key names
-- **Dim** for descriptions and the help hint
+Running the `config` command without any arguments will start an interactive prompt to configure Quire.
 
-When `useColor` is `false` (default), no ANSI escape codes are emitted.
+To view an individual configuration value and its default value use:
 
-The settings command reads `logUseColor` from the config to determine whether to pass `useColor: true`.
+```sh
+❯ quire config [key]
+```
+
+To view the current `logLevel` setting for example:
 
-### Settings Reference
+```sh
+❯ quire config logLevel
+loglevel: 'debug' (default 'info')
+```
 
-Use `quire settings` to view all settings with descriptions, or manage individual values:
+To set an individual configuration value, use the `set` argument:
 
 ```sh
-quire settings                     # Show all settings (coloured if logUseColor is true)
-quire settings get <key>           # Get a single value
-quire settings set <key> <value>   # Set a value
-quire settings delete <key>        # Delete (reset to default)
-quire settings reset [key]         # Reset all or single key
-quire settings path                # Show settings file path
-quire settings --json              # Output all settings as JSON
-quire settings get <key> --json    # Output single value as JSON
-quire settings --json --debug      # Include __internal__ keys in JSON output
+❯ quire config set <key> <value>
 ```
 
-`staleThreshold` How stale an output must be before `quire doctor` warns; default `'HOURLY'`. Options: `'ZERO'` (0 min), `'SHORT'` (5 min), `'HOURLY'` (60 min), `'DAILY'` (12 hours), `'NEVER'` (disabled).
+To reset *all* keys to their default values, use the `reset` argument:
 
 ```sh
-❯ quire config set staleThreshold DAILY
+❯ quire config reset
 ```
 
-The `--json` flag outputs raw JSON to stdout (bypassing the logger), suitable for piping to `jq` or other tools. `__internal__` keys are excluded from JSON output unless `--debug` is also passed, consistent with the plain-text display.
-
-| Key | Type | Default | Description |
-|-----|------|---------|-------------|
-| `debug` | boolean | `false` | Enable debug output by default |
-| `epubEngine` | string | `'epubjs'` | EPUB engine (`epubjs`, `pandoc`) |
-| `logLevel` | string | `'info'` | Log level (`trace`, `debug`, `info`, `warn`, `error`, `silent`) |
-| `logPrefix` | string | `'quire'` | Prefix text for log messages |
-| `logPrefixStyle` | string | `'bracket'` | Prefix style (`bracket`, `emoji`, `plain`, `none`) |
-| `logShowLevel` | boolean | `false` | Show level label in output |
-| `logUseColor` | boolean | `true` | Use colored output |
-| `logColorMessages` | boolean | `true` | Color message text by level |
-| `pdfEngine` | string | `'pagedjs'` | PDF engine (`pagedjs`, `prince`) |
-| `projectTemplate` | string | (GitHub URL) | Default starter template |
-| `quire11tyPath` | string | `'.'` | Path to quire-11ty package |
-| `quireVersion` | string | `'latest'` | Version of quire-11ty to install |
-| `updateChannel` | string | `'rc'` | Release channel (`stable`, `rc`, `beta`, `alpha`) |
-| `updateInterval` | string | `'DAILY'` | Update check frequency (`DAILY`, `WEEKLY`, `MONTHLY`, `NEVER`) |
-| `verbose` | boolean | `false` | Enable verbose output by default |
-| `versionFile` | string | `'.quire'` | Filename to identify Quire projects |
+To reset an individual key to its default value:
+
+```sh
+❯ quire config reset [key]
+```

package/src/lib/conf/config.js

@@ -1,16 +1,14 @@
 import Conf from 'conf'
-import packageConfig from '#src/packageConfig.js'
 import defaults from './defaults.js'
 import migrations from './migrations.js'
+import packageConfig from '#src/packageConfig.js'
 import schema from './schema.js'
 
 const { name, version } = packageConfig
 
-const beforeEachMigration = (_store, context) => {
+const beforeEachMigration = (store, context) => {
   const { fromVersion, toVersion } = context
-  // Call console directly to avoid circular dependency (logger imports config)
-  // Migration messages are rare, so the simpler formatting is acceptable
-  console.info(`[quire] Migrating config from ${fromVersion} → ${toVersion}`)
+  console.info(`quire-cli migrating config from ${fromVersion} → ${toVersion}`)
 }
 
 /**