@nodii/dev 0.6.9 → 0.6.11

package/README.md

@@ -29,7 +29,14 @@ every nodii-dev process on the machine shares it instead of refreshing on each
 run; refreshes take turns under a per-user lock. A refresh clears the saved
 sign-in only when nodii-auth answers `invalid_grant` (expired, revoked or
 replayed). A 429, 5xx, timeout, network error or proxy error page keeps it and
-fails with `OAUTH_REFRESH_UNAVAILABLE` (exit 1) after a few retries. Every API
+fails with `OAUTH_REFRESH_UNAVAILABLE` (exit 1). Only answers that show the
+token was not used are retried at once (a connection that never opened, 429,
+500, 503, a proxy's non-JSON 4xx). After a timeout, a dropped connection, a
+gateway timeout or a 2xx without tokens, nodii-auth may already have rotated
+the token; it is not sent again by that command, though the next one will
+present it, and a rotation whose answer was lost does end the sign-in.
+SIGINT, SIGTERM and SIGHUP wait while a token is in flight and until its
+successor is stored. Every API
 call goes to the edge's `/devops` prefix with the OAuth bearer and the
 registered `x-agent-id`; signing in again as the same person keeps that
 registration. `logout` revokes the refresh chain before erasing local
@@ -228,7 +235,7 @@ nodii-dev lane prioritize|deprioritize KEY --reason TEXT
 nodii-dev lane stop KEY --reason TEXT
 nodii-dev lane non-issue KEY --reason TEXT --evidence TEXT --reroute KEY[,KEY]|none
                          --branch carried:ISSUE|dropped[:REASON] [--commits SHA[,SHA]]
-nodii-dev next KEY
+nodii-dev next KEY [--paths A,B] [--components K,L] [--role ROLE]
 
 nodii-dev built list [--cursor CURSOR] [--include-acknowledged true]
 nodii-dev built ack KEY [KEY ...] [--note TEXT]
@@ -324,8 +331,60 @@ same checks, plus the ones that need its data, in one transaction.
 - `docs validate` also prints Dev's warnings for each document (they never
   block) and any problems with the decision's amends.
 
+- **Clauses are bullets** (Dev issue 80). A clause is defined only as
+  `- **ID** text`. The same id written as a bold paragraph (`**APPR-3.** …`),
+  a heading, a bold table row or a numbered item, and defined nowhere as a
+  bullet, is refused with `CLAUSE_NOT_A_BULLET` (line and id); text inside the
+  bold (`- **ID [INTENDED]** …`) is `CLAUSE_MALFORMED` (write
+  `- **ID** [INTENDED] …`). `CLAUSE_COUNT_MISMATCH` then states how many
+  clauses Dev would store against how many the source defines, naming the
+  missing ids. `docs check` runs these locally; `rulebook list` prints
+  `N clauses` for each document.
+
+### Rule delivery (DEC-0020)
+
+Every MUST clause declares how it reaches an agent, on one tag line indented
+under the clause:
+
+```
+- **MW2-14** The local gates MUST run in this order, …
+  ⟶ enforced · check: review-gates
+- **U03-9** A list MUST page with the shared pager …
+  ⟶ served · build: dev_fix · step: adopt_test · side: frontend · comp: data-table
+- **MW1-3** An agent MUST edit only its own config …
+  ⟶ core
+```
+
+The delivery is `enforced` (with `check:`, which the document's Enforcement
+table must name), `served` (with optional `build`, `step`, `side`, `svc`,
+`path`, `comp` and `role` tags) or `core`; `gap: ISSUE` marks one that does not
+work yet. `->` and `;` are ASCII aliases for `⟶` and `·`. A tag line as the
+first line under a `###` heading is the default for that sub-section. Dev
+checks every key and value, and refuses a ruling that adds or changes a MUST
+clause with no delivery, and a ratification while any MUST clause has none
+(`RULE_DELIVERY_MISSING`). The full syntax is in Dev's AD-era contract §1.8.
+
+```
+nodii-dev next KEY      # the next step, plus the clauses Dev serves for it
+nodii-dev rules core    # the generated core (every `core` clause); refused over the cap
+nodii-dev rules report [--section rulebook|services|all] [--lane KEY]
+nodii-dev rules cap TOKENS   # operator: the core's token cap (default 3000)
+```
+
+`next` sends the lane's changed files (its branch and working tree against
+`origin/main`, read from the lane's worktree) so Dev serves path-tagged
+clauses only where they apply; `--paths`, `--components` and `--role`
+override. Each served clause prints its id, its first sentence and where to
+read the rest; `--json` carries the full text and token counts. If Dev cannot
+serve rules, `next` still prints the step. `rules report` shows, for each
+document and in total, how many clauses use each delivery, how many MUST
+clauses are untagged and how many carry a tool gap, plus the clauses and
+tokens served to each lane at each step. Tokens are estimated as characters
+divided by four.
+
 Like every other command, these reach Dev only through the platform edge
-(`/devops/api/v1/documents`, `/domains`, `/harness`, …) with the OAuth login.
+(`/devops/api/v1/documents`, `/domains`, `/harness`, `/rules`, …) with the
+OAuth login.
 
 ## Agent harness
 
@@ -394,7 +453,8 @@ operation's permission (requested in Dev).
 name, as Dev compares it), branch and worktree from git unless overridden, and resolves `--issue` keys to the UUIDs
 required by Dev. Lane keys are passed directly to every lane and Built
 acknowledgement route. `next` reads the lane's generated
-API steps and prints the exact next `lane step` command. Server refusals,
+API steps and prints the exact next `lane step` command, then the rules Dev
+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.
 

package/bin/nodii-dev

@@ -7,6 +7,16 @@ while [ -L "$self" ]; do
   link=$(readlink "$self")
   case "$link" in /*) self="$link" ;; *) self="$(dirname "$self")/$link" ;; esac
 done
-entry="$(cd "$(dirname "$self")/.." && pwd)/dist/nodii-dev.js"
+root="$(cd "$(dirname "$self")/.." && pwd)"
+entry="$root/dist/nodii-dev.js"
+# A checkout's own build can be older than its package.json (Dev issue 88: a
+# stale 0.3.1 build once answered `npx @nodii/dev@0.6.10` inside a nodii-clis
+# worktree). Refuse to run one.
+built=$(sed -n 's/^export const VERSION = "\(.*\)";$/\1/p' "$root/dist/core.js" 2>/dev/null)
+wanted=$(sed -n 's/^  "version": "\(.*\)",$/\1/p' "$root/package.json" 2>/dev/null)
+if [ -n "$built" ] && [ -n "$wanted" ] && [ "$built" != "$wanted" ]; then
+  echo "nodii-dev: the build at $root is $built but its package.json says $wanted. Run 'npm run build' there, or run npx outside the nodii-clis repo." >&2
+  exit 2
+fi
 if command -v bun >/dev/null 2>&1; then exec bun "$entry" "$@"; fi
 exec node "$entry" "$@"

package/dist/api.js

@@ -103,6 +103,8 @@ export const GROUPS = {
   swaps: "Swaps", ideas: "Ideas", terminology: "Terminology", credentials: "Credentials",
   rulebook: "ad-documents", "ad-decisions": "ad-decisions", domains: "ad-domains", standardizations: "standardizations",
   archive: "archive", harness: "harness",
+  // DEC-0020 rule delivery; `rules core|report|cap` are first-class (upload.js).
+  rules: "rulebook",
 };
 
 export const ALIASES = {

package/dist/cli.js

@@ -27,7 +27,7 @@ import { setupCommand } from "./setup.js";
 import { harnessCommand } from "./harness.js";
 import { doctorCommand } from "./doctor.js";
 import { figmaChangeSetShow, figmaChangeSetText, figmaFileKey, figmaResubmit, notRegisteredHint } from "./figma.js";
-import { docsCommand, rulebookCommand } from "./upload.js";
+import { docsCommand, rulebookCommand, rulesCommand } from "./upload.js";
 import { changeSetCommand, guidelineCommand } from "./guidelines.js";
 import {
   ALIASES,
@@ -87,6 +87,9 @@ Usage: nodii-dev <command> [options] [--json]
   docs ratify --domain KEY [--domain KEY ...] --decision FILE [--wait]
   docs parked [CODE] [--status pending|acknowledged]
   rulebook list|show CODE [--version V]|diff CODE
+  rules core                            # the generated core (M05-33); refused over the cap
+  rules report [--section S] [--lane KEY]   # delivery totals per document; rules served per lane
+  rules cap TOKENS                      # operator: set the core token cap (default 3000)
 
   lane start <key> --title TEXT --kind KIND --side SIDE [--repo REPO] [--issue ISSUE]
   lane step <key> --side SIDE --start|--done|--block <step>
@@ -96,7 +99,8 @@ Usage: nodii-dev <command> [options] [--json]
                  --branch carried:KEY|dropped[:REASON] [--commits SHA[,SHA]]
                                         # DEC-0011: terminal non_issue; issue -> wont_do; slot frees
   lane list [--kind KIND] [--status STATUS] [--mine] [--cursor CURSOR]
-  lane show <key> | next <key>
+  lane show <key> | next <key> [--paths A,B] [--components K,L] [--role R]
+                                        # next step, plus the rules Dev serves for it (DEC-0020)
   built list | built ack <key...>
   machine list|show|set-coordinator|assign|report
   agent lane-limit|grant|revoke
@@ -390,6 +394,7 @@ export async function main(argv = process.argv.slice(2)) {
   }
   if (command === "docs") return emitCommand(await docsCommand(action, rest, f));
   if (command === "rulebook" && ["list", "show", "diff"].includes(action)) return emitCommand(await rulebookCommand(action, rest, f));
+  if (command === "rules") return emitCommand(await rulesCommand(action, rest, f));
   // Guideline change sets: approving or rejecting one is a person's action in Dev.
   if (command === "design" && action === "guideline") return emitCommand(await guidelineCommand(rest[0], rest.slice(1), f));
   if (command === "design" && action === "changeset") return emitCommand(await changeSetCommand(rest[0], rest.slice(1), f));

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.9";
+export const VERSION = "0.6.11";
 export const configPath = () =>
   process.env.NODII_DEV_CONFIG_PATH ??
   join(homedir(), ".config/nodii-dev/config.json");