feat: 远程群控 (#243)

* feat: restore pipe IPC, LAN pipes, monitor tool, and PR-package features

Core IPC system (UDS_INBOX):
- PipeServer/PipeClient with UDS + TCP dual transport, NDJSON protocol
- PipeRegistry: machineId-based role assignment, file locking
- Master/slave attach, prompt relay, permission forwarding
- Heartbeat lifecycle with parallel isPipeAlive probes
- Commands: /pipes, /attach, /detach, /send, /claim-main, /pipe-status

LAN Pipes (LAN_PIPES):
- UDP multicast beacon (224.0.71.67:7101) for zero-config LAN discovery
- PipeServer TCP listener, PipeClient TCP connect mode
- Heartbeat auto-attaches LAN peers via TCP
- Cross-machine attach allowed regardless of role
- /pipes shows [LAN] peers with role + hostname/IP
- SendMessageTool supports tcp: scheme with user consent

Architecture — extracted hooks from REPL.tsx (~830 lines → ~20 lines):
- usePipeIpc: lifecycle (bootstrap, handlers, heartbeat, cleanup)
- usePipeRelay: slave→master message relay via module singleton
- usePipePermissionForward: permission request/cancel forwarding
- usePipeRouter: selected pipe input routing with role+IP labels
- Shared ndjsonFramer.ts replaces 3 duplicate NDJSON parsers

Key fixes applied during development:
- Multicast binds to correct LAN interface (not WSL/Docker)
- Beacon ref stored as module singleton (not Zustand state mutation)
- Heartbeat preserves LAN peers in discoveredPipes and selectedPipes
- Disconnect handler calls removeSlaveClient (fixes listener leak)
- cleanupStaleEntries probes without lock, writes briefly under lock
- getMachineId uses async execFile (not blocking execSync)
- globalThis.__pipeSendToMaster replaced with setPipeRelay singleton
- M key only toggles route mode when selector panel is expanded
- User prompt displayed in message list on pipe broadcast
- Broadcast notifications show [role] + hostname/IP for LAN peers

Other restored features:
- Monitor tool: /monitor command, MonitorTool, MonitorMcpTask lifecycle
- Daemon supervisor and remoteControlServer command
- Tools: SnipTool, SleepTool, ListPeersTool, SendUserFileTool,
  WebBrowserTool, WorkflowTool, and 10+ stub→implementation rewrites
- Feature flags: UDS_INBOX, LAN_PIPES, MONITOR_TOOL, FORK_SUBAGENT,
  KAIROS, COORDINATOR_MODE, WORKFLOW_SCRIPTS, HISTORY_SNIP

Tests: 2190 pass / 0 fail (15 new: lanBeacon 7, peerAddress 8)

* fix: resolve merge conflicts and fix all tsc/test errors after main merge

- Export ToolResultBlockParam from Tool.ts (14 tool files fixed)
- Migrate ink imports from ../../ink.js to @anthropic/ink (7 files)
- Fix toolUseID → toolUseId typo in monitor.ts and MonitorTool.tsx
- Add fallback values for string|undefined type errors (8 locations)
- Fix AppState type in assistant.ts, add NewInstallWizard stubs
- Fix ParsedRepository.repo → .name in subscribe-pr.ts
- Fix AgentId/string type mismatch in BackgroundTasksDialog.tsx
- Fix PipeRelayFn return type in pipePermissionRelay.ts
- Use PipeMessage type in usePipeRelay.ts
- Fix lanBeacon.test.ts mock type assertions
- Create missing MouseActionEvent class for ink package
- Use ansi: color format instead of bare "green"/"red"
- Resolve theme.permission access via getTheme()

Result: 0 tsc errors, 2496 tests pass, 0 fail

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: 恢复 /poor 的说明

---------

Co-authored-by: unraid <local@unraid.local>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

src/utils/__tests__/pipePermissionRelay.test.ts

@@ -0,0 +1,76 @@
+import { afterEach, describe, expect, test } from 'bun:test'
+import {
+  clearPendingPipePermissions,
+  resolvePipePermissionResponse,
+  tryRelayPipePermissionRequest,
+  setPipeRelay,
+} from '../pipePermissionRelay.js'
+
+afterEach(() => {
+  setPipeRelay(null)
+  clearPendingPipePermissions()
+})
+
+function makeToolUseConfirm(overrides: Record<string, unknown> = {}) {
+  return {
+    assistantMessage: { message: { id: 'msg-1' } },
+    tool: { name: 'Bash' },
+    description: 'Run command',
+    input: { command: 'echo hello' },
+    toolUseID: 'tool-1',
+    permissionResult: { behavior: 'ask', message: 'Approve?' },
+    permissionPromptStartTimeMs: 1,
+    ...overrides,
+  } as any
+}
+
+describe('pipe permission relay', () => {
+  test('serializes permission requests through the active pipe sender', () => {
+    const sent: any[] = []
+    setPipeRelay((message: any) => {
+      sent.push(message)
+    })
+
+    const requestId = tryRelayPipePermissionRequest(
+      makeToolUseConfirm(),
+      () => {},
+    )
+
+    expect(requestId).toBeString()
+    expect(sent).toHaveLength(1)
+    expect(sent[0].type).toBe('permission_request')
+    const payload = JSON.parse(sent[0].data)
+    expect(payload.requestId).toBe(requestId)
+    expect(payload.toolName).toBe('Bash')
+    expect(payload.input).toEqual({ command: 'echo hello' })
+  })
+
+  test('dispatches permission responses to the pending request handler', () => {
+    setPipeRelay(() => {})
+    const seen: any[] = []
+    const requestId = tryRelayPipePermissionRequest(
+      makeToolUseConfirm(),
+      payload => {
+        seen.push(payload)
+      },
+    )
+
+    expect(requestId).toBeString()
+    const resolved = resolvePipePermissionResponse({
+      requestId: requestId!,
+      behavior: 'allow',
+      updatedInput: { command: 'echo ok' },
+      permissionUpdates: [],
+    })
+
+    expect(resolved).toBe(true)
+    expect(seen).toEqual([
+      {
+        requestId,
+        behavior: 'allow',
+        updatedInput: { command: 'echo ok' },
+        permissionUpdates: [],
+      },
+    ])
+  })
+})