@nodii/dev 0.6.24 → 0.6.26

package/README.md

@@ -309,7 +309,8 @@ nodii-dev lane step KEY --side backend|frontend --start|--done|--block STEP [--r
                     # --block --reason records the new reason (Dev issue 125 moves it onto the step)
 nodii-dev lane evidence KEY --pr|--commit|--figma|--deploy|--dev-check REF
 nodii-dev lane heartbeat KEY [--note TEXT]
-nodii-dev lane review KEY
+nodii-dev lane review KEY --file REVIEW.json
+nodii-dev lane reviews KEY
 nodii-dev lane land KEY
 nodii-dev lane verify KEY --dev-check REF
 nodii-dev lane list [--kind KIND] [--status STATUS] [--machine UUID]
@@ -350,19 +351,40 @@ nodii-dev docs upload PATH... --class ruling|conformance|editorial
 nodii-dev docs ratify --domain KEY [--domain KEY ...] --decision DECISION.json [--wait]
 nodii-dev docs parked [CODE] [--status pending|acknowledged]
 
-nodii-dev harness install [--include-drafts] [--adopt PATH,...] [--dry-run]
-nodii-dev harness update [--include-drafts] [--adopt PATH,...] [--dry-run]
+nodii-dev harness install [--include-drafts] [--adopt PATH,...] [--dry-run] [--system]
+nodii-dev harness update [--include-drafts] [--adopt PATH,...] [--dry-run] [--system]
 nodii-dev harness check [--json]               # 0 current, 1 differs from Dev, 2 no harness
 nodii-dev harness update --check               # the same check
 ```
 
-`harness install` and `harness update` merge the two safety hooks into
-`.claude/settings.json`; every installed hook invokes only `nodii-dev`. The
+`harness install` and `harness update` merge the safety hooks into both
+`.claude/settings.json` and `.codex/hooks.json`; every installed hook invokes
+only `nodii-dev`. The
 pre-hook blocks edits outside a lane's optional `ownedPaths`, generated UI/API
 files, unsafe Git operations, stale or missing review receipts, lane identity
 changes, production-secret/test-auth bypasses, cleanup of Docker resources the
 run did not create, and deploy/apply commands without an exact grant. Allowed
-calls produce no output.
+calls produce no output. Codex receives runtime-native `Bash` and `apply_patch`
+matchers, JSON denials, and `additionalContext` nudges. A compact session start
+prints the current lane Freeze again.
+
+Hard blocks apply only after Dev proves the current agent, branch and worktree
+belong to an active lane. Interactive or otherwise unproven sessions receive
+nudges instead. Push is blocked only when that proven lane also exposes the
+review-receipt flow; until then the hook says it cannot verify the review and
+allows the command.
+
+Codex trusts system-managed hooks without a per-hash prompt. `--system` writes
+the repository harness normally and refreshes the user-owned dispatcher under
+`~/.config/nodii-dev/codex-managed-hooks`, then only prints the one-time
+`sudo install` commands an operator can review and run to place its stable
+policy in `/etc/codex/requirements.toml`; nodii-dev never runs sudo itself.
+That system layer covers both `CODEX_HOME=~/.codex` and
+`CODEX_HOME=~/.codex-work`; later `--system` updates need no sudo. The
+dispatcher records the absolute executable path so hook processes never
+depend on `PATH`, and refreshes it on every update. Outside a lane, or when
+that executable is missing or too old, it fails open without diagnostics;
+`doctor` reports that fail-open state for each Codex profile.
 
 Until Dev exposes a lane's owned paths (AGENT-HARNESS-10), an edit with no
 ownership field emits a nudge instead of claiming it is safe or blocking an
@@ -602,11 +624,14 @@ OAuth login.
 `harness install` writes the repository's agent harness as Dev generates it
 from the ratified methodology: the `CLAUDE.md` and `AGENTS.md` pointer
 blocks, one pointer skill per methodology document, the Claude Code hooks
-merged into `.claude/settings.json`, and Dev's `.nodii/harness.json`. Every
+merged into `.claude/settings.json`, their Codex equivalents merged into
+`.codex/hooks.json`, and Dev's `.nodii/harness.json`. Every
 generated file carries the methodology version it came from. Nothing about
 the rules is authored locally. Run it in the service's own repository: it
-installs one service at a time, and there is no fleet mode. `--include-drafts`
-uses draft methodology while none is ratified.
+installs one service at a time, and there is no fleet mode. While no
+methodology is ratified, install and update automatically retry with the
+latest draft versions and print the exact draft methodology and source
+versions they used. `--include-drafts` requests that behavior explicitly.
 
 The CLI records what it wrote in `.nodii/harness-state.json` and never touches
 anything else. An existing file it did not write is refused, unless the
@@ -654,6 +679,8 @@ exits 0 only when every check is `OK`. `--json` returns the same checks as
 | `lane_limit` | The agent's active lanes against its lane limit. A full limit is `OK` when a lane on this branch holds the slot. |
 | `figma_file` | Only with `--figma-file KEY` (a key or figma.com link), or `NODII_DEV_FIGMA_FILE`: whether Dev has the brief's Figma file registered. `MISSING` names the `figma file add` command, since `figma lock` would fail with `DESIGN_FILE_NOT_FOUND`. |
 | `figma_scopes` | With `figma_file`, when the file is registered: the change set this agent holds in the file and its lock scopes (or the whole file), or that it holds none (DEC-0032). |
+| `hooks_claude` | Whether Claude hooks are installed, trusted by that runtime, and have a private firing receipt. |
+| `hooks_codex_personal`, `hooks_codex_work` | For `~/.codex` and `~/.codex-work`, whether Codex's own hook registry reports the hooks installed and trusted (including managed status), whether the managed absolute CLI is present and new enough, and whether that profile has fired one. |
 
 Doctor may refresh the access token, as any command does. The permission table
 is kept by hand from Dev's route policy until Dev's OpenAPI names each
@@ -670,9 +697,9 @@ serves for that step (see Rule delivery). Server refusals,
 including operator-only actions, workflow blocks, lane limits and Built items
 that are not on dev, retain Dev's error code/message and exit non-zero.
 
-`setup` installs the Claude Code workflow harness in the current repository.
+`setup` installs the Claude Code and Codex workflow harnesses in the current repository.
 It writes `.claude/skills/nodii-build-workflow/SKILL.md`, merges SessionStart,
-Stop and Bash PostToolUse hooks into `.claude/settings.json`, and maintains one
+Stop and tool hooks into `.claude/settings.json` and `.codex/hooks.json`, and maintains one
 marked section in an existing `CLAUDE.md` or `AGENTS.md` (creating `CLAUDE.md`
 when neither exists). Existing settings and hooks are preserved. The default
 is a read-only preview; `--yes` applies, and `--check` is suitable for drift
@@ -712,6 +739,14 @@ The command reaches Dev through the edge, so it needs the edge's route for
 `/devops/api/v1/lanes/:id/non-issue`; until that is on an environment, the
 command gets the edge's 404 there.
 
+`lane review` reads one JSON object with the review's exact `origin/main`
+commit in `base`, exact reviewed commit in `head`,
+`iterationCount`, `exitReason`, `appliedPatches`, `unresolvedProposals`,
+`reviewerErrors`, and `findings`. Each finding has `perspective` (`code` or
+`rules`), `severity`, `summary`, `detail`, `disposition`, optional `path` and
+`line`, and a required `clauseId` for rules findings. `lane reviews` reads the
+append-only history, including whether each cited clause was a missed trigger.
+
 Heartbeat notes are optional and limited by Dev to 500 characters.
 Prioritize and deprioritize require a 1–500 character reason, which the CLI
 sends to Dev. `lane review` records the review gate.

package/dist/cli.js

@@ -20,11 +20,12 @@ import {
   refuseFromLane,
   revokeOAuth,
 } from "./oauth.js";
-import { heartbeatCurrentLane, postHook, postHookFailure, preHook, settingsSnippet, workflowSuggestion } from "./hooks.js";
+import { heartbeatCurrentLane, postHook, postHookFailure, preHook, sessionStartContext, settingsSnippet, workflowSuggestion } from "./hooks.js";
 import { setupCommand } from "./setup.js";
 import { harnessCommand } from "./harness.js";
-import { safetyPostHook, safetyPreHook } from "./safety.js";
+import { hookRuntime, recordHookFire, safetyPostHook, safetyPreHook } from "./safety.js";
 import { doctorCommand } from "./doctor.js";
+import { dispatchManagedHook } from "./managed-hooks.js";
 import {
   figmaChangeSetShow,
   figmaChangeSetText,
@@ -120,9 +121,10 @@ Usage: nodii-dev <command> [options] [--json]
   figma changeset show CHANGE_SET       # items, variants, round, decision and comment (with the previous round's)
   figma file add FILE_KEY --name TEXT --kind design-system|surfaces|prototype [--module M]
                                         # register a Figma file in Dev so it can be locked
-  hook claude-figma-pre|claude-figma-post|safety-pre|safety-post|print-settings
+  hook claude-figma-pre|claude-figma-post|safety-pre|safety-post|session-start|managed-dispatch|print-settings
   setup [--yes|--check]                 # dry-run by default
-  harness install|update [--include-drafts[=false]] [--adopt PATH,...] [--dry-run]
+  harness install|update [--include-drafts[=false]] [--adopt PATH,...] [--dry-run] [--system]
+                                        # --system stages managed hooks and only prints operator-reviewed sudo commands
   harness check                         # 0 current, 1 differs from Dev, 2 not installed
   harness update --check                # the same check
   docs check|validate|upload <path...> --class ruling|conformance|editorial
@@ -139,7 +141,9 @@ Usage: nodii-dev <command> [options] [--json]
   lane step <key> --side SIDE --start|--done|--block <step> [--reason TEXT]
                                         # --block --reason on a blocked step records its new reason
   lane evidence <key> --pr|--commit|--figma|--deploy|--dev-check REF
-  lane heartbeat|review|land|verify|prioritize|deprioritize|stop <key>
+  lane heartbeat|land|verify|prioritize|deprioritize|stop <key>
+  lane review <key> --file REVIEW.json  # base/head, outcome and clause-cited findings
+  lane reviews <key>                    # stored review history for the lane
   lane non-issue <key> --reason TEXT --evidence TEXT --reroute KEY[,KEY]|none
                  --branch carried:KEY|dropped[:REASON] [--commits SHA[,SHA]]
                                         # DEC-0011: terminal non_issue; issue -> wont_do; slot frees
@@ -755,15 +759,29 @@ export async function main(argv = process.argv.slice(2)) {
   if (command === "hook") {
     if (action === "print-settings")
       return console.log(JSON.stringify(settingsSnippet(), null, 2));
-    if (action === "claude-figma-pre") {
+    if (action === "managed-dispatch") {
+      if (!rest[0] || rest.length > 1) throw new CliError("USAGE", "hook managed-dispatch needs one event name", 2);
+      const output = await dispatchManagedHook(rest[0], await stdinText());
+      if (output) process.stdout.write(output);
+      return;
+    }
+    if (["claude-figma-pre", "figma-pre"].includes(action)) {
       // Fail closed: Claude Code only blocks a tool call on exit code 2, and
       // treats any other non-zero exit as a non-blocking error that lets the
       // write through. Every failure here (bad stdin, missing config, Dev
       // error, lock denied) must therefore exit 2.
+      let payload;
       try {
-        const payload = JSON.parse(await stdinText());
-        return emit(await preHook(payload), json, "allowed");
+        payload = JSON.parse(await stdinText());
+        await recordHookFire(payload).catch(() => {});
+        const result = await preHook(payload);
+        if (hookRuntime(payload) !== "codex") return emit(result, json, "allowed");
+        return;
       } catch (error) {
+        if (payload && hookRuntime(payload) === "codex") {
+          console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: "PreToolUse", permissionDecision: "deny", permissionDecisionReason: `Blocked Figma write: ${error?.message ?? String(error)}` } }));
+          return;
+        }
         throw new CliError(
           error?.code ?? "FIGMA_HOOK_FAILED",
           `Blocked Figma write: ${error?.message ?? String(error)}`,
@@ -774,11 +792,21 @@ export async function main(argv = process.argv.slice(2)) {
     }
     if (action === "safety-pre") {
       // A malformed or unavailable safety check must not turn into permission.
+      let payload;
       try {
-        const result = await safetyPreHook(JSON.parse(await stdinText()));
-        for (const nudge of result.nudges ?? []) console.log(nudge);
+        payload = JSON.parse(await stdinText());
+        await recordHookFire(payload).catch(() => {});
+        const result = await safetyPreHook(payload);
+        const nudges = result.nudges ?? [];
+        if (nudges.length && hookRuntime(payload) === "codex")
+          console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: "PreToolUse", additionalContext: nudges.join("\n") } }));
+        else for (const nudge of nudges) console.log(nudge);
         return;
       } catch (error) {
+        if (payload && hookRuntime(payload) === "codex") {
+          console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: "PreToolUse", permissionDecision: "deny", permissionDecisionReason: error?.message ?? String(error) } }));
+          return;
+        }
         throw new CliError(
           error?.code ?? "SAFETY_HOOK_FAILED",
           error?.message ?? String(error),
@@ -788,12 +816,18 @@ export async function main(argv = process.argv.slice(2)) {
       }
     }
     if (action === "safety-post") {
+      let payload;
       try {
-        await safetyPostHook(JSON.parse(await stdinText()));
+        payload = JSON.parse(await stdinText());
+        await recordHookFire(payload).catch(() => {});
+        await safetyPostHook(payload);
       } catch (error) {
         // A post-hook cannot undo a completed command; report state-tracking
         // failure without making Claude treat the completed command as failed.
-        console.error(`nodii-dev safety post hook: ${error?.code ?? "ERROR"}: ${error?.message ?? String(error)}`);
+        const message = `nodii-dev safety post hook: ${error?.code ?? "ERROR"}: ${error?.message ?? String(error)}`;
+        if (payload && hookRuntime(payload) === "codex")
+          console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: "PostToolUse", additionalContext: message } }));
+        else console.error(message);
       }
       return;
     }
@@ -802,18 +836,30 @@ export async function main(argv = process.argv.slice(2)) {
       return emit(result, json, result.heartbeated ? `Heartbeat recorded for ${result.key}.` : "No current-branch lane; no heartbeat sent.");
     }
     const payload = JSON.parse(await stdinText());
+    await recordHookFire(payload).catch(() => {});
+    if (action === "session-start") {
+      const context = await sessionStartContext(payload);
+      if (context) console.log(context);
+      return;
+    }
     if (action === "workflow-post") {
       const suggestion = workflowSuggestion(payload);
-      if (suggestion) console.log(suggestion);
+      if (suggestion && hookRuntime(payload) === "codex")
+        console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: "PostToolUse", additionalContext: suggestion } }));
+      else if (suggestion) console.log(suggestion);
       return;
     }
-    if (action === "claude-figma-post") {
+    if (["claude-figma-post", "figma-post"].includes(action)) {
       try {
         return emit(await postHook(payload), json, "logged");
       } catch (error) {
         const outcome = postHookFailure(error);
-        console.error(outcome.message);
-        if (outcome.exitCode) process.exitCode = outcome.exitCode;
+        if (hookRuntime(payload) === "codex")
+          console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: "PostToolUse", additionalContext: outcome.message } }));
+        else {
+          console.error(outcome.message);
+          if (outcome.exitCode) process.exitCode = outcome.exitCode;
+        }
         return;
       }
     }

package/dist/core.js

@@ -4,7 +4,7 @@ import { chmod, mkdir, readFile, rm, writeFile } from "node:fs/promises";
 import { homedir, platform } from "node:os";
 import { dirname, join } from "node:path";
 
-export const VERSION = "0.6.24";
+export const VERSION = "0.6.26";
 export const configPath = () =>
   process.env.NODII_DEV_CONFIG_PATH ??
   join(homedir(), ".config/nodii-dev/config.json");
@@ -199,7 +199,7 @@ export async function checkLogin() {
 export const encode = (value) => encodeURIComponent(value);
 // Switches never take the next token as their value, so
 // `docs upload --wait rulebook/` keeps rulebook/ as a path.
-const SWITCHES = new Set(["json", "wait", "dry-run", "check", "all", "fleet", "help", "yes", "mine", "no-browser", "include-drafts", "drafted", "library", "async", "sync", "force"]);
+const SWITCHES = new Set(["json", "wait", "dry-run", "check", "all", "fleet", "help", "yes", "mine", "no-browser", "include-drafts", "drafted", "library", "async", "sync", "force", "system"]);
 export function parseArgs(argv) {
   const flags = {};
   const args = [];