Reactor-11
● Got it — decision made: scrap the PowerShell/WPF hub and rewrite it as a real MUI (Material Design 3) app. No more hand-drawn XAML, no terminal windows. Before
I burn hours building the wrong thing, one call is genuinely yours to make because it changes the whole delivery model (and how you launch/update it) —
everything else I'll just decide and build.
Here's what I found so the choice is concrete:
- The current hub is tools/reactor_sync_win/hub/dashboard-app.ps1 — 992 lines of hand-built WPF drawn in PowerShell (custom brushes/templates), which is
exactly the "not a real UI library" look. It spawns hidden powershell.exe processes for ssh/git/hash work → the terminal flashes.
- "dirty:1 / dirty:11" is status.ps1:109 — it's just git's uncommitted-file count (dirty:$n). Easy rename (→ e.g. "1 changed" / "1 unsynced") in the new UI.
- The "yaml won't resolve" is the size-based diff (rs-engine.ps1) flagging a .yaml as perpetually DIFFER — almost certainly CRLF↔LF (Windows vs box line
endings change the byte size so it never matches). I'll fix that in the rewrite's engine too.
☐ App shell
How should the new MUI3 hub run on your Windows laptop? (The UI is React + MUI v6/Material Design 3 either way — this is only about the shell that hosts it.)
❯ 1. Tauri native app ┌──────────────────────────────────────────┐
(Recommended) │ ┌─ reactor-sync ─────────────┐ │
2. Electron app │ │ ● Projects ⟳ Sync ⚙ │ │
3. Local web app in browser │ │ ───────────────────────── │ │
│ │ reactor-11 ✔ synced │ │
│ │ reactor-1 ● 1 changed │ │
│ │ app-core ✔ verified │ │
│ Standalone native window, no browser │
Notes: press n to add notes
Chat about this
Enter to select · ↑/↓ to navigate · n to add notes · Esc to cancel