4 Commits

Include renames

Author	SHA1	Message	Date
toor	282624f801	adopt CYBER neon-dark theme tokens ... Replace the Pure Ink light/dark/comic theme system with the CYBER single-theme dark palette from the reviewed prototype: OKLCH surfaces, one neon-cyan accent, and monospace-first typography. Arco components were reading colors from arco.css because no ConfigProvider was mounted, so the theme values in arco-theme.ts never took effect. Bridge CYBER into Arco through its --color-* variables in global.scss instead, and align arco-theme.ts to match. Brightness and style switches are gone: useTheme now pins dark, the comic font faces and locale keys are removed, and ThemeSwitch.vue is deleted along with its sidebar slot and display setting.	2026-10-19 13:04:49 +08:00
toor	836d0228d2	Phase 007: migrate every remaining view from naive-ui to Arco Design Vue ... The project now has exactly one UI library. Every naive-ui component in packages/client/src is replaced by its Arco equivalent across 24 views and roughly 80 components, and naive-ui is dropped from package.json along with its transitive vueuc / @css-render / vdirs / seemly dependencies. The migration is rendering-layer only. No store logic, no API contract, and no /chat-run payload was touched. Three classes of leftover were invisible to `grep naive-ui` and are now covered by tests/client/no-naive-ui.test.ts, which asserts all three: - dead .n-* class names in style blocks - dead --n-* custom properties - naive-ui in package.json Notable behavioural traps handled along the way, recorded in docs/arco-migration-rules.md: - a-input-password defaults to masked; passing default-visibility="false" would have exposed API keys in clear text - a-upload fires a real XHR unless auto-upload is false - nested Trigger components fight over the first element child, so the group-chat settings dropdown was flattened - Arco renders tooltip default-slot text inline, which was silently collapsing the chat and group-chat toolbars	2026-10-18 22:57:25 +08:00
toor	4baccd5d88	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.	2026-10-17 09:45:30 +08:00
toor	1e9ea89d86	chore: bootstrap hermes-ui skeleton from 0.6.29 snapshot ... Import the client, server, skills, tests, and build scripts as the starting point for the rebuild, then trim the surfaces this project does not ship: Electron desktop packaging, the marketing website, and the ESP32 firmware tree. CI keeps the web build, e2e, lockfile, release, and Docker workflows. Rename the package and CLI entry points to hermes-ui, drop the prepare hook so npm ci no longer triggers a build, and drop the removed tsconfig and nodemon references. Rewrite AGENTS.md, ARCHITECTURE.md, DEVELOPMENT.md, and the READMEs so the documented package map and hard rules match this repository. reference_code/ is ignored: it is a read-only snapshot, not an input to the build.	2026-10-16 10:34:35 +08:00