Your Name 81a77f1bcd Add Plan B: Vue 3 frontend port implementation plan ... Ten tasks: async-command backend fix, Tailwind 3 + Vite foundation, the 8 n-link-core components, the device store, the app shell, verification. Grounded in the real scaffold rather than assumptions. Reading the actual sources surfaced three hazards missing from the earlier follow-on notes: vue-async-computed (Vue 2 only, drives FileBrowser's listing and spinner), 30 require() calls in FileIcon, and @tailwindcss/custom-forms. Tailwind 3 chosen over 4: the theme is a JS config with 16 @apply/theme() uses in scoped SCSS, and 4's CSS-first rewrite would layer a second migration onto the Vue one. Task 1 fixes the command-serialization defect found during Plan A verification: all commands were sync, so a hung list_dir blocked the whole queue. It goes first because the UI is otherwise untestable on this hardware. Core components inject the store via an InjectionKey rather than importing it, so n-link-core stays decoupled from the desktop implementation and the web consumer remains portable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-21 20:24:09 -04:00
..
plans	Add Plan B: Vue 3 frontend port implementation plan	2026-07-21 20:24:09 -04:00
specs	docs+chore: address final review findings	2026-07-19 21:41:28 -04:00