coderifts 8.3.0 → 8.5.0

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## Unreleased
+
+## 8.5.0 - 2026-09-07
+
+The generated check-summary reads the rulesets API when there is no classic branch protection (a ruleset-governed repo no longer reports protection_not_configured). The quickstart's Atomic example carries the issuer-grant keyring. The strict workflow template pins contract-gate at d1c348d (v0.9.0), the current gate commit.
+
+
+## 8.4.0 - 2026-09-06
+
+### Added
+- Published onboarding for Atomic V2: `coderifts init --agents --atomic-v2` (and `init --strict --atomic-v2`) writes an `ENFORCING_ATOMIC_V2` config plus fail-closed wiring placeholders (`PROFILE_CONFIGURED` / `WIRING_REQUIRED`, `atomic_v2_verified: false`). `coderifts verify atomic-v2` is in the packed binary (exit **0** `TARGET_ENFORCEMENT_VERIFIED` for a named reference target; **2** `WIRING_REQUIRED` for a customer target until the six adapter operations are wired; **3** `VERIFICATION_FAILED`; **1** usage). Packed-install smoke runs `coderifts init --agents --atomic-v2 --dry-run`.
+- ATOMIC_V2 phase 2 (réteg 3): versioned adapter-contract `atomic-v2-adapter/1` (six operations: `state_challenge`, `consume`, `conditional_write`, `mutate`, `executor_attestation`, `provider_readback`). Capability discovery is a machine probe. `coderifts verify atomic-v2` is target-bound (`--target --environment --executor-identity --operation --adapter-id`); reference-executor success is not inherited. Mandatory negative probes (replay, expired challenge, wrong target, CAS mismatch, missing attestation, mismatched JTI/scope-hash) must fail-close. `customer_target_verified:false` + `production_ready:true` is unconstructible.
+- `coderifts init --strict --atomic-v2` writes an `ENFORCING_ATOMIC_V2` config plus fail-closed `unconfiguredCapability` wiring placeholders (`PROFILE_CONFIGURED` / `WIRING_REQUIRED`, `atomic_v2_verified: false`). Init may succeed; verify must not exit 0 on incomplete wiring. Placeholders throw; they are not no-ops.
+
+### Changed
+- Strict installer teaching (`coderifts init --agents --strict`): primary production grant is `cr.exec.v2` (mint with `grantVersion: 'v2'`). `cr.exec.v1` is labelled legacy; the gate still accepts both so a migration is not a hard cut. `ENFORCING_ATOMIC_V2` is not the installer default — that profile needs customer-held executor wiring this installer cannot emit.
+- `inescapable_deploy` is false while `MERGEGATE_ENFORCE` is unobservable. All six layers `VERIFIED` is a proven binding, not a proven inescapable deploy; the composite reads `CLAMP_RESIDUAL` on `required_check` (classic and ruleset). True only when `MERGEGATE_ENFORCE` is observably `'true'`.
+
 ## 8.3.0 - 2026-09-05
 
 ### Changed

package/README.md

@@ -75,7 +75,9 @@ coderifts init --agents --hosts=cursor   # Cursor only
 coderifts init --agents --hosts=copilot  # GitHub Copilot / VS Code only
 coderifts init --agents --no-hook        # skip host hook install
 coderifts init --agents --no-workflow    # skip .github/workflows/coderifts.yml
-coderifts init --agents --strict         # STRICT: require-verified-monitoring: true
+coderifts init --agents --strict         # STRICT: require-verified-monitoring + require-grant (cr.exec.v2 primary)
+coderifts init --strict --atomic-v2      # ATOMIC_V2 config + fail-closed wiring (implies --agents --strict)
+coderifts verify atomic-v2               # 0 TARGET_ENFORCEMENT_VERIFIED; 2 WIRING_REQUIRED; 3 VERIFICATION_FAILED; 1 usage
 coderifts init --agents --check          # which of the four pieces are present
 ```
 
@@ -84,17 +86,28 @@ coderifts init --agents --check          # which of the four pieces are present
 | **MCP config** | `.mcp.json` (Claude Code), `.cursor/mcp.json` (Cursor), `.vscode/mcp.json` (Copilot / VS Code) | Three shapes, never normalised into one: Claude `mcpServers` + `type: "http"` + `url`; Cursor `mcpServers` + `url` only (no `type`); Copilot **`servers`** (not `mcpServers`) + `type: "http"` + `url`. Never `httpUrl` (that is Gemini, extension-level — this command does not write it). |
 | **Agent rules** | generated host files via `agent-setup`'s writer | `AGENTS.md` is always written. Claude also gets `CLAUDE.md`; Cursor also gets `.cursor/rules/coderifts.mdc`; Copilot also gets `.github/copilot-instructions.md`. `--hosts=all` adds LangGraph and OpenAI instructions. (`coderifts init agent` is a different command — it writes a `.coderifts.yml` template.) |
 | **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'` |
+| **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'` and `require-grant: 'true'` (teaches `cr.exec.v2`) |
 
 **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`. |
+| `cr.exec.v2` | `coderifts init --agents --strict` (`require-grant`); Guard/SDK when `grantVersion: 'v2'` | Canonical production execution grant. Not the same bytes as v1. Mint with `grantVersion: 'v2'`. |
+| `cr.exec.v1` | capability-demo; legacy/migration | Older reference grant bound to `operation ∥ target_id ∥ after_payload`. Not the installer default. The gate still accepts it so a migration is not a hard cut. |
+| `ENFORCING_STRICT` | Guard `withCodeRifts({ profile })` | Permanent alias of `ENFORCING_STRICT_V1` (must resolve to `_V1` forever). Installer-reachable production lock. Not a grant format. Different axis from `ENFORCING_ATOMIC_V1`/`V2` — those require customer-held executor wiring this installer does not emit. |
 
-`--strict` turns on `require-grant` and `require-verified-monitoring` in the workflow; it does not rename those three things.
+`--strict` turns on `require-grant` and `require-verified-monitoring` in the workflow; it teaches `cr.exec.v2` as the grant to mint. It does not emit `ENFORCING_ATOMIC_V2`.
+
+`--atomic-v2` writes `.coderifts/atomic-v2.json` plus fail-closed `unconfiguredCapability` wiring placeholders. Init may exit 0 with `PROFILE_CONFIGURED` / `WIRING_REQUIRED` (`state: ATOMIC_V2_CONFIGURED`, `atomic_v2_verified: false`). That is configuration, not target enforcement. `coderifts verify atomic-v2` is the verifier and **must not exit 0** while placeholders remain:
+
+| Exit | Meaning |
+|------|---------|
+| **0** | `TARGET_ENFORCEMENT_VERIFIED` — customer target fully verified |
+| **2** | `WIRING_REQUIRED` — config installed, placeholders still throw |
+| **3** | `VERIFICATION_FAILED` — wiring present but verification failed (including a document that claimed `verified:true` with incomplete wiring) |
+| **1** | usage / missing config |
+
+Never emit `state: ENFORCING_ATOMIC_V2` with `atomic_v2_verified: true` while any of the adapter-contract (`atomic-v2-adapter/1`) operations is missing: `state_challenge`, `consume`, `conditional_write`, `mutate`, `executor_attestation`, `provider_readback`. Discovery is a machine probe, not a customer boolean. Exit 0 is target-bound (`--target --environment --executor-identity --operation --adapter-id`); a reference-executor success is not inherited. `customer_target_verified:false` and `production_ready:true` cannot be constructed together. The names are `PROFILE_CONFIGURED` / `TARGET_ENFORCEMENT_VERIFIED`, not STRICT-vs-ATOMIC (that pairing would read as a weaker-but-acceptable end state).
 
 **Next manual step:** add `CODERIFTS_API_KEY` to the repository secrets. The
 CLI never writes a key anywhere.
@@ -477,7 +490,9 @@ coderifts enforce --check --repo owner/repo --env production --json
 Provider-native pipeline-protection evidence. This is **not** a host claim:
 `--enforce` and `CODERIFTS_DEPLOY_NO_BYPASS` do **not** set
 `inescapable_deploy`. The field is true only when every layer below is
-`VERIFIED`.
+`VERIFIED` **and** `MERGEGATE_ENFORCE` is observably true. A `VERIFIED`
+required-check binding whose reason names the unobservable clamp is not an
+inescapable deploy.
 
 | Layer | VERIFIED when |
 |-------|----------------|
@@ -488,7 +503,7 @@ Provider-native pipeline-protection evidence. This is **not** a host claim:
 | `workflow_contract_gate` | an **active** job (not `if: false`) has a step whose `uses:` is `coderifts/contract-gate` at a pinned major. Comments, string literals, and commented-out steps are **NOT_VERIFIED** |
 | `workflow_deploy_gate` | an **active** job step **invokes** `coderifts deploy-gate` (not `echo` of the string; not a comment) |
 
-**Invariant:** any layer whose evidence cannot be bound to an issuer (our GitHub App id) or to an active job is `NOT_VERIFIED` or `UNVERIFIABLE` — never `VERIFIED`. `inescapable_deploy` remains true only when every layer is `VERIFIED` under that rule.
+**Invariant:** any layer whose evidence cannot be bound to an issuer (our GitHub App id) or to an active job is `NOT_VERIFIED` or `UNVERIFIABLE` — never `VERIFIED`. `inescapable_deploy` remains true only when every layer is `VERIFIED` **and** `MERGEGATE_ENFORCE` is observably true.
 
 Statuses: `VERIFIED` / `NOT_VERIFIED` / `UNVERIFIABLE(reason)`. Auth:
 `GITHUB_TOKEN` (never printed). **No token** → API layers `UNVERIFIABLE` with

package/bin/coderifts.js

@@ -165,7 +165,8 @@ program
   .option('--hosts <list>', 'With --agents: claude, cursor, copilot, or all (default: all)', 'all')
   .option('--no-hook', 'With --agents: skip host hook install')
   .option('--no-workflow', 'With --agents: skip writing .github/workflows/coderifts.yml')
-  .option('--strict', 'With --agents: STRICT workflow (require-verified-monitoring: true)')
+  .option('--strict', 'With --agents: STRICT workflow (require-verified-monitoring + require-grant; cr.exec.v2 primary)')
+  .option('--atomic-v2', 'Write ENFORCING_ATOMIC_V2 config + fail-closed wiring (implies --agents --strict)')
   .option('--dry-run', 'With --agents: print the plan without writing')
   .option('--check', 'With --agents: report which of the four pieces are present (no write)')
   .option('--out <dir>', 'With --agents: target directory (default: cwd)')
@@ -176,7 +177,7 @@ program
       AGENT_FLAGS_REQUIRE_AGENTS,
       AGENTS_NO_TEMPLATE,
     } = require('../src/commands/init-agents');
-    if (options.agents) {
+    if (options.agents || options.atomicV2) {
       if (template) {
         console.error(AGENTS_NO_TEMPLATE);
         process.exitCode = 1;
@@ -189,7 +190,8 @@ program
         dryRun: !!options.dryRun,
         check: !!options.check,
         out: options.out,
-        strict: !!options.strict,
+        strict: !!options.strict || !!options.atomicV2,
+        atomicV2: !!options.atomicV2,
       });
       if (result && typeof result.exitCode === 'number') {
         process.exitCode = result.exitCode;
@@ -468,6 +470,34 @@ const corpusCmd = program
   .command('corpus')
   .description('Reproduce the CodeRifts accuracy proof matrix (MCP always; OpenAPI needs oasdiff)');
 
+program
+  .command('verify <target>')
+  .description('Verify an installed profile. Target: atomic-v2. Exit 0 = TARGET_ENFORCEMENT_VERIFIED (named target); 2 = WIRING_REQUIRED; 3 = VERIFICATION_FAILED; 1 = usage.')
+  .option('--out <dir>', 'Target directory (default: cwd)')
+  .option('--json', 'Print the structured status JSON')
+  .option('--target <id>', 'Bind verification to this target_id')
+  .option('--environment <env>', 'Bind verification to this environment')
+  .option('--executor-identity <id>', 'Bind verification to this executor identity')
+  .option('--operation <op>', 'Bind verification to this operation')
+  .option('--adapter-id <id>', 'Bind verification to this adapter_id')
+  .action((target, options) => {
+    if (String(target) !== 'atomic-v2') {
+      console.error(`verify: unknown target "${target}" (use atomic-v2)`);
+      process.exitCode = 1;
+      return;
+    }
+    const { runVerifyAtomicV2 } = require('../src/commands/verify-atomic-v2');
+    runVerifyAtomicV2({
+      out: options.out,
+      json: !!options.json,
+      target: options.target,
+      environment: options.environment,
+      executorIdentity: options.executorIdentity,
+      operation: options.operation,
+      adapterId: options.adapterId,
+    });
+  });
+
 corpusCmd
   .command('verify', { isDefault: true })
   .description('Evaluate every trust vector and print the proof matrix (exit 1 on any FAIL)')

package/dist/.build-source-sha

@@ -1,5 +1,5 @@
 {
   "$comment": "GENERATED by scripts/build.js. sha256 over src/**.js + bin/**.js (path + bytes). test/build-freshness.test.js recomputes it; a mismatch means dist/cli.js is stale.",
-  "sha256": "9596f98c3c463ea53896621305484fd1ca3c5685b15c410fa4205c07a285c709",
-  "file_count": 44
+  "sha256": "e9cca5e219ca1bc43448406afaae8ac9b4bd5f61dcbb880967393ea37575b354",
+  "file_count": 49
 }