@nodii/dev 0.6.8 → 0.6.10

package/README.md

@@ -146,6 +146,8 @@ nodii-dev figma apply CHANGE_SET --figma-version VERSION
 nodii-dev figma published CHANGE_SET --figma-version VERSION
 nodii-dev figma abandon CHANGE_SET
 nodii-dev figma withdraw CHANGE_SET    # take back a submit before anything is decided
+nodii-dev figma resubmit CHANGE_SET PAYLOAD.json   # round 2: re-submit every rejected item
+nodii-dev figma changeset show CHANGE_SET          # items, variants, round, decision, comment
 nodii-dev figma release FILE_KEY
 
 ```
@@ -168,7 +170,42 @@ an unregistered file prints the `figma file add` command to run.
 aren't its holder or an operator (`WITHDRAW_NOT_ALLOWED`), or an item is
 already decided (`CHANGE_SET_HAS_DECISIONS`: ask the reviewer to request
 changes instead). The CLI prints each refusal in plain words and keeps the
-code.
+code. Withdrawing an undecided re-submit returns the set to `applying`.
+
+`figma changeset show` lists a Figma change set's current items (the latest
+round of each): each one's decision, its comment (a rejection always has one), its
+round, the previous round's decision and comment when it was re-submitted,
+and its variants. It reads Dev's `getDesignChangeSet`; `--json` also gives the
+replaced rows (`previousRounds`) and the write log. Guideline change sets are
+`design changeset show`.
+
+`figma resubmit` is round 2 inside the same change set (Dev's
+`resubmitDesignChangeSet`). When every item is decided and some were
+rejected, the set is `applying`: rework the rejected items in Figma (the lock
+check allows writes in `applying`, and refuses them only while a submit is
+`in_review`), then re-submit them. The payload names every rejected item, by
+`itemId` or `figmaNodeId`, with its new variants, exported at 2x as for
+`figma submit`:
+
+```json
+{
+  "figmaVersion": "VERSION",
+  "items": [
+    { "figmaNodeId": "36:531", "variants": [{ "nodeId": "36:532", "afterPngBase64": "..." }] }
+  ]
+}
+```
+
+A variant without a PNG is rendered from Figma, and a variant keeps the
+"before" image from its earlier round. Each item goes back to review with its
+round + 1; approved items keep their decisions; the set goes `in_review`.
+`figma apply` runs once, when every item is approved. Dev refuses when you
+aren't the holder (`CHANGE_SET_HOLDER_REQUIRED`), the set isn't `applying`
+(`INVALID_CHANGE_SET_STATE`), nothing is rejected
+(`CHANGE_SET_HAS_NO_REJECTIONS`), a rejected item is missing (`REJECTED_ITEMS_MISSING`:
+the CLI lists each one with its comment), or the payload names an item that
+isn't rejected (`CHANGE_ITEM_NOT_REJECTED`); images go through the same
+style check as a submit (`CHANGE_SET_IMAGE_STYLE`).
 
 ```bash
 nodii-dev hook claude-figma-pre       # reads Claude Code hook JSON on stdin
@@ -191,7 +228,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]
@@ -287,8 +324,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
 
@@ -357,7 +446,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.
 
@@ -439,7 +529,9 @@ surfaces, service edges, lanes, swaps, ideas, terminology, and the AD era: `rule
 `archive` (`archive resolve --ref pre:D1366`), and `harness methodology`. `api list` is the authoritative discovery view;
 `api OPERATION_ID` makes every operation callable even without an alias.
 
-`figma check` exits `0` when allowed and `3` when denied. The pre-hook permits
+`figma check` exits `0` when allowed and `3` when denied. A held lock is
+denied only while its change set is `in_review` (`change-set-not-editable`),
+and `figma log-write` follows the same rule (`CHANGE_SET_NOT_EDITABLE`). The pre-hook permits
 non-Figma tools and allowlisted Figma reads, but defaults to denying every
 Figma write if the file key is absent, Dev cannot be reached, or the lock
 is denied. It exits `2`, which makes Claude Code block the call. The post-hook

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

@@ -26,8 +26,8 @@ import { heartbeatCurrentLane, postHook, preHook, settingsSnippet, workflowSugge
 import { setupCommand } from "./setup.js";
 import { harnessCommand } from "./harness.js";
 import { doctorCommand } from "./doctor.js";
-import { figmaFileKey, notRegisteredHint } from "./figma.js";
-import { docsCommand, rulebookCommand } from "./upload.js";
+import { figmaChangeSetShow, figmaChangeSetText, figmaFileKey, figmaResubmit, notRegisteredHint } from "./figma.js";
+import { docsCommand, rulebookCommand, rulesCommand } from "./upload.js";
 import { changeSetCommand, guidelineCommand } from "./guidelines.js";
 import {
   ALIASES,
@@ -70,7 +70,10 @@ Usage: nodii-dev <command> [options] [--json]
   design guideline propose ENTRY --file FILE.md [--summary TEXT] [--dry-run]
   design changeset list [--entry KEY] [--state STATE] | show ID
   figma lock|check|log-write|submit|apply|published|abandon|release
-  figma withdraw CHANGE_SET             # holder takes back a submit: in_review -> editing
+  figma withdraw CHANGE_SET             # holder takes back a submit: in_review -> editing (or a re-submit -> applying)
+  figma resubmit CHANGE_SET PAYLOAD.json
+                                        # holder re-submits every rejected item: applying -> in_review, round + 1
+  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|print-settings
@@ -84,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>
@@ -93,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
@@ -387,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));
@@ -630,7 +638,14 @@ export async function main(argv = process.argv.slice(2)) {
       );
     }
     if (action === "withdraw")
-      return emit(await figmaWithdraw(rest[0]), json, `Withdrew ${rest[0]}; it is back in editing.`);
+      return emit(await figmaWithdraw(rest[0]), json, (p) => `Withdrew ${rest[0]}; it is back in ${p.data?.state ?? "editing"}.`);
+    if (action === "resubmit")
+      return emit(await figmaResubmit(rest[0], rest[1]), json, (p) =>
+        [`Re-submitted ${rest[0]}; it is ${p.data.state}.`, figmaChangeSetText(p.data)].join("\n"));
+    if (action === "changeset") {
+      if (rest[0] !== "show" || !rest[1] || rest.length > 2) throw new CliError("USAGE", "figma changeset show CHANGE_SET", 2);
+      return emit(await figmaChangeSetShow(rest[1]), json, (p) => figmaChangeSetText(p.data));
+    }
     if (action === "release")
       return emit(
         await devRequest(

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