Lutra/ROADMAP.md
danny f41df518b5 M1.12: notifications as toasts
The host publishes picker, command-line and pump errors as notification
events (Engine::notify, same id sequence) instead of stderr, keeps
notifications and watchFailed published before engine_ready and replays
them after the state replay, so startup warnings (corrupt settings,
journal entries) reach the UI. ipc.ts announces engine_ready once all
subscriptions started together are registered.

Frontend: notifications store and NotificationStack (bottom right, info
auto-dismissed after 5 s, warnings/errors stay, close button and Escape,
at most 5 visible with "+n more", role status/alert); watchFailed maps to
a warning toast; failed commands without their own UI raise an error
toast. Catalog keys notification.settings.*, project.*, vfs.*, watch.*,
command.* plus the runtime allow-list. Docs updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 16:20:45 +02:00

8.6 KiB
Raw Blame History

Lutra Roadmap

Stage: pre-alpha (M1 in progress) · next: the rest of M1 (palette, settings, themes), then M2 syntax and search; alpha when the six core workflows work end to end (see docs/roadmap.md › Alpha gate)

Last reviewed: 2026-10-15 · Last updated: 2026-10-16 · Change: minor (M1.12: notifications) · Target: JetBrains PhpStorm 2026.x, described from public documentation only

Lutra is a clean-room, open-source PHP IDE with a Rust core and a Tauri + Vue interface, targeting the PhpStorm workflow. Agents can drive all of it over MCP, the lutra CLI and a JSON control channel. This page is the summary; the evidence is in docs/target-app-parity.md and the work list in docs/gaps.md.

Why pre-alpha: M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, a themed window). M1 so far lets you open a folder, browse it in the project tree and edit and save files in tabs, but as plain text: no PHP feature (highlighting, completion, navigation) exists yet. M1–M3 deliver the MVP.

Headline numbers

Value Kind
Feature breadth (PhpStorm's actions, tool windows, languages, integrations exist) <1% (project tool window, editor tabs; no inventory to count against yet) estimated
Feature depth (weighted by use, scored by behaviour) ~1.6% (Editor core 9% × weight 12, Project view 8% × weight 6, Settings 4% × weight 1, of 101) estimated
To MVP (M3) ~20 h (M1 ~6 h of which 2.5 h done, M2 ~5 h, M3 ~8 h); was ~190 h before calibration estimated (×0.1 from cycle C1)
To full parity ~330 h if cycle C1's speed holds (range 300–3,300 h; deep areas such as type inference and inspections have no data yet) estimated

Hours are agent wall-clock hours for one agent. M0 took about 2 h of active agent time (measured from the session, excluding toolchain installation and waiting for owner decisions). Later milestones are estimated far more conservatively per line of code, because editor, language and UI work need integration, debugging and visual checks that the foundation did not. Estimates are recalibrated after each cycle from task start times and commit timestamps. Cycle C1 (M1.1–M1.6) took 2.5 h of agent time for 37 h estimated (factor 0.07); M1–M3 hours are scaled by ×0.1 since then, and the per-area hours below are the raw first estimates (multiply by ~0.1 for the calibrated value). PhpStorm is not inspected: the clean-room rule in AGENTS.md forbids it, so everything is measured from our code against public documentation.

By dimension

Dimension hours overlap: language, framework and tooling hours are part of the feature total.

Dimension % One agent (h) Doc
Features (depth) ~1.6% ~2,920 target-app-parity.md
UI/UX fidelity 1% (est.) ~150 on top of features ui-parity.md
PHP language support 0% ~920 (in features) language-parity.md
Frameworks (Symfony, Laravel, Shopware, WordPress) 0% ~300 (in features) framework-parity.md
Tooling (Git, terminal, debugger, tests, Composer, DB) 0% ~730 (in features) tooling-parity.md
Localization (en, de) 5% ~38 localization-parity.md
Performance 0% ~100 gaps.md › G12
Stability 8% ~95 gaps.md › G11
Agent automation 10% ~60 AGENTS.md

Stability 8%: no-panic lints, the engine guard, a fuzzed control protocol and a crash-recovery journal for unsaved buffers (property-tested: random edits, crash, restore) exist; the journal is not yet checked in the running app. Agent automation 10%: the control channel (ping, execute, listCommands, screenshot) works; MCP and the CLI do not exist yet. Both are estimated. Localization 5% (estimated): every UI string comes from an English catalog enforced by lint; engine messages, the language switch and German are missing. UI/UX fidelity 1% (estimated): light and dark themes switch live and pass a WCAG AA contrast test; the rest of the ui-parity checklist is open.

Features

Area % One agent (h)
Editor core (buffers, undo, multi-caret, folding, soft wrap) 9% (est.) ~106
Project view, VFS, file watching 8% (est.) ~40
Navigation (go to class/file/symbol, recent files, structure) 0% ~120
Search and replace (in file, in project, structural) 0% ~80
Code completion 0% ~250
Inspections and quick-fixes 0% ~300
Refactoring 0% ~250
Code style and formatting 0% ~120
Version control (Git) 0% ~150
Terminal 0% ~30
Run configurations 0% ~50
Debugger (Xdebug) 0% ~120
Testing (PHPUnit, Pest) 0% ~80
Composer and PHP interpreters 0% ~50
Frameworks 0% ~300
Database tools 0% ~250
HTTP client 0% ~60
Web languages (JS/TS, Vue, CSS, Twig, Blade) 0% ~200
Docker and remote 0% ~120
Settings, keymaps, themes 4% (est.) ~60
Plug-ins and ecosystem 0% ~120
AI features 0% ~60

All hours estimated. Weights, evidence and the missing items per area: target-app-parity.md.

Upcoming

  1. M1 editor and project (~6 h, 2.5 h done): open folder, project tree, tabs, editor, save and recovery, command palette, settings, themes.
  2. M2 syntax and search (~5 h): highlighting, file structure, find in files, go to file/class/symbol.
  3. M3 language server, terminal and CLI (~8 h): completion, diagnostics, go to definition via Phpactor; terminal; lutra CLI and MCP. MVP.
  4. Then: Git (M4), debugger, tests and Composer (M5), own indexer and frameworks (M6).

Progress log

Date What landed
2026-10-16 M1.12: errors and notices reach the user as toasts instead of stderr: a corrupt settings file or recovery entry, a folder that cannot be opened (also with unsaved changes when switching projects), stopped file watching and failed commands without their own UI. Info toasts go away after 5 s, warnings and errors stay.
2026-10-16 M1.7: unsaved text survives a crash. Dirty buffers are journaled about a second after the last edit; the next open offers them in a restore dialog (restore all, selected, or discard), with line endings and BOM kept.
2026-10-16 M1.10: Lutra Light next to Lutra Dark, switched live through the appearance.theme setting or following the OS (system); the window starts in the stored theme; the editor, tabs and notices get their own tokens; both themes pass a WCAG AA contrast test.
2026-10-15 M1.11: every interface string comes from an English message catalog (ui/src/i18n/en.json), enforced by a lint rule and a catalog test; the groundwork for German.
2026-10-15 M1.6: files open in tabs with a CodeMirror editor synced to the engine; save, save all, close with a Save / Don't Save / Cancel question, a notice when a file with unsaved changes changes on disk; a 1 MB file opens in about 90 ms.
2026-10-15 M1 so far: text buffer, VFS with native watching, engine workspace (files, buffers, edit protocol, events), desktop bridge: open a folder by picker or command line, browse it in the project tree with live updates from disk.
2026-10-14 M0 foundation: Cargo workspace with layered crates, no-panic lints with a self-test, cargo xtask ci (fmt, clippy, tests, layers, assets, clean-room, licences, frontend lint/typecheck/tests), Vue frontend, command registry with panic guard (app.about, app.quit), JSON control channel, Tauri window themed from Rust tokens, CI workflow. First estimates.
2026-10-13 Project started: name, conventions, agent rules and progress docs.

Revision history

Date Change Summary
2026-10-16 minor M1.12: progress log (headline unchanged)
2026-10-16 minor M1.7: Stability 8%, Editor core 9%, feature depth ~1.6% (with Settings 4% from M1.10)
2026-10-16 minor M1.10: UI/UX fidelity 1%, Settings row 4% (estimates), progress log
2026-10-15 minor M1.11: localization 5% (English UI catalog), progress log
2026-10-15 minor Cycle C1 review: stage line, breadth estimate, hours recalibrated ×0.1
2026-10-15 minor Feature depth ~1.4%: tabs and editor (M1.6)
2026-10-15 minor Feature depth above 0%: project tree runs against the engine (M1.4)
2026-10-14 minor M0 done; MVP and parity estimates; stability and agent automation scored
2026-10-13 major Initial roadmap