1. Why it's not MUI / why it looks hand-drawn. Because it literally is hand-drawn. The hub (dashboard-app.ps1) is a WPF window written as raw XAML inside a 
  PowerShell string, with every button/table styled by hand via ControlTemplate. The tray + offline badge (TrayApp.cs) is raw WinForms. There is zero component
  library. The reason it ended up that way: the whole tool was designed to run on a locked-down corporate laptop with nothing installed — no Node, no npm, no
  .NET assumptions — just "double-click a .cmd, it self-updates from the box." WPF/WinForms ship inside Windows, so that's all it could use without an installer.
  React/MUI need a build toolchain and a host, which the original zero-install design deliberately refused. That constraint is exactly what we have to decide
  about now.

  2. "going through terminal always." The hub actually runs almost everything hidden — sync/pull/build/status all spawn powershell -WindowStyle Hidden and stream
  output into the window. A real terminal only pops for interactive dev commands (flutter run, ng serve, npm start, Deploy) that you need to type into — plus
  the install .cmd. In the rewrite that all becomes an embedded console panel in the app (xterm.js) — no stray Windows Terminal windows ever.

  3. "dirty 1 / dirty 11." That's not a name and it's not about reactor 1 / reactor 11. It's status.ps1:109 — the git worktree column: dirty:N means "this repo
  has N uncommitted changes," clean means none. So dirty:11 = 11 modified files sitting in that repo. I'll relabel it to plain English (11 changed / ✓ clean, or
  a colored dot) in the rewrite — or right now if you want.

  4. The YAML. I syntax-checked every recently-touched one (mcad-app/azure-pipelines-v4.4.plus.yml, build-android/ios/windows.yml, both pubspec.yaml, etc.) —
  they all parse clean. So "won't resolve" is a semantic/tooling failure (Azure Pipelines extends/template/resources not resolving, or flutter pub get
  version-solving, or editor-schema squiggles), not broken syntax. I can't guess which of ~40 files you mean — so I need you to point me at it.

  Two things gate the rest, so let me ask both at once, then I'll start building:

● User declined to answer questions
  ⎿  · You want a real MUI app — good. The one choice that reshapes everything is how we package it, because the current tool's whole point is zero-install on a
     locked-down laptop. What do we build it as? (In all cases the UI is a real MUI / Material-Design-3 app; this is about the shell + install.) (Tauri v2 + 
     React + MUI / Local web / PWA + MUI / Flutter Desktop (M3) / Electron + React + MUI)
     · Which YAML is the one that won't resolve? (Every recent one parses clean, so it's a resolve/tooling error, not syntax — pick the file/area and I'll dig 
     into the real error.) (mcad-app Azure Pipelines / A Flutter pubspec.yaml / mcad-service APIOps yaml / Something else)

● No problem — let me not railroad you into a multiple-choice box. What would you like to clarify or push back on? A few things it might be:

                                                                                                                                                 ◈ max · /effort

❯ if this is for windows desktop we want the purest

  ⏵⏵ bypass permissions on (shift+tab to cycle)