@purveyors/cli 0.14.0 → 0.15.1

package/README.md

@@ -2,9 +2,22 @@
 
 Coffee intelligence from your terminal.
 
-`purvey` is the official CLI for [purveyors.io](https://purveyors.io). It gives coffee professionals and AI agents direct access to the Purveyors platform from the terminal: catalog search, inventory tracking, roast logging, sales records, tasting notes, and Artisan `.alog` import.
+`purvey` is the official CLI for [purveyors.io](https://purveyors.io). It gives coffee professionals, developers, and AI agents direct access to the Purveyors platform from the terminal: catalog search, inventory tracking, roast logging, sales records, tasting notes, and Artisan `.alog` import.
 
-Run `purvey manifest` for the machine-readable contract, `purvey context` for the dense human-readable reference, or import `@purveyors/cli/manifest` in-process.
+Use `purvey --help` for quick command discovery, `purvey context` for the dense human-readable operator reference, `purvey manifest` for the preferred machine-readable contract, or `@purveyors/cli/manifest` in-process.
+
+## At a glance
+
+- Official binary: `purvey`
+- Package: `@purveyors/cli`
+- Runtime: Node.js 20+
+- No pre-existing session required: `auth`, `config`, `context`, `manifest`
+- Viewer role required: `catalog`
+- Member role required: `inventory`, `roast`, `sales`, `tasting`
+- Preferred machine-readable contract: `purvey manifest`
+- Dense human-readable reference: `purvey context`
+- Compatibility JSON alias: `purvey context --json`
+- In-process machine contract: `@purveyors/cli/manifest`
 
 ## Installation
 
@@ -22,6 +35,30 @@ Verify the install:
 purvey --version
 ```
 
+## Documentation map
+
+| Surface                                          | Use it for                                                |
+| ------------------------------------------------ | --------------------------------------------------------- |
+| <https://purveyors.io/docs/cli/overview>         | Live CLI docs                                             |
+| <https://purveyors.io/docs/api/overview>         | Live API docs                                             |
+| [AGENTS.md](./AGENTS.md)                         | Canonical contributor and agent guidance                  |
+| [docs/CLI_STRATEGY.md](./docs/CLI_STRATEGY.md)   | Historical architecture and shipped-surface retrospective |
+| <https://github.com/reedwhetstone/purveyors-cli> | Repository, issues, and source                            |
+| <https://www.npmjs.com/package/@purveyors/cli>   | Package installation and release metadata                 |
+
+Use the live docs on purveyors.io as the primary external reference. Use this README and `AGENTS.md` for repo-specific contributor detail.
+
+## Source-of-truth hierarchy
+
+Use this hierarchy when references disagree:
+
+1. `src/program.ts`, `src/commands/*`, and `src/lib/manifest.ts` define the shipped command surface, help text, auth requirements, output modes, ID guidance, and manifest payload.
+2. `package.json` defines the package version, Node engine, binary entrypoint, scripts, and exported subpaths.
+3. `README.md`, `AGENTS.md`, and `docs/CLI_STRATEGY.md` explain the repo-specific contract for users, contributors, and agents.
+4. `https://purveyors.io/docs/cli/overview` and `https://purveyors.io/docs/api/overview` are the primary live product docs for external readers.
+
+The CLI is an agent-first product surface. Treat the binary, exported functions, `purvey manifest`, `purvey context`, stdout/stderr behavior, and role-gated command boundaries as one contract.
+
 ## Quick Start
 
 ```bash
@@ -34,7 +71,7 @@ purvey auth login
 # 2. Confirm the session and role
 purvey auth status
 
-# 3. Search the catalog (requires viewer role, granted on sign-in)
+# 3. Search the catalog (requires viewer role)
 purvey catalog search --origin "Ethiopia" --stocked --pretty
 
 # 4. Check inventory (requires member role)
@@ -43,18 +80,56 @@ purvey inventory list --stocked --pretty
 # 5. Import a roast from Artisan
 purvey roast import ~/artisan/my-roast.alog --coffee-id 7 --pretty
 
-# 6. (Agents/scripts) Get the machine-readable CLI contract in one command
+# 6. Get the machine-readable CLI contract
 purvey manifest
 
-# 7. (Humans/agents) Get the dense readable CLI reference
+# 7. Get the dense readable CLI reference
 purvey context
 ```
 
-## Authentication
+## Reference surfaces
+
+Use the right reference surface for the job:
+
+- `purvey manifest` is the preferred stable machine-readable contract for agents, scripts, generated tooling, and parity checks.
+- `purvey context` is the dense human-readable operator reference for reviewers and interactive use.
+- `purvey context --json` and `purvey context --pretty` emit the same JSON payload as `purvey manifest`, but exist mainly for compatibility with tooling that already shells out to `context`.
+- `@purveyors/cli/manifest` exposes the same contract in-process for Node.js and agent runtimes.
+
+## Package exports and shared product surface
+
+The npm package is both a binary and a shared TypeScript product surface. `coffee-app` and agent runtimes import CLI business functions directly, so exported subpaths are part of the supported machine contract.
+
+| Import path                | Use it for                                     |
+| -------------------------- | ---------------------------------------------- |
+| `@purveyors/cli`           | CLI entrypoint package root                    |
+| `@purveyors/cli/catalog`   | Catalog search, lookup, stats, similar coffees |
+| `@purveyors/cli/inventory` | Green coffee inventory operations              |
+| `@purveyors/cli/roast`     | Roast profile operations                       |
+| `@purveyors/cli/sales`     | Sales record operations                        |
+| `@purveyors/cli/tasting`   | Tasting note and rating operations             |
+| `@purveyors/cli/lib`       | Shared library helpers                         |
+| `@purveyors/cli/manifest`  | Stable machine-readable CLI manifest           |
+| `@purveyors/cli/artisan`   | Artisan `.alog` parsing and import utilities   |
+| `@purveyors/cli/ai`        | AI helper surface used by CLI workflows        |
+
+Shell integrations should usually start with `purvey manifest`. In-process agent and website integrations should import the smallest relevant subpath instead of shelling out when they are already running in Node.js.
+
+Export discipline:
+
+- Add or remove subpaths only when the package contract intentionally changes.
+- Keep `package.json`, `README.md`, `AGENTS.md`, `docs/CLI_STRATEGY.md`, `src/lib/manifest.ts`, and dist parity checks aligned in the same PR.
+- Prefer the narrowest import path for application and agent code. For example, use `@purveyors/cli/catalog` for catalog operations instead of importing the package root.
+- Treat export-shape changes as product changes because coffee-app and agent runtimes import these functions directly.
+
+## Authentication and access model
 
 No pre-existing session is required for `auth`, `config`, `context`, or `manifest`.
 
-**All remote data commands require a valid authenticated session.** `catalog`, `inventory`, `roast`, `sales`, and `tasting` all require auth.
+All remote data commands require a valid authenticated session:
+
+- `catalog` requires the `viewer` role
+- `inventory`, `roast`, `sales`, and `tasting` require the `member` role
 
 `purvey` uses Google OAuth through purveyors.io.
 
@@ -91,23 +166,20 @@ Credentials are stored at `~/.config/purvey/credentials.json`.
 
 ### Auth roles
 
-Two roles gate different command groups:
-
-| Role     | Commands                                                            |
+| Role     | Access                                                              |
 | -------- | ------------------------------------------------------------------- |
 | `viewer` | `catalog search`, `catalog get`, `catalog stats`, `catalog similar` |
 | `member` | All viewer commands, plus `inventory`, `roast`, `sales`, `tasting`  |
 
-Both roles are granted when you sign in through purveyors.io. The `viewer` role is the minimum required for catalog access; the `member` role is required for any personal data or write operations.
+`auth`, `config`, `context`, and `manifest` remain available without a pre-existing session.
 
-`auth`, `config`, `context`, and `manifest` work without a pre-existing session. `config list/get/set/reset` are local-only commands, `context` is a local reference command, and `manifest` emits the machine-readable CLI contract.
+Commands that require a higher role exit with code `3` on auth failure. That includes not being signed in, an expired session, or an insufficient role.
 
-Commands that require a higher role will exit with code `3` (auth error) if you are not signed in or your role is insufficient. Run `purvey auth status` to confirm your current role before scripting.
+## Output contract and scripting
 
-## Output and Scripting
+Most commands write compact JSON to stdout by default. Use `--json` if you want to request that mode explicitly.
 
-Most commands write compact JSON to stdout by default.
-Use `--json` if you want to request that mode explicitly.
+Machine-contract rule of thumb: stdout is for successful payloads, stderr is for status or errors, and exit codes communicate the failure class. That rule is more important than making terminal output look conversational.
 
 Pretty JSON:
 
@@ -115,10 +187,11 @@ Pretty JSON:
 purvey inventory list --pretty
 ```
 
-CSV output for array results:
+CSV output for array results on supporting commands:
 
 ```bash
 purvey inventory list --csv > inventory.csv
+purvey roast list --csv > roasts.csv
 purvey sales list --csv > sales.csv
 ```
 
@@ -130,7 +203,7 @@ purvey roast list --limit 5 | jq '.[].roast_id'
 purvey auth status 2>/dev/null | jq -r '.email'
 ```
 
-Operational messages go to stderr, so stdout stays script-friendly.
+Operational messages go to stderr so stdout stays script-friendly.
 
 Fatal errors also stay on stderr, but the payload format depends on mode:
 
@@ -138,7 +211,7 @@ Fatal errors also stay on stderr, but the payload format depends on mode:
 - `--json`, `--pretty`, or `--csv`: JSON error envelope on stderr
 - piped or redirected with no explicit flag: compact JSON error envelope on stderr
 
-That same contract applies to parser-level mistakes too, including unknown options, unknown commands, and missing required arguments.
+That contract also applies to parser-level mistakes such as unknown options, unknown commands, and missing required arguments.
 
 The JSON error envelope includes:
 
@@ -148,24 +221,25 @@ The JSON error envelope includes:
 
 ### Output caveats worth knowing
 
-- `purvey auth status` prints human-readable output in an interactive terminal unless you pass `--json`, `--pretty`, or `--csv`. When piped or redirected, it emits JSON on stdout even when unauthenticated.
+- `purvey auth status` prints human-readable output in an interactive terminal unless you pass `--json`, `--pretty`, or `--csv`. When piped or redirected, it emits structured JSON on stdout even when unauthenticated.
 - `purvey config list/get/set/reset` stay human-readable in an interactive terminal, but emit JSON on stdout when you pass `--json` or `--pretty`, or when stdout is non-interactive. `--csv` is not supported for config commands.
-- `--json` is an explicit alias for the default compact JSON mode, and it forces JSON even in an interactive terminal.
+- `purvey context` defaults to dense human-readable reference text. `--json` and `--pretty` make it emit the same JSON manifest as `purvey manifest`.
+- `purvey manifest` always emits the machine-readable contract on stdout. `--pretty` only changes formatting.
 - `--csv` affects successful stdout output only; fatal errors still use JSON on stderr.
 
-## Exit Codes
+## Exit codes
 
 All `purvey` commands exit with a numeric code your scripts can check with `$?`.
 
-| Code | Meaning                                                                                   |
-| ---- | ----------------------------------------------------------------------------------------- |
-| `0`  | Success                                                                                   |
-| `1`  | Unexpected or unclassified error                                                          |
-| `2`  | Invalid argument or bad input                                                             |
-| `3`  | Auth error: not logged in, expired session, or insufficient role                          |
-| `4`  | Not found                                                                                 |
-| `5`  | Dependency conflict (for example, `inventory delete` without `--force` when roasts exist) |
-| `6`  | Local config error                                                                        |
+| Code | Meaning                                                          |
+| ---- | ---------------------------------------------------------------- |
+| `0`  | Success                                                          |
+| `1`  | Unexpected or unclassified error                                 |
+| `2`  | Invalid argument or bad input                                    |
+| `3`  | Auth error: not logged in, expired session, or insufficient role |
+| `4`  | Not found                                                        |
+| `5`  | Dependency conflict                                              |
+| `6`  | Local config error                                               |
 
 Scripting pattern:
 
@@ -176,15 +250,35 @@ if [ $? -eq 3 ]; then
 fi
 ```
 
-## Command Reference
+## Command reference
 
 ### auth
 
 - `purvey auth login`
 - `purvey auth login --headless`
 - `purvey auth status`
+- `purvey auth status --json`
+- `purvey auth status --pretty`
+- `purvey auth status --csv`
 - `purvey auth logout`
 
+Examples:
+
+```bash
+purvey auth login
+purvey auth login --headless
+purvey auth status --pretty
+purvey auth status --csv
+purvey auth logout
+```
+
+Notes:
+
+- `auth login` uses browser-based Google OAuth.
+- `auth login --headless` prints an OAuth URL and accepts a pasted callback URL.
+- `auth status --json` is the safest mode for scripts.
+- `auth status --csv` is supported for spreadsheet-style checks, but JSON remains the better integration format.
+
 ### catalog
 
 - `purvey catalog search`
@@ -194,27 +288,27 @@ fi
 
 `catalog search` filters:
 
-- `--origin <text>` -- filter by origin (country, continent, or region)
-- `--process <method>` -- filter by processing method (e.g. natural, washed)
-- `--price-min <n>` -- minimum price per lb (USD)
-- `--price-max <n>` -- maximum price per lb (USD)
-- `--flavor <keywords>` -- flavor keywords, comma-separated
-- `--name <text>` -- filter by coffee name (partial match, case-insensitive)
-- `--supplier <name>` -- filter by supplier/source name (partial match, case-insensitive)
-- `--ids <n,n,...>` -- fetch specific catalog IDs (comma-separated, ignores limit)
-- `--stocked` -- only show currently stocked coffees
-- `--variety <text>` -- filter by coffee variety/cultivar (partial match)
-- `--drying-method <text>` -- filter by drying method (partial match)
-- `--stocked-days <n>` -- only show coffees stocked within N days
-- `--sort <price|price-desc|name|origin|newest>` -- sort results
-- `--offset <n>` -- skip N results for pagination
-- `--limit <n>` -- maximum results to return (default: 10)
+- `--origin <text>`; origin, country, continent, or region
+- `--process <method>`; processing method
+- `--price-min <n>`; minimum USD/lb
+- `--price-max <n>`; maximum USD/lb
+- `--flavor <keywords>`; comma-separated flavor terms
+- `--name <text>`; partial coffee name match
+- `--supplier <name>`; partial supplier match
+- `--ids <n,n,...>`; fetch specific catalog IDs, ignores limit and offset
+- `--variety <text>`; partial cultivar match
+- `--drying-method <text>`; partial drying method match
+- `--stocked-days <n>`; stocked within N days
+- `--stocked`; only currently stocked coffees
+- `--sort <price|price-desc|name|origin|newest>`
+- `--offset <n>`; pagination offset
+- `--limit <n>`; default `10`
 
 `catalog similar <id>` options:
 
-- `--threshold <0-1>` -- minimum similarity score (default: 0.70)
-- `--limit <n>` -- max results (default: 10)
-- `--stocked-only` -- only show currently stocked beans
+- `--threshold <0-1>`; default `0.70`
+- `--limit <n>`; default `10`
+- `--stocked-only`
 
 Examples:
 
@@ -224,57 +318,73 @@ purvey catalog search --supplier "Royal Coffee" --stocked --pretty
 purvey catalog search --ids "1182,1183,1200"
 purvey catalog search --stocked --sort price --offset 10 --limit 10
 purvey catalog similar 1182 --threshold 0.85 --stocked-only --pretty
-purvey catalog similar 1182 --json | jq '.[0]'
+purvey catalog stats --pretty
+purvey catalog get 1182 --pretty
 ```
 
+Notes:
+
+- Catalog commands require an authenticated `viewer` role.
+- `catalog get` and `catalog similar` both take `coffee_catalog.catalog_id`.
+- `catalog stats` returns aggregate catalog metrics, not your personal inventory metrics.
+
 ### inventory
 
 - `purvey inventory list`
 - `purvey inventory get <id>`
 - `purvey inventory add`
 - `purvey inventory update <id>`
-- `purvey inventory delete <id>` (use `--force` to cascade delete dependent roasts and sales)
+- `purvey inventory delete <id>`
 
-`inventory list` options:
+`inventory list` filters:
 
-- `--stocked` -- only show currently stocked beans
-- `--catalog-id <id>` -- filter by catalog ID
-- `--purchase-date-start <YYYY-MM-DD>` -- only show purchases on or after this date
-- `--purchase-date-end <YYYY-MM-DD>` -- only show purchases on or before this date
-- `--origin <country>` -- filter by country of origin (partial match)
-- `--limit <n>` -- maximum results (default: 20)
-- `--offset <n>` -- skip N results for pagination (default: 0)
+- `--stocked`
+- `--catalog-id <id>`
+- `--purchase-date-start <YYYY-MM-DD>`
+- `--purchase-date-end <YYYY-MM-DD>`
+- `--origin <country>`
+- `--limit <n>`; default `20`
+- `--offset <n>`; default `0`
 
 `inventory add` flags:
 
-- `--catalog-id <id>` -- [REQUIRED] coffee_catalog.catalog_id
-- `--qty <lbs>` -- [REQUIRED] quantity in pounds
-- `--cost <dollars>` -- bean cost in dollars
-- `--tax-ship <dollars>` -- tax and shipping cost in dollars
-- `--notes <text>` -- notes for this inventory item
-- `--purchase-date <YYYY-MM-DD>` -- purchase date (defaults to today)
-- `--form` -- interactive form mode
+- `--catalog-id <id>`; required in flag mode
+- `--qty <lbs>`; required in flag mode
+- `--cost <dollars>`
+- `--tax-ship <dollars>`
+- `--notes <text>`
+- `--purchase-date <YYYY-MM-DD>`
+- `--form`
 
 `inventory update <id>` flags:
 
-- `--qty <lbs>` -- updated quantity in pounds
-- `--cost <dollars>` -- updated bean cost
-- `--tax-ship <dollars>` -- updated tax/shipping cost
-- `--notes <text>` -- updated notes
-- `--stocked <true|false>` -- mark as stocked or not
+- `--qty <lbs>`
+- `--cost <dollars>`
+- `--tax-ship <dollars>`
+- `--notes <text>`
+- `--stocked <true|false>`
+
+`inventory delete <id>` options:
+
+- `--force`; cascade dependent roasts and sales
+- `--yes`; skip confirmation prompt
 
 Examples:
 
 ```bash
 purvey inventory list --stocked --pretty
-purvey inventory list --limit 20 --offset 20       # page 2
-purvey inventory list --csv > inventory.csv
 purvey inventory add --catalog-id 128 --qty 10 --cost 8.50
-purvey inventory add --catalog-id 42 --qty 5 --cost 6.25 --tax-ship 4.00
+purvey inventory add --form
 purvey inventory update 7 --stocked false
 purvey inventory delete 7 --yes
 ```
 
+Notes:
+
+- Inventory commands require an authenticated `member` role.
+- Inventory `id` is `green_coffee_inv.id`, not `catalog_id`.
+- `inventory delete` may require `--force` if dependent roasts or sales exist.
+
 ### roast
 
 - `purvey roast list`
@@ -287,69 +397,78 @@ purvey inventory delete 7 --yes
 
 `roast list` filters:
 
-- `--coffee-id <id>` -- filter by inventory item ID (green_coffee_inv.id)
-- `--roast-id <id>` -- filter by exact roast profile ID
-- `--batch-name <text>` -- filter by batch name (partial match, case-insensitive)
-- `--coffee-name <text>` -- filter by bean name (partial match, case-insensitive)
-- `--date-start <YYYY-MM-DD>` -- only show roasts on or after this date
-- `--date-end <YYYY-MM-DD>` -- only show roasts on or before this date
-- `--stocked` -- only show roasts for currently stocked beans
-- `--catalog-id <id>` -- filter by coffee_catalog ID
-- `--limit <n>` -- maximum results (default: 20)
-- `--offset <n>` -- skip N results for pagination (default: 0)
+- `--coffee-id <id>`; inventory item ID
+- `--roast-id <id>`; exact roast profile ID
+- `--batch-name <text>`
+- `--coffee-name <text>`
+- `--date-start <YYYY-MM-DD>`
+- `--date-end <YYYY-MM-DD>`
+- `--stocked`
+- `--catalog-id <id>`
+- `--limit <n>`; default `20`
+- `--offset <n>`; default `0`
 
 `roast get <id>` options:
 
-- `--include-temps` -- include temperature curve data
-- `--include-events` -- include roast event markers
+- `--include-temps`
+- `--include-events`
 
 `roast create` flags:
 
-- `--coffee-id <id>` -- [REQUIRED] green_coffee_inv ID
-- `--batch-name <name>` -- batch name (defaults to coffee name + today's date)
-- `--oz-in <oz>` -- green weight in ounces
-- `--oz-out <oz>` -- roasted weight in ounces
-- `--roast-date <YYYY-MM-DD>` -- roast date (defaults to today)
-- `--notes <text>` -- roast notes
-- `--form` -- interactive form mode
+- `--coffee-id <id>`; required in flag mode
+- `--batch-name <name>`
+- `--oz-in <oz>`
+- `--oz-out <oz>`
+- `--roast-date <YYYY-MM-DD>`
+- `--notes <text>`
+- `--form`
 
-`roast update <id>` fields:
+`roast update <id>` flags:
 
-- `--notes <text>` -- updated roast notes
-- `--oz-out <oz>` -- updated roasted weight (triggers weight loss recalculation)
-- `--batch-name <name>` -- updated batch name
-- `--targets <text>` -- updated roast targets
+- `--batch-name <name>`
+- `--oz-out <oz>`
+- `--notes <text>`
+- `--targets <text>`
 
 `roast import [file]` flags:
 
-- `--coffee-id <id>` -- [REQUIRED] green_coffee_inv ID
-- `--batch-name <name>` -- batch name (auto-generated if omitted)
-- `--oz-in <oz>` -- green weight (extracted from .alog if present, overridden here)
-- `--roast-notes <text>` -- additional roast notes
-- `--form` -- interactive form mode
+- `--coffee-id <id>`; required unless `--form`
+- `--batch-name <name>`
+- `--oz-in <oz>`
+- `--roast-notes <text>`
+- `--roast-targets <text>`
+- `--form`
 
 `roast watch [directory]` options:
 
-- `--coffee-id <id>` -- [REQUIRED unless --auto-match] inventory ID for all imports
-- `--batch-prefix <name>` -- batch name prefix for auto-named batches
-- `--prompt-each` -- prompt for bean selection on each new file
-- `--auto-match` -- auto-match beans per file (mutually exclusive with --coffee-id)
-- `--resume` -- resume a previous watch session
-- `--form` -- interactive setup wizard
+- `--coffee-id <id>`; required unless `--auto-match`
+- `--batch-prefix <name>`
+- `--prompt-each`
+- `--auto-match`
+- `--commit-mode <batch|individual>`
+- `--oz-in <oz>`
+- `--roast-notes <text>`
+- `--roast-targets <text>`
+- `--resume`
+- `--form`
 
 Examples:
 
 ```bash
 purvey roast list --catalog-id 128 --pretty
-purvey roast list --batch-name "Ethiopia Guji" --pretty
-purvey roast list --date-start 2026-03-01 --date-end 2026-03-31
-purvey roast list --limit 20 --offset 20           # page 2
+purvey roast get 123 --include-temps --pretty
 purvey roast create --coffee-id 7 --batch-name "Ethiopia Guji Light" --oz-in 16
-purvey roast update 123 --targets "Aim for FC at 390F, 18% dev"
-purvey roast import ~/artisan/ethiopia.alog --coffee-id 7
+purvey roast import ~/artisan/ethiopia.alog --coffee-id 7 --roast-targets "Aim for 18% development"
 purvey roast watch ~/artisan/ --auto-match
 ```
 
+Notes:
+
+- Roast commands require an authenticated `member` role.
+- `--coffee-id` uses inventory IDs.
+- `roast watch --auto-match` is mutually exclusive with `--coffee-id`.
+- `roast watch --commit-mode` defaults to `batch`.
+
 ### sales
 
 - `purvey sales list`
@@ -359,123 +478,150 @@ purvey roast watch ~/artisan/ --auto-match
 
 `sales list` filters:
 
-- `--roast-id <id>` -- filter by roast profile ID
-- `--date-start <YYYY-MM-DD>` -- only show sales on or after this date
-- `--date-end <YYYY-MM-DD>` -- only show sales on or before this date
-- `--buyer <name>` -- filter by buyer name (partial match, case-insensitive)
-- `--limit <n>` -- maximum results (default: 20)
-- `--offset <n>` -- skip N results for pagination (default: 0)
+- `--roast-id <id>`
+- `--date-start <YYYY-MM-DD>`
+- `--date-end <YYYY-MM-DD>`
+- `--buyer <name>`
+- `--limit <n>`; default `20`
+- `--offset <n>`; default `0`
 
 `sales record` flags:
 
-- `--roast-id <id>` -- [REQUIRED] roast_data.roast_id
-- `--oz <amount>` -- [REQUIRED] ounces sold
-- `--price <dollars>` -- [REQUIRED] total sale price in dollars
-- `--buyer <name>` -- buyer name or identifier
-- `--sell-date <YYYY-MM-DD>` -- sale date (defaults to today)
-- `--form` -- interactive form mode
+- `--roast-id <id>`; exact selector mode
+- `--coffee-id <id>`; resolved selector mode, requires `--batch-name`
+- `--batch-name <name>`; resolved selector mode, requires `--coffee-id`
+- `--oz <amount>`; required in flag mode
+- `--price <dollars>`; required in flag mode
+- `--buyer <name>`
+- `--sell-date <YYYY-MM-DD>`
+- `--form`
 
 `sales update <id>` flags:
 
-- `--oz <amount>` -- updated ounces sold
-- `--price <dollars>` -- updated sale price
-- `--buyer <name>` -- updated buyer name
-- `--sell-date <YYYY-MM-DD>` -- updated sale date
+- `--oz <amount>`
+- `--price <dollars>`
+- `--buyer <name>`
+- `--sell-date <YYYY-MM-DD>`
+
+`sales delete <id>` options:
+
+- `--yes`
 
 Examples:
 
 ```bash
 purvey sales record --roast-id 123 --oz 12 --price 22.00 --buyer "Jane Smith"
+purvey sales record --coffee-id 7 --batch-name "Ethiopia Guji Light" --oz 8 --price 16.00
 purvey sales list --pretty
-purvey sales list --limit 20 --offset 20           # page 2
 purvey sales update 5 --price 24.00
 purvey sales delete 5 --yes
 ```
 
+Notes:
+
+- Sales commands require an authenticated `member` role.
+- Use exactly one selector mode for `sales record`: exact `--roast-id`, or resolved `--coffee-id` plus `--batch-name`.
+- If resolved mode matches multiple roasts, rerun with `--roast-id`.
+- `--price` is total sale price, not per-ounce price.
+
 ### tasting
 
-- `purvey tasting get <catalog-id>` -- retrieve tasting notes (uses `coffee_catalog.catalog_id`)
-- `purvey tasting rate [inventory-id]` -- record cupping scores (uses `green_coffee_inv.id`)
+- `purvey tasting get <catalog-id>`
+- `purvey tasting rate [inventory-id]`
+
+ID distinction:
 
-**ID distinction:** `tasting get` takes a `catalog_id`; `tasting rate` takes an `inventory id`. These are different numbers. Use `purvey catalog search` to find a `catalog_id` and `purvey inventory list` to find your `inventory id`.
+- `tasting get` takes a `catalog_id`
+- `tasting rate` takes an `inventory id`
 
 `purvey tasting get <catalog-id>` options:
 
-- `--filter <user|supplier|both>` -- which notes to show (default: both)
+- `--filter <user|supplier|both>`; default `both`
 
 `purvey tasting rate [inventory-id]` options:
 
-- `--aroma <1-5>` -- [REQUIRED in flag mode]
-- `--body <1-5>` -- [REQUIRED in flag mode]
-- `--acidity <1-5>` -- [REQUIRED in flag mode]
-- `--sweetness <1-5>` -- [REQUIRED in flag mode]
-- `--aftertaste <1-5>` -- [REQUIRED in flag mode]
-- `--brew-method <method>` -- brew method used (e.g. pour_over, espresso)
-- `--notes <text>` -- additional tasting notes
-- `--form` -- interactive form mode
+- `--aroma <1-5>`; required in flag mode
+- `--body <1-5>`; required in flag mode
+- `--acidity <1-5>`; required in flag mode
+- `--sweetness <1-5>`; required in flag mode
+- `--aftertaste <1-5>`; required in flag mode
+- `--brew-method <method>`
+- `--notes <text>`
+- `--form`
 
 Examples:
 
 ```bash
-# catalog_id 128 = the bean in the catalog
 purvey tasting get 128 --filter both --pretty
-# inventory id 7 = your physical purchase from inventory
 purvey tasting rate 7 --aroma 4 --body 3 --acidity 5 --sweetness 4 --aftertaste 4
-purvey tasting rate 42 --aroma 3 --body 3 --acidity 3 --sweetness 3 --aftertaste 3 --notes "Underextracted"
+purvey tasting rate --form
 ```
 
-### config
+Notes:
 
-- `purvey config list`
-- `purvey config get <key>`
-- `purvey config set <key> <value>`
-- `purvey config reset`
+- Tasting commands require an authenticated `member` role.
+- `tasting get` combines supplier notes with your own notes when available.
+- `tasting rate` writes scores back to your inventory row.
 
-Current config key:
+### config
 
-- `form-mode`: when set to `true`, write commands enter interactive mode when required args are missing
+- `purvey config list` (supports `--json`, `--pretty`)
+- `purvey config get <key>` (supports `--json`, `--pretty`)
+- `purvey config set <key> <value>` (supports `--json`, `--pretty`)
+- `purvey config reset` (supports `--json`, `--pretty`)
 
-Output behavior:
+Current config key:
 
-- Interactive terminals keep config commands human-readable by default
-- `--json` or `--pretty`, or any non-interactive stdout, emits JSON on stdout
-- `--csv` is not supported for config commands
+- `form-mode`: when `true`, write commands enter interactive mode when required args are missing
 
 Examples:
 
 ```bash
 purvey config set form-mode true
-purvey config get form-mode
 purvey config get form-mode --json
 purvey config reset --json
 ```
 
+Notes:
+
+- Config commands are local-only.
+- Config file path: `~/.config/purvey/config.json`
+- `--csv` is not supported.
+
 ### context
 
 - `purvey context`
 - `purvey context --json`
 - `purvey context --pretty`
 
-`purvey context` defaults to dense, human-readable, source-aware CLI reference text.
+Notes:
 
-Use `--json` or `--pretty` when you want the same machine-readable manifest that `purvey manifest` emits.
+- Default output is the dense human-readable operator reference text.
+- `--json` and `--pretty` emit the same machine-readable manifest as `purvey manifest`.
+- Prefer `purvey manifest` for new machine integrations. Use `purvey context --json` when you need compatibility with an existing `context`-based workflow.
+- Use `@purveyors/cli/manifest` when you need that same contract in-process from Node.js or an agent runtime.
+- `--csv` is not supported.
 
 ### manifest
 
 - `purvey manifest`
+- `purvey manifest --json`
 - `purvey manifest --pretty`
 
-Use this when an agent or script needs the machine-readable contract directly. `purvey manifest` emits compact JSON by default.
-
-`purvey manifest` and `purvey context --json` emit the same JSON manifest.
+Notes:
 
-If you want indented JSON, add `--pretty` to either command.
+- `purvey manifest` emits the preferred stable machine-readable CLI contract on stdout.
+- `purvey manifest` and `purvey manifest --json` both emit compact JSON.
+- `purvey manifest --pretty` emits indented JSON.
+- `purvey manifest` and `purvey context --json` emit the same JSON payload.
+- Use `purvey manifest` for new automation and treat `purvey context --json` as a compatibility alias.
+- `--csv` is not supported.
 
-### in-process manifest
+### In-process manifest export
 
 - `@purveyors/cli/manifest`
 
-Use this when you need the same contract from Node.js without shelling out to the CLI. This package subpath is exported via `./manifest` in `package.json`.
+Use this when you need the same stable contract from Node.js without shelling out to the CLI. This package subpath is exported via `./manifest` in `package.json` and is part of the supported public machine surface for agents and scripts.
 
 ```ts
 import { getCliManifest } from '@purveyors/cli/manifest';
@@ -483,17 +629,16 @@ import { getCliManifest } from '@purveyors/cli/manifest';
 const manifest = getCliManifest();
 ```
 
-## Common Workflows
+## Common workflows
 
-### Buy coffee, roast it, rate it, and record a sale
+### Catalog to inventory to roast to sale
 
 ```bash
 purvey catalog search --origin "Ethiopia" --process "natural" --stocked --pretty
 purvey inventory add --catalog-id 128 --qty 10 --cost 8.50
-purvey inventory list --stocked --pretty
 purvey roast import ~/artisan/guji-light.alog --coffee-id 7 --pretty
 purvey tasting rate 7 --aroma 5 --body 3 --acidity 5 --sweetness 4 --aftertaste 4
-purvey sales record --roast-id 123 --oz 12 --price 22.00 --buyer "Jane Smith"
+purvey sales record --coffee-id 7 --batch-name "Ethiopia Guji Light" --oz 12 --price 22.00 --buyer "Jane Smith"
 ```
 
 ### Continuous Artisan watch mode
@@ -512,53 +657,57 @@ purvey roast list --csv > roasts.csv
 purvey sales list --csv > sales.csv
 ```
 
-## ID Reference
+### Bootstrap an agent or script
+
+```bash
+purvey manifest
+purvey context
+purvey auth login --headless
+purvey auth status 2>/dev/null | jq .
+```
+
+## ID reference
 
 Use the right ID for the right command.
 
-- `catalog_id`: coffee_catalog rows; used by `catalog get`, `inventory add --catalog-id`, `tasting get`, `roast list --catalog-id`
-- `inventory id`: green_coffee_inv rows; used by `inventory get/update/delete`, `roast --coffee-id`, `tasting rate`, `roast list --coffee-id`
-- `roast_id`: roast_data rows; used by `roast get/delete`, `sales --roast-id`, `roast list --roast-id`
-- `sale id`: coffee_sales rows; used by `sales update/delete`
+- `catalog_id`: `coffee_catalog` rows; used by `catalog get`, `inventory add --catalog-id`, `tasting get`, `roast list --catalog-id`
+- `inventory id`: `green_coffee_inv` rows; used by `inventory get/update/delete`, `roast --coffee-id`, `tasting rate`, `roast list --coffee-id`
+- `roast_id`: `roast_data` rows; used by `roast get/delete`, `sales --roast-id`, `roast list --roast-id`
+- `sales record` also supports resolving a roast from `inventory id` plus `--batch-name`; if that selector is ambiguous, use exact `roast_id`
+- `sale id`: `coffee_sales` rows; used by `sales update/delete`
 
-## Environment Variables
+## Environment variables
 
 - `PURVEYORS_SUPABASE_URL`: override the Supabase project URL
 - `PURVEYORS_SUPABASE_ANON_KEY`: override the Supabase anon key
 - `PURVEYORS_BASE_URL`: override the Purveyors web base URL
 - `PURVEY_DEBUG`: enable verbose error output
 
-## For AI Agents
+## For AI agents
 
-Start here:
+Recommended bootstrap order:
 
 ```bash
 purvey manifest
 purvey context
-```
-
-Recommended flow:
-
-```bash
 purvey auth login --headless
-purvey auth status 2>/dev/null | jq .
-purvey inventory list | jq '.[].id'
 ```
 
-The CLI is designed to be agent-friendly:
+Use `purvey manifest` as the authoritative machine-readable entry point. Keep `purvey context` for dense operator context, or use `purvey context --json` only when you need compatibility with an existing wrapper.
+
+Why this CLI works well for agents:
 
 - stable command names
-- structured output on stdout
+- structured stdout by default
 - headless auth flow
-- copy-pasteable examples
-- a dedicated `manifest` command for machine-readable onboarding
-- a dedicated `context` command for dense human-readable onboarding
+- documented exit codes and role boundaries
+- dedicated machine-readable manifest command
+- dedicated dense human-readable reference command
 - `purvey context --json` parity with `purvey manifest`
-- an `@purveyors/cli/manifest` export for in-process access
-- documented exit codes for programmatic error handling
-- `--offset` + `--limit` pagination on all list commands
+- `@purveyors/cli/manifest` export for in-process access
+- `--offset` and `--limit` pagination across list commands
 
-The scripting contract: stdout is always structured success data (JSON or CSV). stderr carries status/spinner output plus fatal errors. In structured or non-interactive modes, fatal errors are JSON envelopes on stderr; in interactive no-flag mode, they stay human-readable. Exit codes are stable and documented above. Never expect success data on stderr.
+The scripting contract is simple: stdout carries successful payloads, stderr carries status and fatal errors, and exit codes stay stable.
 
 ## Troubleshooting
 
@@ -566,31 +715,29 @@ The scripting contract: stdout is always structured success data (JSON or CSV).
 
 ```bash
 purvey auth login
-# or for headless environments:
+# or
 purvey auth login --headless
 ```
 
-**Catalog commands fail with auth error after logging in**
+**Catalog commands fail after logging in**
 
-Run `purvey auth status` to confirm you have a `viewer` or `member` role. Both are granted automatically on sign-in. If auth status shows a stale session, run `purvey auth logout` then log in again.
+Run `purvey auth status` to confirm you have a `viewer` or `member` role. If the session is stale, run `purvey auth logout` and log in again.
 
 **Wrong ID type passed to a command**
 
-The most common mistake is mixing up ID types. Check the [ID Reference](#id-reference) section above. Use `purvey catalog search` to find `catalog_id` values; use `purvey inventory list` to find `inventory id` values.
+Use the [ID reference](#id-reference) section above. `catalog_id` and inventory IDs are different values.
 
-**Pagination: only seeing the first 20 results**
+**Pagination only shows the first page**
 
-All list commands default to 20 results. Use `--limit` and `--offset` to page through larger sets:
+All list commands default to 20 results. Use `--limit` and `--offset`.
 
 ```bash
-purvey inventory list --limit 20 --offset 0    # page 1
-purvey inventory list --limit 20 --offset 20   # page 2
-purvey inventory list --limit 20 --offset 40   # page 3
+purvey inventory list --limit 20 --offset 0
+purvey inventory list --limit 20 --offset 20
+purvey inventory list --limit 20 --offset 40
 ```
 
-**`inventory delete` fails with dependency conflict (exit code 5)**
-
-The item has dependent roast profiles or sales records. Use `--force` to cascade delete:
+**`inventory delete` fails with dependency conflict**
 
 ```bash
 purvey inventory delete 7 --force --yes
@@ -609,11 +756,16 @@ git clone https://github.com/reedwhetstone/purveyors-cli
 cd purveyors-cli
 pnpm install
 npm run build
+npm run verify:contract
+npm run verify:dist
+npm run verify:prepublish
 npm run check
 npm run lint
 npm test
 ```
 
+`npm run verify:prepublish` is the release guardrail. It rebuilds first, re-runs the targeted manifest and output-contract suites, checks the compiled `dist/` artifact, verifies the `npm pack --dry-run` publish surface, and smoke-tests `package.json`, `README.md`, `purvey manifest`, `purvey context --json`, and `@purveyors/cli/manifest`.
+
 Key files:
 
 - `src/index.ts`: executable entrypoint
@@ -622,12 +774,15 @@ Key files:
 - `src/lib/`: business logic and Supabase integration
 - `src/commands/context.ts`: dense human-readable agent reference
 - `src/commands/manifest.ts`: machine-readable CLI manifest command
-- `src/lib/manifest.ts`: shared manifest contract and renderer
+- `src/lib/manifest.ts`: shared manifest contract, package export list, command metadata, ID guidance, and context renderer
 - `package.json`: package metadata and export surface, including `./manifest`
-- `AGENTS.md`: contributor guide
+- `tests/dist-contract.test.ts`: compiled artifact parity guardrails
+- `AGENTS.md`: canonical contributor guide
+
+Live documentation:
 
-Live documentation: [purveyors.io/docs](https://purveyors.io/docs)
-Package: [npmjs.com/package/@purveyors/cli](https://www.npmjs.com/package/@purveyors/cli)
+- <https://purveyors.io/docs/cli/overview>
+- <https://purveyors.io/docs/api/overview>
 
 ## License