Phase 005: vendor ArkScope, land the Arco style baseline, and fix bridge interpreter resolution

- Vendor ArkScope decorative layers (ScrambleTitle / IsometricWave) with provenance notes; decorative-only per AGENTS.md red lines
- Migrate theme tokens to Arco, register the Arco theme, and add hook adapter composables (useMessage / useDialog / useNotification) with matching signatures
- Sample pages: LoginView and AppSidebar on the new baseline; docs/arco-mapping.md and docs/ui-baseline.md land
- agent-bridge: prefer the PM-selected venv from facts.json over legacy in-tree venvs (legacy lacks the mcp extra, so every MCP server showed 0 tools / not connected)
- agent-bridge python (vendored, deliberate deviation): MCP discovery import fallback and pyyaml -> hermes_yaml so plugins and MCP work under the PM env; install the mcp extra via `hermes pm install --extra mcp`
- Chat-chain fragment: docs/chat-chain-changes/2026-10-17-phase005-arkscope-baseline.md

Verified: harness:check, test (2020 passed), test:e2e (30 passed), build all green; manual: plugins 100/0 warnings, MCP 6/6 servers connected with 104 tools.

This commit is contained in:

toor

2026-10-17 09:45:30 +08:00

parent 4701bf0ad0

commit 4baccd5d88

106 changed files with 1493 additions and 221 deletions

									
										tests/client/plugins-view.test.ts
									
		+3
		
												View File
												
				@@ -56,6 +56,9 @@ vi.mock('naive-ui', () => ({

				  useMessage: () => messageMock,

				}))

				// PluginsView reads messages via the Arco adapter layer, not naive-ui.

				vi.mock('@/composables/useMessage', () => ({ useMessage: () => messageMock }))

				import PluginsView from '@/views/hermes/PluginsView.vue'

				describe('PluginsView management actions', () => {