rootr-cli 0.19.0 → 0.22.0

package/lib/mcp-tools/databases.js

@@ -412,6 +412,30 @@ export function registerDatabaseTools(server) {
               'Default month. The year view shows twelve mini-months at once (darker = more rows that day). ' +
               'Saved on the view, so everyone who opens it sees that span.',
           ),
+        cardProps: z
+          .array(z.string())
+          .nullable()
+          .optional()
+          .describe(
+            'board view only: the fields shown on each card, in this order (names or ids, up to 12). Rollups and formulas ' +
+              'work here (e.g. an interview date rolled up from a linked table) — only the picked ones are computed. ' +
+              'null or [] goes back to the default (the first 3 stored fields that have a value).',
+          ),
+        rowColors: z
+          .array(
+            z.object({
+              propId: z.string(),
+              op: z.enum(['is', 'is_not_empty']),
+              values: z.array(z.string()).optional(),
+              color: z.string(),
+            }),
+          )
+          .nullable()
+          .optional()
+          .describe(
+            'Tint rows/cards by value: the first matching rule wins. e.g. [{propId:"진행상태",op:"is",values:["채용불가"],color:"red"}, ' +
+              '{propId:"면접예정일",op:"is_not_empty",color:"yellow"}]. Colors: gray, brown, orange, yellow, green, blue, purple, pink, red. null or [] turns it off.',
+          ),
       },
     },
     async ({
@@ -426,6 +450,8 @@ export function registerDatabaseTools(server) {
       sort,
       colWidths,
       calendarScale,
+      cardProps,
+      rowColors,
     }) => {
       try {
         const client = makeClient();
@@ -440,6 +466,8 @@ export function registerDatabaseTools(server) {
           sort,
           colWidths,
           calendarScale,
+          cardProps,
+          rowColors,
         });
         return jsonResult({ view });
       } catch (err) {
@@ -1055,9 +1083,57 @@ export function registerDatabaseTools(server) {
               'chat, button AI-fill steps, formula/rollup columns and MCP reads still see the values; to hide values from ' +
               'people, use an "own rows only" table or a private node. Table managers only. false puts the column back into the index.',
           ),
+        optionRenames: z
+          .array(z.object({ from: z.string(), to: z.string() }))
+          .optional()
+          .describe(
+            'select/multi_select/status with `options`: rename choices and move every row that used the old name ' +
+              '(e.g. [{from:"신규접수",to:"접수 완료"}]). A choice left out of `options` and not renamed is DELETED and the rows using it are emptied.',
+          ),
+        dedupe: z
+          .boolean()
+          .optional()
+          .describe(
+            'title/text/phone/email/url only: warn when another row has the same value (phone numbers compare digits only, ' +
+              'other text ignores case and spaces). People get a choose-merge-or-keep dialog; forms filled inside Rootr warn before submit; ' +
+              'public forms leave a "possible duplicate" comment. See rootr_find_duplicates.',
+          ),
+        dedupeShow: z
+          .array(z.string())
+          .nullable()
+          .optional()
+          .describe(
+            'With dedupe on: which fields of the EXISTING row the duplicate dialog shows, in order (column ids). A relation column ' +
+              'shows the latest 5 linked rows (contact history) and the total. Names or ids; an unknown name is refused (400), not dropped. ' +
+              'null/[] = automatic (status, notes, dates, rollups; relations as history).',
+          ),
+        relationFilter: z
+          .array(z.object({ propId: z.string(), op: z.enum(['is', 'is_not_empty']), values: z.array(z.string()).optional() }))
+          .nullable()
+          .optional()
+          .describe(
+            'relation only: which rows of the linked table may be linked (all rules must match; propId is a column of the LINKED table). ' +
+              'e.g. [{propId:"진행상태",op:"is",values:["채용"]}]. The picker hides others and the server refuses new links that fail. null turns it off.',
+          ),
       },
     },
-    async ({ databaseId, propertyId, name, options, formula, rollup, prefix, reverseName, searchExcluded, type, dimensions }) => {
+    async ({
+      databaseId,
+      propertyId,
+      name,
+      options,
+      formula,
+      rollup,
+      prefix,
+      reverseName,
+      searchExcluded,
+      optionRenames,
+      dedupe,
+      dedupeShow,
+      relationFilter,
+      type,
+      dimensions,
+    }) => {
       // 조용히 무시하지 않는다 — 못 바꾸는 것을 넘기면 까닭과 할 일을 말한다(벡터 차원을 바꾸면 저장된 벡터가 전부 틀려진다).
       if (type !== undefined || dimensions !== undefined) {
         return errorResult(
@@ -1078,6 +1154,10 @@ export function registerDatabaseTools(server) {
           prefix,
           reverseName,
           searchExcluded,
+          optionRenames,
+          dedupe,
+          dedupeShow,
+          relationFilter,
         });
         return jsonResult({ property });
       } catch (err) {
@@ -1086,6 +1166,190 @@ export function registerDatabaseTools(server) {
     },
   );
 
+  // ── DEDUPE(F5) — 같은 사람 찾기·합치기·새 행으로 두기 ─────────────────────
+  //
+  // 화면의 중복 창과 같은 일을 에이전트도 할 수 있어야 한다. 그렇지 않으면 "지원자 붙여 넣으면서 이미 있는 사람은 합쳐 줘"
+  // 같은 부탁에서 에이전트가 표 전체를 읽어 전화번호를 손으로 견주게 된다(9천 행이면 수 MB).
+
+  server.registerTool(
+    'rootr_find_duplicates',
+    {
+      title: 'Find existing rows that duplicate a row (same phone/email/name)',
+      description:
+        'Find rows of a Rootr (루터) DATABASE whose duplicate-detection columns (rootr_update_column dedupe:true — e.g. a phone ' +
+        'column) hold the same value. Phone numbers compare digits only (010-1234-5678 = 01012345678); other text ignores case ' +
+        'and spaces. Give `rowId` to check an existing row (it is excluded from the result) or `values` ({column name or id: value}) ' +
+        'to check before adding. Each match comes with the fields the duplicate dialog shows (`preview`: status, notes, dates, rollups ' +
+        '— or the column\'s dedupeShow list) and `history`: the latest 5 linked rows per relation column (e.g. call log) with the total. ' +
+        'Only rows the caller can see are returned. Then use rootr_merge_rows or rootr_keep_duplicate.',
+      annotations: { readOnlyHint: true, destructiveHint: false },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        rowId: z.string().optional().describe('Check this existing row (its current values).'),
+        values: z.record(z.any()).optional().describe('Or check these values before adding a row: { "연락처": "010-1234-5678" }'),
+      },
+    },
+    async ({ databaseId, rowId, values }) => {
+      try {
+        if (!rowId && !values) return errorResult(new Error('rowId 나 values 중 하나를 주세요.'));
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        return jsonResult(await client.findDuplicates(id, { rowId, values }));
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_merge_rows',
+    {
+      title: 'Merge a duplicate row into an existing row',
+      description:
+        'Merge row `rowId` into row `into` of the same Rootr (루터) DATABASE — the "same person applied again" case. Empty cells of ' +
+        '`into` are filled from `rowId` (existing values are kept), relation/multi-select/people/files are unioned (so a call log linked ' +
+        'to the new row moves to the old one), a "🔁 재지원" comment listing the new values is left on `into`, and `rowId` is DELETED ' +
+        '(row history records it as merged into `into`). Both rows must be editable by the caller. Not reversible except by the table history.',
+      annotations: { readOnlyHint: false, destructiveHint: true },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        rowId: z.string().describe('The newer/duplicate row — it is deleted after merging'),
+        into: z.string().describe('The existing row to keep'),
+      },
+    },
+    async ({ databaseId, rowId, into }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        return jsonResult(await client.mergeRows(id, rowId, into));
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_keep_duplicate',
+    {
+      title: 'Keep a duplicate as a new row but link it to the earlier row',
+      description:
+        'The "keep as new row" choice: leaves row `rowId` as it is and writes a 🔗 comment on BOTH rows pointing at each other, so the ' +
+        'earlier history follows the new row. Use when the same person really should have a separate row (e.g. a new application period).',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        rowId: z.string().describe('The new row to keep'),
+        from: z.string().describe('The earlier row of the same person'),
+      },
+    },
+    async ({ databaseId, rowId, from }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        return jsonResult(await client.keepDuplicate(id, rowId, from));
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  // ── ROW-HISTORY / RESTORE(F6·F7·G3) — 행·표 이력과 되돌리기 ─────────────────
+
+  server.registerTool(
+    'rootr_database_history',
+    {
+      title: 'Read the change history of a database (or one row)',
+      description:
+        'Newest-first change history of a Rootr (루터) DATABASE — every create/update/delete with who, when, how (via: button, ' +
+        'automation, form, restore, option-edit, merge:<rowId>, link…) and the before/after values of the changed columns. Give `rowId` ' +
+        'for one row. Page with `before` + `beforeId` (the `at` and `id` of the last item you got). Use the change `id`s with ' +
+        'rootr_restore_row, or an `at` with rootr_restore_database.',
+      annotations: { readOnlyHint: true, destructiveHint: false },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        rowId: z.string().optional(),
+        before: z.string().optional().describe('ISO time — only changes before it (the `at` of the last item of the previous page)'),
+        beforeId: z.string().optional().describe('The `id` of the last item of the previous page (needed when many changes share a time)'),
+        limit: z.number().int().min(1).max(500).optional(),
+      },
+    },
+    async ({ databaseId, rowId, before, beforeId, limit }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        return jsonResult(await client.databaseHistory(id, { rowId, before, beforeId, limit }));
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_restore_row',
+    {
+      title: 'Restore one row to how it was at a change',
+      description:
+        'Put ONE row of a Rootr (루터) DATABASE back to its state right after (`side: "after"`, default) or right before (`"before"`) ' +
+        'the change `changeId` from rootr_database_history. A deleted row comes back with the same id (links on the other side are ' +
+        'restored too). The restore itself is recorded in the history, so it can be undone the same way.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        rowId: z.string(),
+        changeId: z.string().describe('The history item id'),
+        side: z.enum(['after', 'before']).optional(),
+      },
+    },
+    async ({ databaseId, rowId, changeId, side }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        return jsonResult(await client.restoreRow(id, rowId, changeId, side ?? 'after'));
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_restore_database',
+    {
+      title: 'Restore a whole database to a point in time',
+      description:
+        'Put a whole Rootr (루터) DATABASE back to how it was at `at` (ISO time): rows created after it are deleted, rows deleted after ' +
+        'it come back, edited values go back — and the table definition too (columns incl. deleted ones and their values, select ' +
+        'choices, views, buttons, automations) when it was recorded at that time. ALWAYS call with `dryRun: true` first and show ' +
+        'the person the counts (`updates/creates/deletes`, `schema`). Table managers only. Big restores (over 300 rows) run in the ' +
+        'background: the reply has `job`, and this tool waits up to ~2 minutes for it, then returns the progress — call ' +
+        'rootr_restore_database again with `jobId` to keep checking. Automations do not fire while restoring.',
+      annotations: { readOnlyHint: false, destructiveHint: true },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        at: z.string().optional().describe('ISO time to go back to'),
+        dryRun: z.boolean().optional().describe('true = only count what would change'),
+        jobId: z.string().optional().describe('Check a running background restore instead of starting one'),
+      },
+    },
+    async ({ databaseId, at, dryRun, jobId }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        if (jobId) return jsonResult({ job: await client.restoreJob(id, jobId) });
+        if (!at) return errorResult(new Error('at(ISO 시각)을 주세요.'));
+        const res = await client.restoreDatabase(id, at, { dryRun });
+        if (!res.job) return jsonResult(res);
+        let job = { ...res.job, done: 0, state: 'running' };
+        for (let i = 0; i < 60 && job.state !== 'done'; i++) {
+          await new Promise((r) => setTimeout(r, 2000));
+          job = await client.restoreJob(id, res.job.id);
+        }
+        return jsonResult({ ...res, job });
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
   // ── DB-PERM-001 / DB-WATCH — 노션에 없는 두 가지: 자물쇠와 알림 ────────────
   //
   // 표를 만들 수 있으면 잠글 수도, 누구에게 알릴지 정할 수도 있어야 한다. 이게 없으면
@@ -1286,12 +1550,27 @@ export function registerDatabaseTools(server) {
         'row the person pressed on, where `relation` is the relation column IN THE TARGET table that points back ' +
         'here. That pair is how "press 전화 on an applicant → a call row already linked to them" becomes one ' +
         'press instead of switching tables and searching the person again.\n' +
+        '  add_row also takes `match: { key: "{요청 건}", on: "업체명", normalize?: ["spaces","parens","suffix:의원",' +
+        '"trailingDigits","case"], fill?: "empty" }` — FIND-OR-LINK instead of always creating: `key` (filled from the ' +
+        'pressed row) is compared with the target column `on` — first exactly (spaces ignored, so "다라치과(홍대점)" ' +
+        'picks that branch), then after `normalize` (parens drops "(긴급)"·"(소독)", suffix:X drops a trailing X, ' +
+        'trailingDigits drops a trailing number). ONE match → no new row, the pressed row is ADDED to that row\'s `link` ' +
+        'relation (fill:"empty" also fills its blank cells from `values`); NONE → created as usual; TWO OR MORE → ' +
+        'nothing is created and the pressed row gets a "후보 여러 곳: A, B" comment so a person picks. The result ' +
+        'says `matched: { linked, created, ambiguous }`.\n' +
         '· {kind:"update_rows", target:"created"|"selected", values} — set values on the rows this button just ' +
         'made, or on the rows the person ticked in the table.\n' +
         '· {kind:"ai_fill", target, propId, prompt} — let AI write ONE cell. The prompt may quote the row with ' +
         '{칸이름}, e.g. "{제목}과 {메모}를 한 문장으로 요약해". If the AI fails the button keeps going.\n' +
         '· {kind:"open_row"} — open the row this button made (UI only; over the API it just reports the id).\n' +
-        'Values accept @today, @today+7 and @me — the server fills them in at press time, not now.\n' +
+        'Values accept @today, @today+7 and @me — the server fills them in at press time, not now. A text value ' +
+        'may also quote the pressed row with {칸이름}, e.g. "{이름} {통화 건수+1}차": computed columns (rollup, ' +
+        'formula) are read too, {칸이름+N} / {칸이름-N} adds to a numeric value, and when several rows are ' +
+        'selected each new row is filled from its own source row. A relation column resolves to the linked row: ' +
+        '{지원자} is its TITLE (not the id) and {지원자.통화 건수} reads one of its columns — EXCEPT when the value ' +
+        'is exactly "{관계 칸}" and the column it goes into is a relation to the SAME table: then the row ids are ' +
+        'copied (e.g. 담당 매니저: "{배정 매니저}"). Ids the receiving column\'s relationFilter rejects are left out ' +
+        'of that cell only (the rest still runs), commented on the row and reported in `notes`.\n' +
         'A button never grants permission: it runs as whoever presses it — writing into another table needs ' +
         'write access there too.',
       annotations: { readOnlyHint: false, destructiveHint: true },
@@ -1333,7 +1612,9 @@ export function registerDatabaseTools(server) {
         'Returns `created` (the ARRAY of row ids it made, not a count), `updated` and `filled` counts, the ' +
         '`openRowId` a final "open_row" step points at (with `openDatabaseId` when that row is in another ' +
         'table), `createdIn` telling which table each new row landed in, and — if the AI could not write a cell — `aiFailed` ' +
-        'with the reason (the rest of the button still ran). ' +
+        'with the reason (the rest of the button still ran). `aiSkipped` counts rows where the AI answered but the ' +
+        'answer could not go in the cell (e.g. not one of a select\'s options), with one sample in `aiSkippedAnswer`; ' +
+        '`aiUnchanged` counts rows whose AI answer equals the current value (left as is, not counted in `filled`). ' +
         'It runs with YOUR permissions: a button that writes a locked column stops there if you cannot edit it.',
       annotations: { readOnlyHint: false, destructiveHint: false },
       inputSchema: {
@@ -1400,7 +1681,11 @@ export function registerDatabaseTools(server) {
         '부재 3회 초과 → set the applicant to 보류; every morning at 09:00 → flag rows whose 재통화 예정일 is today.\n' +
         'Rules run as the person who SAVED them, never with more permission than that. A rule that a computed ' +
         'column (rollup/formula) triggers must use a value comparison, not changed/changed_to — the server ' +
-        'refuses those instead of quietly never firing.',
+        'refuses those instead of quietly never firing.\n' +
+        'add_row `match` (find-or-link, see rootr_set_database_buttons) is how "투입확정 → 사업장 마스터에 등록" ' +
+        'stops making duplicates for existing customers: one matching 사업장 → linked, none → created, several → a ' +
+        '"후보 여러 곳" comment on the request row. Those notes, and relation ids skipped by a relationFilter, are ' +
+        'written to the rule\'s lastError (with the row) — read them with rootr_list_database_automations.',
       annotations: { readOnlyHint: false, destructiveHint: true },
       inputSchema: {
         databaseId: z.string().describe(DATABASE_TARGET_DESC),

package/lib/mcp-tools/forms.js

@@ -31,6 +31,10 @@ const fieldShape = z
       .boolean()
       .optional()
       .describe('Not shown; filled from the URL (?이름=값). Use to record where a signup came from.'),
+    range: z
+      .boolean()
+      .optional()
+      .describe('date only: false = a single date (no end-date input). Omitted/true = start + optional end.'),
     showIf: z
       .object({ fieldId: z.string(), equals: z.string() })
       .optional()
@@ -45,7 +49,8 @@ const FIELDS_GUIDE =
   'Also: time (HH:MM) and file (uploaded on the published page only). ' +
   'select/multi_select/matrix/ranking need `options` ({name,color}[]); matrix also needs `rows`. ' +
   'Per-field extras: `help` (a hint line), `placeholder`, `page` (split into multiple pages), `hidden` + URL ' +
-  'params (record the traffic source), `showIf` (show only when an earlier answer matches). ' +
+  'params (record the traffic source), `showIf` (show only when an earlier answer matches), `range: false` on a ' +
+  'date field (ask for ONE date — by default a date field also shows an optional end date). ' +
   'Read the form first (rootr_read_form) before updating so ' +
   'you keep each field\'s `id` stable — response values are keyed by field id, so renaming/dropping an id orphans ' +
   'past responses\' answers for that field.';

package/lib/mcp-tools/pages.js

@@ -26,7 +26,9 @@ import {
 const BLOCK_GUIDE =
   'A page is `blocks[]` (ordered, max 200) + `config`. Each block is {id?, type, props}. ' +
   'You assemble a page from these block types:\n' +
-  '· hero {title, subtitle?, align?:"left"|"center", background?:{kind:"color",color}|{kind:"image",attachmentId}, button?:{label,target}} — the opening banner\n' +
+  '· hero {title, subtitle?, align?:"left"|"center", size?:"normal"|"screen", background?:{kind:"color",color}|{kind:"image",attachmentId}, button?:{label,target}} — the opening banner. ' +
+  'size:"screen" makes it a FULL-SCREEN landing hero: edge to edge and one viewport tall (minus the top name bar, capped at 1200px), big headline, content centred vertically ' +
+  '(default "normal" = a compact banner inside the text column)\n' +
   '· text {body (markdown), title?} — prose section; markdown is sanitized when rendered\n' +
   '· features {columns?:1|2|3, items:[{title, body, icon?(emoji)}]} — "what it does" grid\n' +
   '· gallery {images:[{attachmentId, caption?}]} — images must be workspace attachments (no external image URLs)\n' +
@@ -40,12 +42,35 @@ const BLOCK_GUIDE =
   '· liveTable {source:{nodeId}, columns?:[name], rowLimit?(1-200), orderBy?:{column, dir:"asc"|"desc"}}\n' +
   '· liveChart {source:{nodeId, sheet?, range?}, chart, labelColumn, valueColumn?, agg?, …} — a LIVE chart (46 kinds, see CHARTS below)\n' +
   '· form {formNodeId(FORM node), headline?, submitLabel?} — visitors submit right on the page\n' +
-  '· custom {html, height?(40-4000, default 260)} — free HTML/CSS, rendered inside a locked-down sandboxed iframe ' +
+  '· booking {bookingNodeId(DATABASE node id — a table that is published with visitor booking turned on, see rootr_set_booking), headline?, type?} — ' +
+  'a visitor scheduling calendar right on the page; `type` shows only one of the table\'s booking types. ' +
+  'bookingNodeId must be the node ID (names/paths are not resolved here); a table that is not published or has booking off renders as "not taking bookings"\n' +
+  '· custom {html, height?(40-4000, default 260), minHeight?:"none"|"screen", bleed?:boolean} — free HTML/CSS, rendered inside a locked-down sandboxed iframe ' +
   '(no scripts, no same-origin, no network). Use it for a look the other blocks cannot make. Page theme colors are ' +
   'available inside as var(--pg-bg|text|muted|faint|card|line|accent|on-accent) and var(--pg-font). Scripts and ' +
-  'on*= handlers are stripped on save — do not put behaviour here, only markup and CSS.\n' +
+  'on*= handlers are stripped on save — do not put behaviour here, only markup and CSS. ' +
+  'bleed:true makes the frame span the FULL page width with no gap or padding around it, so consecutive bleed blocks ' +
+  'stack into seamless edge-to-edge colour bands (the sandbox is unchanged). Inside a bleed block paint your own ' +
+  'full-width background and keep the content in a centred max-width wrapper; still set `height` (the frame does not auto-size). ' +
+  'minHeight:"screen" makes the frame ONE VIEWPORT TALL on every device (same rule as hero size:"screen": minus the top name bar, capped at 1200px); ' +
+  'a numeric `height` given with it becomes the FLOOR — frame height = max(one screen, height) — so give the height your content ' +
+  'needs on a short phone and nothing is clipped. Inside, take the frame height with `height:100%` (html and body already are 100%) ' +
+  'and centre the content with flexbox. bleed:true + minHeight:"screen" = a full-screen section; stack several for a ' +
+  'section-per-screen landing page.\n' +
   'LAYOUT: any block takes `width:"full"|"twoThirds"|"half"|"third"` — neighbouring blocks sit side by side (phones stack them). ' +
-  'That is how a page becomes a DASHBOARD: a row of `chart:"kpi"` blocks at width "third", then charts at width "half".\n' +
+  'That is how a page becomes a DASHBOARD: a row of `chart:"kpi"` blocks at width "third", then charts at width "half". ' +
+  'A hero with size:"screen" and a custom block with bleed:true always take the whole row — `width` is ignored (not stored) on them.\n' +
+  'REVEAL (scroll-in animation): any block takes `reveal:"fade"|"fade-up"` (default "none" = always visible). On the published page ' +
+  'the block appears ONCE when it scrolls into view (its top passes ~85% of the viewport height; blocks already on the first screen ' +
+  'play right after load): "fade" fades in, "fade-up" also rises a little. A hero staggers title → subtitle → button while its ' +
+  'background stays put. On a custom block, reveal ALSO starts the CSS animations inside the frame at that moment — the sandboxed ' +
+  'frame is created only when the block scrolls in, so `@keyframes`/`animation` in your html run from 0s exactly when the visitor ' +
+  'sees the section (without reveal they start at page load and are over before anyone scrolls down). Write those animations so ' +
+  'the content is still fine without them and wrap them in `@media (prefers-reduced-motion: no-preference)`. Visitors who ask ' +
+  'for reduced motion, and browsers without IntersectionObserver, simply see everything at once; nothing shifts layout. The editor ' +
+  'always shows blocks (the effect plays in its preview mode and on the published page).\n' +
+  'LANDING PAGE: start with hero size:"screen", follow with custom bleed:true bands (add minHeight:"screen" where a section should fill the screen), and set config.navEnabled:false so the hero owns the first screen. ' +
+  'All other blocks stay in the centred text column.\n' +
   'CHARTS (liveChart): chart ∈ bar|barH|stackedBar|stackedBarH|percentBar|lollipop|dumbbell|bullet|waterfall|pareto|radar|polarBar|line|step|area|stackedArea|percentArea|combo|slope|stream|calendar|pie|donut|halfDonut|rose|funnel|treemap|sunburst|waffle|histogram|boxplot|heatmap|scatter|bubble|sankey|chord|network|tree|kpi|gauge|progress|ring|candlestick|gantt|wordCloud|pivot. ' +
   'source = a DATABASE, SPREADSHEET or LOG node (sheet: {nodeId, sheet?(name), range?:"A1:F200"} — first row = column names, formula results are read). ' +
   'Category charts: labelColumn (dates are bucketed: dateBucket day|week|month|quarter|year|weekday|hour, empty periods filled with 0) + ' +

package/lib/mcp-tools/workspaces.js

@@ -3,8 +3,27 @@ import { z } from 'zod';
 import { textResult, jsonResult, errorResult, makeClient, requireWorkspace } from './shared.js';
 import { loadConfig } from '../config.js';
 import { currentClientOverride } from '../context.js';
-import { candidateClients, rememberWorkspace, resolveWorkspaceSwitch, surveyWorkspaces } from '../credentials.js';
+import {
+  candidateClients,
+  rememberSessionKey,
+  rememberWorkspace,
+  resolveWorkspaceSwitch,
+  surveyWorkspaces,
+} from '../credentials.js';
 import { parseRootrUrl } from '../resolve.js';
+import { t as tr } from '../i18n.js';
+
+/**
+ * ISSUE-221 — the workspace this server process was pinned to at launch via the
+ * ROOTR_WORKSPACE env var ('' when it was not). Read once, before any switch
+ * rewrites process.env: a switch on an env-pinned server only lasts as long as
+ * the process does (the MCP client passes the same env again on every restart
+ * or reconnect, and env deliberately wins over the config file), so the switch
+ * reply has to say where the server will be after a restart — otherwise the
+ * next write after a reconnect lands in the pinned workspace while the agent
+ * still believes it is in the one it switched to.
+ */
+const LAUNCH_WORKSPACE = process.env.ROOTR_WORKSPACE || '';
 
 /**
  * Scaffold `tree` argument schema. Declared as an ARRAY of node objects so MCP
@@ -22,6 +41,11 @@ const ACCESS_HINT =
   'lock) and `database.notifications` (who to notify on row changes). A database property may carry ' +
   '`searchExcluded: true` (values stay out of the search index behind ask / AI explore / similar rows — not a read permission) and a `type: "vector"` ' +
   'property needs `dimensions` (an embedding column agents fill with rootr_set_row_vectors). ' +
+  'A phone/email/name property may carry `dedupe: true` (warn when the same person is entered again) with ' +
+  '`dedupeShow: ["진행상태","특이사항","콜 이력"]` (fields of the existing row the warning shows — a relation shows its latest 5 rows); ' +
+  'a relation property may carry `relationFilter: [{ propId, op: "is"|"is_not_empty", values? }]` (which linked rows may be picked). ' +
+  'A board view config may carry `cardProps: ["면접예정일","연락처"]` (fields on each card, rollups too) and any view `rowColors` ' +
+  '(`[{ propId, op: "is"|"is_not_empty", values?, color }]`). ' +
   'A DOCUMENT\'s `content` may embed a live ' +
   'table/sheet/deck with a line `[[embed:<name of a node in this same tree>]]` or `[[embed:/absolute/path]]` — it is ' +
   'linked to the real node after the whole tree is built (an unknown name rolls the whole tree back).';
@@ -49,6 +73,8 @@ export function registerWorkspaceTools(server) {
         'reconfiguration, no restart. With an account key (PAT) you can switch to any workspace you belong ' +
         'to; if separate workspace keys are configured, the one that covers the target is selected and ' +
         'remembered automatically. Call rootr_workspaces first if you need to see what is available. ' +
+        'If the server was started with the ROOTR_WORKSPACE env var, the switch lasts until the server ' +
+        'restarts (the reply says so) — after a restart/reconnect, check rootr_workspaces again. ' +
         '(A hosted/remote connector is bound to a single workspace at consent time and cannot switch.)',
       annotations: { readOnlyHint: false, destructiveHint: false },
       inputSchema: {
@@ -91,6 +117,9 @@ export function registerWorkspaceTools(server) {
         // process, same request loop) picks up the switch immediately.
         if (process.env.ROOTR_WORKSPACE) process.env.ROOTR_WORKSPACE = match.workspace.id;
         if (process.env.ROOTR_API_KEY && match.candidate && match.candidate.apiKey !== process.env.ROOTR_API_KEY) {
+          // ISSUE-221 — the key being replaced may exist nowhere but in this
+          // process's environment; keep it so switching back still works.
+          rememberSessionKey(process.env.ROOTR_API_KEY);
           process.env.ROOTR_API_KEY = match.candidate.apiKey;
         }
         // Verify the switch actually took before reporting success — never
@@ -107,7 +136,23 @@ export function registerWorkspaceTools(server) {
           );
         }
         const name = match.workspace.name || match.workspace.slug || '';
-        return textResult(`활성 워크스페이스를 "${name}" (${match.workspace.id}) 로 바꿨습니다. 이후 도구 호출은 여기에 적용됩니다.`);
+        // ISSUE-221 — say how long the switch lasts when the server is env-pinned.
+        const pinnedNote =
+          LAUNCH_WORKSPACE && LAUNCH_WORKSPACE !== match.workspace.id
+            ? tr(
+                `\n주의: 이 MCP 서버는 ROOTR_WORKSPACE 환경변수(${LAUNCH_WORKSPACE})로 고정되어 시작됐습니다. 이 전환은 서버가 ` +
+                  `켜져 있는 동안만 유효하고, 서버가 재시작(재연결)되면 ${LAUNCH_WORKSPACE} 로 돌아갑니다 — 재시작 뒤에는 쓰기 전에 ` +
+                  'rootr_workspaces 로 현재 워크스페이스를 다시 확인하세요. 계속 이 워크스페이스를 쓰려면 MCP 서버 설정의 ' +
+                  `ROOTR_WORKSPACE 를 ${match.workspace.id} 로 바꾸거나 지우세요 (사용자가 직접).`,
+                `\nNote: this MCP server was started pinned to ROOTR_WORKSPACE=${LAUNCH_WORKSPACE}. The switch lasts only while ` +
+                  `the server keeps running; after a restart/reconnect it is back on ${LAUNCH_WORKSPACE} — check rootr_workspaces ` +
+                  'again before writing. To stay on this workspace, change (or remove) ROOTR_WORKSPACE in the MCP server ' +
+                  `config to ${match.workspace.id} (a step for the user).`,
+              )
+            : '';
+        return textResult(
+          `활성 워크스페이스를 "${name}" (${match.workspace.id}) 로 바꿨습니다. 이후 도구 호출은 여기에 적용됩니다.${pinnedNote}`,
+        );
       } catch (err) {
         return errorResult(err);
       }

package/package.json

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