rootr-cli 0.8.1 → 0.9.0

package/lib/mcp-tools/forms.js

@@ -126,13 +126,20 @@ export function registerFormTools(server) {
       annotations: { readOnlyHint: true, destructiveHint: false },
       inputSchema: {
         formId: z.string().describe(`FORM node id${NODE_TARGET_HINT}`),
+        latestPerRespondent: z
+          .boolean()
+          .optional()
+          .describe(
+            'Keep only the newest response per signed-in submitter (`submitterUserId`), dropping their earlier ' +
+              'drafts. Anonymous share-link submissions have no submitter and are never merged. Default false.',
+          ),
       },
     },
-    async ({ formId }) => {
+    async ({ formId, latestPerRespondent }) => {
       try {
         const client = makeClient();
         formId = await resolveNodeId(client, formId);
-        const result = await client.listFormResponses(formId);
+        const result = await client.listFormResponses(formId, { latestPerRespondent });
         return jsonResult({ responses: result });
       } catch (err) {
         return errorResult(err);
@@ -166,6 +173,84 @@ export function registerFormTools(server) {
     },
   );
 
+  server.registerTool(
+    'rootr_create_form_collector',
+    {
+      title: 'Create a table or spreadsheet that collects this form\'s responses',
+      description:
+        'Create a destination for a Rootr (루터) FORM\'s responses and link it in one call. ' +
+        '`target: "database"` builds a DATABASE whose columns come straight from the form\'s questions ' +
+        '(same names, matching types, select options carried over) — this is the right way to answer ' +
+        '"collect the answers in a table", because a hand-built table only mirrors when every column name ' +
+        'matches a question exactly. `target: "spreadsheet"` creates a SPREADSHEET whose sheet is bound to ' +
+        'the form, so its rows ARE the responses. Both replace any previous destination — a form collects ' +
+        'into one place. To link an already-built table instead, use rootr_update_form with targetDatabaseId.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        formId: z.string().describe(`FORM node id${NODE_TARGET_HINT}`),
+        target: z
+          .enum(['database', 'spreadsheet'])
+          .describe('database = typed columns/views (filters, boards); spreadsheet = one sheet of rows for formulas'),
+      },
+    },
+    async ({ formId, target }) => {
+      try {
+        const client = makeClient();
+        formId = await resolveNodeId(client, formId);
+        return jsonResult(await client.createFormCollector(formId, target));
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_update_form_response',
+    {
+      title: 'Fix an already-submitted Rootr form response',
+      description:
+        'Correct one response that was already submitted to a Rootr (루터) FORM. `values` REPLACES the whole ' +
+        'answer set and is re-checked against the form\'s current fields (required/type rules), so send every ' +
+        'answer you want to keep — call rootr_list_form_responses first. Use this instead of deleting and ' +
+        're-submitting when you want the original submitter and submission time preserved.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        responseId: z.string().describe('Response id from rootr_list_form_responses'),
+        values: z.record(z.any()).describe('Full replacement answers, keyed by field id'),
+      },
+    },
+    async ({ responseId, values }) => {
+      try {
+        const result = await makeClient().updateFormResponse(responseId, values);
+        return jsonResult(result);
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_delete_form_response',
+    {
+      title: 'Delete one Rootr form response',
+      description:
+        'Permanently delete a single response submitted to a Rootr (루터) FORM. This cannot be undone — the ' +
+        'answers are gone. Use rootr_update_form_response to correct a response instead of deleting it.',
+      annotations: { readOnlyHint: false, destructiveHint: true },
+      inputSchema: {
+        responseId: z.string().describe('Response id from rootr_list_form_responses'),
+      },
+    },
+    async ({ responseId }) => {
+      try {
+        await makeClient().deleteFormResponse(responseId);
+        return jsonResult({ deleted: true, responseId });
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
   server.registerTool(
     'rootr_create_form_share_link',
     {

package/lib/mcp-tools/misc.js

@@ -31,6 +31,46 @@ export function registerMiscTools(server) {
     },
   );
 
+  server.registerTool(
+    'rootr_update_node',
+    {
+      title: 'Rename / re-icon / move any node',
+      description:
+        'Change a Rootr (루터) node\'s NAME, ICON, TAGS, or PARENT — works for every node type ' +
+        '(DOCUMENT, FOLDER, DATABASE, SPREADSHEET, FORM, …). Until now icons could only be set when a node ' +
+        'was CREATED, so matching a migrated tree to its Notion icons was impossible without recreating ' +
+        'everything. Only the fields you pass change. `parentId: null` moves the node to the workspace root; ' +
+        'a node cannot be moved inside its own subtree.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        target: z.string().describe('Node path (starting with "/") or node id'),
+        name: z.string().optional().describe('New name'),
+        icon: z.string().optional().describe('New emoji icon, e.g. "📋". Empty string clears it.'),
+        tags: z.array(z.string()).optional().describe('Replaces the tag list'),
+        parentId: z
+          .string()
+          .nullable()
+          .optional()
+          .describe('Move under this folder/document/database (id or path). null = workspace root.'),
+      },
+    },
+    async ({ target, name, icon, tags, parentId }) => {
+      try {
+        const client = makeClient();
+        const id = requireResolved(await resolveTarget(client, target));
+        // 부모도 경로로 줄 수 있어야 한다 — id를 미리 아는 쪽이 오히려 드물다.
+        let parent = parentId;
+        if (typeof parentId === 'string' && parentId) {
+          parent = requireResolved(await resolveTarget(client, parentId));
+        }
+        const node = await client.updateNode(id, { name, icon, tags, parentId: parent });
+        return jsonResult(node);
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
   server.registerTool(
     'rootr_delete_node',
     {

package/lib/mcp-tools/workspaces.js

@@ -14,7 +14,14 @@ import { parseRootrUrl } from '../resolve.js';
  * branch plus parseTree() keeps any client that still stringifies working.
  * Mirrors the typed-array pattern already used in logs.js.
  */
-const treeArg = (desc) => z.array(z.record(z.any())).or(z.string()).describe(desc);
+const ACCESS_HINT =
+  ' Any node may also carry `visibility: "PRIVATE"` (only its creator, workspace admins, and people listed in ' +
+  '`access` can see it and everything under it) plus `access: [{ subjectId: "<userId>", level: "READ"|"WRITE"|' +
+  '"MANAGE" }]` — that pair is how "make a folder these three people can see" happens in one call instead of ' +
+  'leaving the locking to the user afterwards. A DATABASE node may also carry `database.permissions` (칸/행 ' +
+  'lock) and `database.notifications` (who to notify on row changes).';
+
+const treeArg = (desc) => z.array(z.record(z.any())).or(z.string()).describe(desc + ACCESS_HINT);
 
 /** Accept either a real array (typed clients) or a JSON string (clients that stringify structured args). */
 function parseTree(tree) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rootr-cli",
-  "version": "0.8.1",
+  "version": "0.9.0",
   "description": "Official Rootr CLI + MCP server — read, write, edit and search Rootr documents from the shell or from an AI agent.",
   "type": "module",
   "bin": {