coderifts 7.0.0 → 8.0.1

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 8.0.1 - 2026-09-02
+
+### Changed
+- `--require-workflow-binding` now gates the exit code: `enforce --check` exits non-zero when the required workflow is not SHA-pinned to the head (Action-path audit verdict; default off, advisory output unchanged without the flag).
+- The generated strict workflow pins contract-gate v0.8.0 (1fae5d2); the previously published 8.0.0 still pinned 0.7.0.
+- `@coderifts/agent-guard` range follows the published 15.1.0; embedded agent rule text regenerated (names cr.exec.v2 and ENFORCING_STRICT_V1 once).
+
+## 8.0.0
+
+### Security
+
+- **Installs from `coderifts@7.0.0` pinned contract-gate v0.5.0.** That action's vendored verifier accepted receipts signed by revoked keys. Fixed in contract-gate **0.7.0**. The strict install now pins **0.7.0 / `90de4be`**.
+
+### Breaking
+
+- **`@coderifts/agent-guard` declared `^15.0.0`** (`MIN_GUARD_MAJOR` 15). There is no `peerDependencies` entry — this is a **direct** dependency, so a fresh `npm i -g coderifts` resolves 15.x, not 14.x. The CLI still uses only `deployGate`, `asVerifiedDeployReceiptView`, `DEPLOY_RECEIPT_VIEW_SPEC`, and `matchGlob`.
+
+### Fixed
+
+- **Claude Code PreToolUse hook governs a path family**, not a single `coderifts.specPath`. Default globs cover OpenAPI/Swagger, GraphQL, `*.proto`, AsyncAPI, MCP manifests, and `*tool-schema*.json`. `git config --add coderifts.specPath` is additive (never drops the family). `coderifts.specPathExclude` opts one path out. A not-governed Write/Edit/MultiEdit exits 0 and prints `coderifts claude-hook: not governed: <path>` — the hook is never silent on those tools.
+
+### Docs
+
+- README **Grant versions** table: `cr.exec.v1` is the reference/teaching grant the demo and strict install use; the Atomic V2 request contract (`execution-grant-request.v2` fields) is what the SDK/Guard/executor speak; `ENFORCING_STRICT` is the current profile name and will become a versioned name.
+
 ## 7.0.0
 
 ### Breaking

package/README.md

@@ -86,6 +86,16 @@ coderifts init --agents --check          # which of the four pieces are present
 | **Host hook** | `.claude/settings.json`, `.cursor/hooks.json` | Reuses `hook install --claude` / `--cursor` (JSON-merge, backup, idempotent). Copilot shares Claude's `.claude/settings.json` — VS Code reads it by default. |
 | **CI workflow** | `.github/workflows/coderifts.yml` | `coderifts/contract-gate@v0`. Default: `require-verified-monitoring` commented (honest default: **false**). `--strict`: the same file with `require-verified-monitoring: 'true'` |
 
+**Grant versions** (these names are not interchangeable; field-by-field matrix: [Grant versions](https://github.com/coderifts/app/blob/main/docs/grant-versions.md)):
+
+| What | Who uses it | What it proves |
+|------|-------------|----------------|
+| `cr.exec.v1` | capability-demo and the strict-install workflow (`require-grant`) | A reference/teaching execution grant bound to `operation ∥ target_id ∥ after_payload`. The demo and `coderifts init --agents --strict` use this form. |
+| Atomic V2 request (the V2 fields of the authorize request; see docs/grant-versions.md) | TS SDK, Python SDK, Guard (not MCP; not the capability-demo executor) | The request contract those three speak when minting a grant. Not the same bytes as a `cr.exec.v1` token. |
+| `ENFORCING_STRICT` | Guard `withCodeRifts({ profile })` | Permanent alias of `ENFORCING_STRICT_V1` (must resolve to `_V1` forever). Not a grant format. Different axis from `ENFORCING_ATOMIC_V1`/`V2`. |
+
+`--strict` turns on `require-grant` and `require-verified-monitoring` in the workflow; it does not rename those three things.
+
 **Next manual step:** add `CODERIFTS_API_KEY` to the repository secrets. The
 CLI never writes a key anywhere.
 
@@ -287,7 +297,26 @@ Unparseable settings JSON → refuse, no write.
 ### Claude Code PreToolUse (`coderifts claude-hook`) — ID824
 
 Tool-call-time gate for **Claude Code**: blocks contract-touching `Write` /
-`Edit` / `MultiEdit` when authorize preflight returns **BLOCK/STOP**.
+`Edit` / `MultiEdit` when authorize preflight returns **BLOCK/STOP**. The
+matcher is tool-level (`Write|Edit|MultiEdit`); the **path family** is
+enforced inside the hook.
+
+**Default governed family** (from `SUPPORTED_TYPES` + `@coderifts/contract-path`
+`looksLikeContractPath` / `CONTRACT_EXT`; `agent_tools` via `*tool-schema*.json`):
+
+- `**/*openapi*.{yaml,yml,json}` and `**/*swagger*.{yaml,yml,json}` (openapi)
+- `**/*.{graphql,gql}` (graphql)
+- `**/*.proto` (grpc)
+- `**/*asyncapi*.{yaml,yml,json}` (asyncapi)
+- `**/*mcp*.{json,yaml,yml}` (mcp_manifest)
+- `**/*tool-schema*.json` (agent_tools)
+
+`node_modules/` and `vendor/` are not governed (same as the path detector).
+`git config --add coderifts.specPath <path-or-glob>` is **additive** (never
+replaces the family). `git config --add coderifts.specPathExclude <path-or-glob>`
+opts one path out. A not-governed path exits 0 and prints
+`coderifts claude-hook: not governed: <path>` on stderr — the hook is never silent
+on a write/edit.
 
 **Exit map (Claude Code semantics — fixed):**
 
@@ -299,11 +328,12 @@ Tool-call-time gate for **Claude Code**: blocks contract-touching `Write` /
 
 Push-time equivalent (git exit **1** on BLOCK): `coderifts hook install`.
 
-**Install path:** `coderifts hook install --claude` (or `agent-setup` writes project `.claude/settings.json` when absent). Then set key + spec:
+**Install path:** `coderifts hook install --claude` (or `agent-setup` writes project `.claude/settings.json` when absent). Then set key; spec path is optional and additive:
 
 ```bash
 git config coderifts.apiKey 'cr_live_…'          # or: coderifts login / CODERIFTS_API_KEY
-git config coderifts.specPath api/openapi.yaml   # default if omitted
+git config --add coderifts.specPath extra/spec.yaml          # additive; does not drop the family
+git config --add coderifts.specPathExclude docs/openapi.yaml # opt out one false positive
 ```
 
 **Recipe — project** (`.claude/settings.json`) **or user** (`~/.claude/settings.json`):
@@ -423,7 +453,7 @@ failed, **1** on missing repo/key, API error, or any apply failure.
 | `--branch <name>` | With `--check`: branch (default: repo default) | default branch |
 | `--provider <name>` | With `--check`: provider adapter. `github` only; others report UNVERIFIABLE and are never stubbed | `github` |
 | `--head-sha <sha>` | With `--check`: pull-request head commit, so the required-workflow pin can be compared with the bytes being merged | none |
-| `--require-workflow-binding` | With `--check`: also require a sha-pinned required workflow matching the head. **Default OFF** — without it the evidence still gains a `workflow_binding` section and neither the verdict nor the exit code changes | `false` |
+| `--require-workflow-binding` | With `--check`: **exit non-zero** when the required workflow is not sha-pinned to the head (`workflow_binding.grants_pass !== true`). Scope: the CLI's own audit verdict on the **Action path** — it is not the App-path merge clamp, which is decided server-side and is a separate control. **Default OFF** — without the flag the evidence is byte-identical, the verdict is unchanged and the exit code stays 0 (advisory) | `false` |
 | `--json` | Machine-readable JSON result | `false` |
 
 ```bash
@@ -492,7 +522,7 @@ coderifts provider-canary --repo owner/repo --confirm --json
 Encodes an **already-signed** execution grant plus the PR head sha into a
 comment marker on stdout, for the 1094 PR-comment delivery slot. **It does not
 mint a grant** (`src/commands/grant-publish.js:4`) — the token must already be a
-signed `cr.exec.v1` or `cr.exec.v2`.
+signed `cr.exec.v1` or `cr.exec.v2` (see **Grant versions** above).
 
 | Flag | Description | Default |
 |------|-------------|---------|