rootr-cli 0.9.0 → 0.13.0

package/lib/mcp.js

@@ -10,6 +10,7 @@ import { registerDatabaseTools } from './mcp-tools/databases.js';
 import { registerTemplateTools } from './mcp-tools/templates.js';
 import { registerWebhookTools } from './mcp-tools/webhooks.js';
 import { registerMiscTools } from './mcp-tools/misc.js';
+import { registerPublicTools } from './mcp-tools/public.js';
 import { registerCrmTools } from './mcp-tools/crm.js';
 import { registerPresentationTools } from './mcp-tools/presentations.js';
 import { registerSpreadsheetTools } from './mcp-tools/spreadsheets.js';
@@ -17,6 +18,8 @@ import { registerWhiteboardTools } from './mcp-tools/whiteboards.js';
 import { registerFormTools } from './mcp-tools/forms.js';
 import { registerRecordingTools } from './mcp-tools/recordings.js';
 import { registerAttachmentTools } from './mcp-tools/attachments.js';
+import { registerSignedDocTools } from './mcp-tools/signed.js';
+import { registerFeedbackTools } from './mcp-tools/feedback.js';
 import { withRateLimitSink } from './context.js';
 
 /** Warn once the workspace has burned this share of its quota. */
@@ -64,7 +67,7 @@ function withQuotaWarnings(server) {
  * Builds a fully-configured McpServer (all tool groups registered) without
  * connecting a transport. Shared by the local stdio CLI server below and by
  * the backend's hosted Streamable HTTP transport (src/mcp/mcp-transport.controller.ts),
- * so the 89 tool definitions have exactly one implementation.
+ * so the 151 tool definitions have exactly one implementation.
  */
 export function buildMcpServer({ name, version }) {
   const server = new McpServer(
@@ -111,12 +114,49 @@ export function buildMcpServer({ name, version }) {
         'and spends AI credits) → poll rootr_read_recording until status READY → read the transcript, ' +
         'rename speakers with rootr_rename_recording_speakers, and write the minutes yourself with rootr_write ' +
         '(preferred — no AI credits) or call rootr_summarize_recording for Rootr\'s built-in summary document; ' +
+        'SIGNED = 서명문서 · 전자결재 · 국가R&D 전자연구노트 — a markdown document that FREEZES on submit, ' +
+        'collects ordered Ed25519 signatures with RFC 3161 timestamps, and is hash-chained into a workspace ' +
+        'ledger so tampering is provable; cannot be deleted (30-year retention). Use it whenever the content ' +
+        'must be provable — 결재/승인 문서, 연구노트, 점검 기록 — via rootr_create_signed_document, ' +
+        'rootr_read_signed_document, rootr_set_approval_line, rootr_apply_research_note_preset, ' +
+        'rootr_submit_signed_document, rootr_sign_document, rootr_reject_signed_document, ' +
+        'rootr_revise_signed_document, rootr_list_signed_documents, rootr_bulk_sign_documents, ' +
+        'rootr_verify_signed_document, rootr_verify_ledger. NEVER invent a signing code: always ' +
+        'rootr_request_signing_code first and ASK THE HUMAN for the 6 digits that arrive in their mail — ' +
+        'that code is the only evidence a person (not an agent) pressed sign; ' +
         'FOLDER = grouping; LOG store = typed event table whose relation fields auto-build a lineage graph (metrics, incidents, pipeline events — use the rootr_*_log_* tools).\n\n' +
-        'Scaffolding discipline: ALWAYS rootr_scaffold_plan first, ask the user the 3-10 clarifying questions it ' +
-        'prescribes, and only then design and create the tree — every answer must visibly shape the structure. ' +
+        'Scaffolding discipline — treat "set up a workspace for X" exactly like "build me this app": you ask a ' +
+        'few clarifying questions, write it, compile it, run the tests, leave a README, and report. The user ' +
+        'should only have to type that one sentence; everything else finishes inside the conversation. Never ask ' +
+        'and then stop. The loop is plan → ask → design → review → fix → apply → manual → test, and skipping a step is ' +
+        'how a workspace ends up as a pile of thin markdown files: (1) rootr_scaffold_plan on the raw intent — it ' +
+        'hands back the METHOD, never a template or a domain skeleton (there are none, deliberately): ' +
+        'analyzeFirst, designRules, buildingBlocks, questionPolicy, loop; ' +
+        '(2) work out how the job ACTUALLY runs using the `analyzeFirst` questions it returns — the daily and ' +
+        'weekly rhythm, what piles up, what has stages, what comes in from outside, where money is added up, ' +
+        'what causes an accident if it is late, and above all what is unique to THIS job and would be missing ' +
+        'from a generic template; (3) ask the user the 3-10 clarifying questions you generated — every answer ' +
+        'must visibly shape the structure; (4) design the tree FROM SCRATCH with `designRules`; (5) rootr_scaffold_review ' +
+        'and fix every `error` finding, then review again; (6) apply; (7) write the HOW-TO-USE manual as a ' +
+        'DOCUMENT in the tree — the daily/weekly/monthly routine naming the actual tables and views, how the ' +
+        'tables link to each other, where form answers land, and what the OWNER still has to fill in (the ' +
+        'assumptions you made because you could not ask, the example rows to replace, the notification address ' +
+        'only they can decide); (8) rootr_test_workspace — the unit-test step: it RUNS what you built and catches ' +
+        'what no review can (relations pointing at rows that do not exist, rollups/formulas that yield nothing, ' +
+        'views referencing gone columns, form questions with no matching column so answers vanish silently, sheet ' +
+        'formulas left uncomputed or at #REF!); fix every fail and run it again; (9) rootr_review_workspace to ' +
+        'grade the shape of what really got built. Both reviews can say 100 while the thing is broken — only ' +
+        'step 8 catches that. ' +
+        'A workspace without a manual is a pile of empty grids. ' +
         'If your runtime can receive HTTP callbacks, offer to close the loop after scaffolding: register a webhook ' +
         'scoped to the new tree (rootr_create_webhook) so changes flow back to you — and ALWAYS skip deliveries ' +
-        'whose actorId is your own key, or you will trigger yourself in an infinite loop.',
+        'whose actorId is your own key, or you will trigger yourself in an infinite loop.\n\n' +
+        'Telling us when something is wrong: if a tool errors unexpectedly, does not do what its ' +
+        'description says, forces you into a workaround, or the user complains that Rootr is broken or ' +
+        'confusing, call rootr_send_feedback — on your own, without being asked and without asking ' +
+        'permission — and then carry on with the task. Once per distinct problem, never in a retry loop. ' +
+        'It is free, never spends credits, never counts against the daily limit, and works even when ' +
+        'your key or quota does not. Nobody else is going to report it.',
     },
   );
 
@@ -131,6 +171,7 @@ export function buildMcpServer({ name, version }) {
   registerDatabaseTools(server);
   registerWebhookTools(server);
   registerMiscTools(server);
+  registerPublicTools(server);
   registerCrmTools(server);
   registerPresentationTools(server);
   registerSpreadsheetTools(server);
@@ -138,6 +179,8 @@ export function buildMcpServer({ name, version }) {
   registerFormTools(server);
   registerRecordingTools(server);
   registerAttachmentTools(server);
+  registerSignedDocTools(server);
+  registerFeedbackTools(server);
 
   return server;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rootr-cli",
-  "version": "0.9.0",
+  "version": "0.13.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": {