@things-factory/ai-assistant 10.1.31 → 10.1.33

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@things-factory/ai-assistant",
-  "version": "10.1.31",
+  "version": "10.1.33",
   "main": "dist-server/index.js",
   "things-factory": true,
   "author": "heartyoh",
@@ -30,9 +30,9 @@
     "@operato/i18n": "^10.0.0",
     "@operato/styles": "^10.0.0",
     "@things-factory/ai-client-base": "^10.1.31",
-    "@things-factory/auth-base": "^10.1.31",
+    "@things-factory/auth-base": "^10.1.33",
     "@things-factory/env": "^10.1.20",
-    "@things-factory/shell": "^10.1.31",
+    "@things-factory/shell": "^10.1.33",
     "dompurify": "^3.0.0",
     "graphql-scalars": "^1.22.0",
     "graphql-tag": "^2.12.6",
@@ -44,5 +44,5 @@
     "copyfiles": "^2.4.1",
     "rimraf": "^5.0.0"
   },
-  "gitHead": "5213e6f9913b40ea2618a2111d9884b792dbaa01"
+  "gitHead": "7fb7b6587846b5ff6ee7a4983652d9561b4d6b2c"
 }

package/server/service/testing/mode-conformance.test.ts

@@ -0,0 +1,48 @@
+/*
+ * What this guards: the harness an app uses to check its own modes asks about **modes**, not about
+ * permission.
+ *
+ * `runRegisteredMode` answers "which tools does this mode open". Since the gate moved onto `doors`
+ * (ADR-0071 decision 2), a tool that names a door is closed to a caller with no access check —
+ * which is right in a request and wrong in a conformance run: an app checking that its mode opens
+ * four tools would see three, and the one that vanishes is the one that reads real data.
+ *
+ * So the harness runs as someone who passes every door, and an app that wants the other case names
+ * it. The permission axis has its own tests (`tool-access.test.ts` · `tool-scope.test.ts`).
+ */
+import { clearAssistantModes, registerAssistantMode } from '../assistant-mode/registry'
+import { clearToolRegistry, registerToolCategory } from '@things-factory/ai-client-base'
+
+import { runRegisteredMode } from './mode-conformance'
+
+const client = {
+  chatWithTools: async () => ({ text: '한 턴', toolCalls: [], stopReason: 'end_turn' })
+}
+
+beforeEach(() => {
+  clearAssistantModes()
+  clearToolRegistry()
+  registerToolCategory({
+    name: 'twin-authoring',
+    guidance: 'read the scene before proposing an edit',
+    specs: [
+      /* 화면이 보낸 것을 되돌려 준다 — 저장소에 안 닿는다. */
+      { kind: 'read', name: 'getOpenScene', description: 'the open scene', schema: {}, doors: [], builder: () => ({}) },
+      /* 저장소를 읽는다 — 문을 적는다. 관문이 이 자리를 가른다. */
+      { kind: 'read', name: 'getTwinStructure', description: 'the twin structure', schema: {}, doors: ['Query.twinInstances'], builder: () => ({}) }
+    ]
+  } as any)
+  registerAssistantMode({ kind: 'twin.space', systemPrompt: 'you answer about one space', toolCategories: ['twin-authoring'] } as any)
+})
+
+it('★ a mode opens the tools that read real data too — a conformance run is not a caller without permission', async () => {
+  const result = await runRegisteredMode('twin.space', { client })
+
+  expect(result.offeredTools.sort()).toEqual(['getOpenScene', 'getTwinStructure'])
+})
+
+it('an app that wants to see the other case names it — the door the caller cannot pass', async () => {
+  const result = await runRegisteredMode('twin.space', { client, toolAccess: async () => false })
+
+  expect(result.offeredTools).toEqual(['getOpenScene'])
+})

package/server/service/testing/mode-conformance.ts

@@ -52,7 +52,14 @@ export async function runRegisteredMode(
     temperature: settings.temperature,
     maxTokens: settings.maxTokens,
     hostContext: options.hostContext,
-    toolAccess: options.toolAccess,
+    /*
+     * 이 하네스가 묻는 것은 **모드**다 — 「이 모드가 무엇을 여는가」이지 「이 사람이 문을 지나는가」가
+     * 아니다. 관문이 `doors` 로 옮겨간 뒤(ADR-0071 결정 2) 검사를 안 넘기면 문을 적은 도구가 전부
+     * 닫히고, 그러면 앱의 적합성 시험에서 **실제 자료를 읽는 도구만** 조용히 사라진다. 그래서 기본은
+     * 모든 문을 지나는 사람이고, 다른 쪽을 보고 싶은 앱은 `toolAccess` 를 적어 그 경우를 쓴다.
+     * 권한 축은 자기 시험이 따로 본다(`tool-access.test.ts` · `tool-scope.test.ts`).
+     */
+    toolAccess: options.toolAccess ?? (async () => true),
     state: options.state ?? { domain: { id: 'dom-1' }, user: { id: 'u-1' } }
   })