@things-factory/board-ai 10.1.159 → 10.1.161

package/dist-server/service/assistant.js

@@ -121,32 +121,24 @@ class DefaultBoardAIAssistant {
          * 모아 붙이기만 한다(도메인 지식이 board-ai 프롬프트로 새지 않는다). */
         const guidance = (0, ai_client_base_2.getCategoryGuidance)(options.toolCategories);
         const surface = (options.surfacePrompt ?? '').trim();
+        const openSubject = (options.openSubject ?? '').trim();
         const systemPrompt = this.buildSystemPromptForTools(knownTypes, categories, schemas) +
             (surface ? `\n\n==== THIS SURFACE (declared by the app) ====\n${surface}` : '') +
+            /* Which board is open - the server's line from the stored anchor, the one way the model learns it (screen-pattern §2-1). */
+            (openSubject ? `\n\n==== OPEN SUBJECT ====\n${openSubject}` : '') +
+            (gate.coreOn ? `\n\n${READ_THE_BOARD}` : '') +
             (guidance.length ? `\n\n==== TOOL USE RULES (from the tools exposed to this conversation) ====\n${guidance.join('\n')}` : '') +
             (!gate.coreOn && options.boardToolsWithheld ? `\n\n${exports.BOARD_EDIT_WITHHELD}` : '');
         const selectedRefids = (options.selectedRefids ?? []).filter((n) => typeof n === 'number' && Number.isFinite(n));
-        // selection 정보는 항상 포함 (비어 있어도) — LLM 이 "선택된 게 뭐냐" 류 질문에
-        // getSelection 을 호출할지 판단하는 데 필요.
-        const selectionContext = selectedRefids.length > 0
-            ? `\n\nUser-selected component refids: ${JSON.stringify(selectedRefids)}\n` +
-                `When the user says "selected" / "선택한" / "this" / "그것" / "these" etc. ` +
-                `WITHOUT specifying targets, operate ONLY on these refids. ` +
-                `Do not modify other components unless explicitly asked. ` +
-                `For inspecting selected components, prefer calling \`getSelection\` over guessing.`
-            : `\n\nNo component is currently selected. If the user asks about "selected" / "this", ` +
-                `clarify or call \`getSelection\` to confirm.`;
-        const boardContext = currentBoard
-            ? `Current board state (JSON, summarized; full details via \`getComponent\` / \`findComponents\`):\n` +
-                `${JSON.stringify(summarizeBoard(currentBoard), null, 2)}` + selectionContext
-            : 'No current board (empty start).' + selectionContext;
-        let conversation = [
-            { role: 'user', content: boardContext },
-            ...messages.map(m => ({
-                role: m.role === 'assistant' ? 'assistant' : 'user',
-                content: m.content
-            }))
-        ];
+        /*
+         * The board and the selection are not pasted into the request any more (screen-pattern §2-2, 2026-10-13): the
+         * whole board went into every turn as a first user message, a second way of knowing the open board beside the
+         * server's line. The model reads what it needs with getBoardOutline · getSelection · findComponents.
+         */
+        let conversation = messages.map(m => ({
+            role: m.role === 'assistant' ? 'assistant' : 'user',
+            content: m.content
+        }));
         // multi-turn agentic loop — LLM 이 read 호출 → 서버 실행 → 결과 회신 → LLM 추론 반복.
         // write tool 은 누적해 client 에 patch 로 전달. 본체는 ./agentic-loop 에 분리.
         //
@@ -231,8 +223,7 @@ class DefaultBoardAIAssistant {
          * 근거집합의 정의와 사정거리는 ./grounding 머리말 참조(식별자 없는 창작 서술은 잡지 못한다). */
         const warnings = (0, grounding_1.checkReplyGrounding)(baseReply, {
             systemPrompt,
-            /* 근거집합의 칸 이름은 공용 패키지의 것이다 — 이 값이 보드 문맥이라는 것은 이 파일만 안다. */
-            hostContext: boardContext,
+            /* 보드는 이제 도구로만 모델에게 닿는다 — 읽은 보드는 toolResults 안에 있다(screen-pattern §2-2). */
             messages: messages.map(m => (typeof m.content === 'string' ? m.content : '')),
             toolResults: loopResult.groundedTexts
         });
@@ -244,7 +235,7 @@ class DefaultBoardAIAssistant {
                 confidence: { level: warnings.length ? 'low' : 'medium', reasons: warnings.length ? ['grounding-warning'] : ['tool-or-board-context'] },
                 limitations: warnings.map(code => ({ code })),
                 claims: [{ code: patch ? 'board.patch-proposed' : 'board.context-reviewed', severity: 'info', evidence: { toolCalls: toolUsages.length, componentCount: components.length }, method: 'board-agentic-loop', assumptions: ['Board context is current for this turn.'] }],
-                facts: { board: boardContext, toolUsages },
+                facts: { board: summarizeBoard(currentBoard), toolUsages },
                 ...(patch ? { proposal: patch } : accumulatedActions.length ? { proposal: accumulatedActions } : {}),
                 approvalRequired: true,
                 approval: { required: true, mode: 'confirm', reason: patch || accumulatedActions.length ? 'Board or scene change requires user confirmation.' : 'Analysis is advisory.' },
@@ -346,8 +337,8 @@ Rules:
 배열에 자식을 가질 수 있다. 자식이 또 group 일 수 있어 임의 깊이로 중첩 가능.
 
 가시성:
-  - \`summarizeBoard\` (대화 시작 시 보여지는 보드 상태) 는 *평면 list* 로 모든
-    컴포넌트를 노출한다 — top-level 뿐 아니라 group/container 안 자식도 모두 포함.
+  - \`getBoardOutline\` 은 *평면 list* 로 모든 컴포넌트를 돌려준다 — top-level 뿐 아니라
+    group/container 안 자식도 모두 포함.
   - 자식은 \`_parentRefid\` (부모 group refid) 와 \`_depth\` (중첩 깊이, 0=root) 메타
     가 첨부되어 어느 group 안에 있는지 식별 가능.
   - \`findComponents\` 는 전체 트리를 search — group 안 자식까지 매칭. 특정 group
@@ -537,7 +528,7 @@ Behavioral rules:
 - If the user is asking a question rather than commanding, REPLY in TEXT WITHOUT calling any tool.
 - If the user's request is ambiguous, REPLY in TEXT (asking for clarification) WITHOUT calling any tool.
 - For multiple components, call addComponent multiple times in parallel.
-- The current board JSON is provided as the first user message in the conversation.
+- The board is not in the conversation: read it with \`getBoardOutline\` (all components, flat) and the other read tools before you describe or change it.
 
 Reply formatting rules (chat surface):
 - Reply ONCE with ONE form only. NEVER restate the same answer in a second form (e.g. do NOT add a prose summary after a bullet list, or vice versa).
@@ -605,7 +596,7 @@ function buildBoardEditTools(knownTypes, exposure = {}) {
         },
         {
             name: 'removeComponentByRefid',
-            description: 'Remove an existing component by its `refid` — the universal numeric handle that things-scene auto-assigns to every component (visible in board summary as the `refid` field of each component).',
+            description: 'Remove an existing component by its `refid` — the universal numeric handle that things-scene auto-assigns to every component (each component in `getBoardOutline` carries it as `refid`).',
             parameters: {
                 type: 'object',
                 properties: {
@@ -696,6 +687,11 @@ function buildBoardEditTools(knownTypes, exposure = {}) {
             }
         },
         // ── Read tools (서버측 즉시 실행, 결과를 LLM 에 회신) ─────────
+        {
+            name: 'getBoardOutline',
+            description: 'The open board as it stands now, saved or not: its own attributes (size, background, ...) and every component in a flat list - group and container children included, each with `refid`, `type`, its key attributes and, for a child, `_parentRefid` / `_depth`. Call this before describing or changing the board. Full details of one component: getComponentByRefid.',
+            parameters: { type: 'object', properties: {} }
+        },
         {
             name: 'getSelection',
             description: 'Get full details of components currently selected by the user in the modeller. Call this when the user asks "what is selected?" / "선택된 게 뭐냐?" / refers to "the selected component" without specifying ids. Returns array of full component objects (no truncation).',
@@ -703,7 +699,7 @@ function buildBoardEditTools(knownTypes, exposure = {}) {
         },
         {
             name: 'getComponentByRefid',
-            description: 'Get full details of a single component by its `refid` (the things-scene-assigned universal numeric handle). Use this to inspect properties not visible in the board summary.',
+            description: 'Get full details of a single component by its `refid` (the things-scene-assigned universal numeric handle). Use this to inspect properties `getBoardOutline` leaves out.',
             parameters: {
                 type: 'object',
                 properties: {
@@ -1055,7 +1051,11 @@ function buildBoardEditTools(knownTypes, exposure = {}) {
     return tools;
 }
 // ── Read tool 분류 + 실행기 ────────────────────────────────────────
+/** How the model learns the board and the selection - by reading, every time it needs to (screen-pattern §2-2). */
+const READ_THE_BOARD = 'The board and the selection are not in the conversation. Read the board with `getBoardOutline` before you describe or change it, ' +
+    'and the selection with `getSelection` when the person says "selected", "this" or "these" without naming components; then work only on those.';
 const READ_TOOL_NAMES = new Set([
+    'getBoardOutline',
     'getSelection',
     'getComponentByRefid',
     'getComponentStyle',
@@ -1121,6 +1121,9 @@ function executeReadTool(call, currentBoard, selectedRefids) {
     // 컴포넌트 인지 가능. (top-level 만 보던 옛 동작 → 자식 누락 사고 방지)
     const flatComponents = (0, component_tree_1.collectAllComponents)(board).map(f => f.component);
     switch (call.name) {
+        case 'getBoardOutline':
+            /* The summary that used to be pasted into every request - now read when the question needs it. */
+            return board ? summarizeBoard(board) : { empty: true, message: 'No board is open in this conversation.' };
         case 'getSelection': {
             if (selectedRefids.length === 0) {
                 return { selected: [], message: 'No component is currently selected.' };