@nodii/dev 0.6.8 → 0.6.9

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
@@ -439,7 +476,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/cli.js

@@ -26,7 +26,7 @@ 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 { figmaChangeSetShow, figmaChangeSetText, figmaFileKey, figmaResubmit, notRegisteredHint } from "./figma.js";
 import { docsCommand, rulebookCommand } from "./upload.js";
 import { changeSetCommand, guidelineCommand } from "./guidelines.js";
 import {
@@ -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
@@ -630,7 +633,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.9";
 export const configPath = () =>
   process.env.NODII_DEV_CONFIG_PATH ??
   join(homedir(), ".config/nodii-dev/config.json");