The three most recent pinpoints from the catalog. Each one is a single observed gap with a check that proves it is fixed.
Arcatect was framed as a source-modifying self-improvement agent. It could propose `[REBUILD]`, had UI for rebuild approvals, and Studio copy centered on changing Arca itself. That model is wrong for downloadable builds and confusing in normal project workspaces.
Arca's desktop chrome was visually dated against the Codex desktop reference. Top-level surfaces sat flush against the window edges and used hard 1-pixel borders + neutral panel backgrounds; dropdowns and modals leaned on heavy box-shadows with hard borders; the workspace view + manager-tab toggles cross-faded between options instead of animating; file references in the chat / NodeModal / TaskDetailDialog were either plain monospaced text or a generic `<code>` chip. Net effect: the harness read as "old Electron app" rather than "modern desktop tool". Canvas of nodes (React Flow) intentionally untouched; this is a chrome redesign.
Arca had no public surface. Anyone hearing about the harness had nowhere to read what it is, see the moving pieces, or join the beta waitlist. The app itself is internal-only and ships as a Tauri build, so there was no static front door at all.
