@pathmode/cli 2.0.2 → 2.1.0

package/README.md

@@ -17,9 +17,15 @@ pathmode --version
 You can also run it without installing:
 
 ```bash
-npx @pathmode/cli validate
+npx @pathmode/cli preflight
 ```
 
+That runs the deterministic readiness gate on the `intent.md` in your directory, or on the
+OpenSpec change your repo is working on, with no account and nothing leaving your machine. It
+prints what it read for each dimension before the verdict, so a blocked check shows the text it
+judged rather than just an accusation. Exits non-zero when the gate blocks, so it drops into CI
+as-is.
+
 ## Quick start
 
 ```bash
@@ -28,7 +34,7 @@ pathmode login          # paste your pm_live_ API key
 pathmode init           # write intent.md, .cursorrules, CLAUDE.md
 ```
 
-`validate` works with no account. The other five commands talk to the Pathmode API and need a key.
+`preflight` and `validate` work with no account. The other five commands talk to the Pathmode API and need a key.
 
 ## Authentication
 
@@ -57,6 +63,7 @@ Environment variables take precedence over the config file, so use them in CI in
 
 | Command | What it does | Needs auth |
 |---|---|---|
+| [`preflight`](#preflight-path) | Run the readiness gate on an intent.md or OpenSpec change | No |
 | [`validate`](#validate-file) | Check a spec against the IntentSpec schema | No |
 | [`login`](#login) | Store and verify your API key | Sets it up |
 | [`init`](#init) | Scaffold intent files in a fresh repo | Yes |
@@ -64,6 +71,22 @@ Environment variables take precedence over the config file, so use them in CI in
 | [`push`](#push) | Send status changes and notes back | Yes |
 | [`status`](#status) | List workspace intents and their status | Yes |
 
+### `preflight [path]`
+
+```bash
+pathmode preflight                             # ./intent.md, else the active OpenSpec change
+pathmode preflight specs/login.md              # a specific intent file
+pathmode preflight openspec/changes/add-auth   # an OpenSpec change directory
+```
+
+Six deterministic checks: title, objective, outcomes, constraints, edge cases, verification. Pure
+functions, no model call, no network; the same spec always gets the same verdict. A `?` means the
+check read your text and could not confirm it, which is often the check's fixed vocabulary rather
+than your writing. Reading an OpenSpec change writes nothing.
+
+Exit codes: `0` ready, `1` the gate blocks, `2` nothing to grade. With several OpenSpec changes
+present it refuses to guess and lists them.
+
 ### `validate [file]`
 
 Validates the YAML frontmatter of a markdown file against the [IntentSpec schema](https://intentspec.org/schema.json). Exits `0` when valid and `1` when not, printing each failed field, so it works as a CI gate.