Lutra/ROADMAP.md
danny dd98636de4 M1.4: desktop bridge: engine events to the window, folder picker, live project tree
The desktop host publishes every engine event, from commands and from a
pump thread that calls Engine::pump_vfs every 100 ms, to control channel
subscribers and to the window as the Tauri event engine://event, in engine
order. ui/src/ipc.ts gets a typed onEngineEvent; its first subscription
calls engine_ready, and the host replays the current project and buffers,
so a project opened from the command line (lutra-desktop --control PORT
PATH) reaches the UI. project.openDialog returns Effect::PickFolder; the
host shows the native folder picker (tauri-plugin-dialog, licence checked)
and opens the choice, one picker at a time, cancel is not an error.
Capabilities shrink to event listen/unlisten.

Contract fix: the M1.5 project UI assumed shapes the engine does not use.
engineEvents.ts now translates engine events ({kind: projectOpened, ...})
and project.children results ({dir, entries, truncated}) into the UI types,
keeping role and truncated; the store maps listings through
toTreeEntries() and the project tests use the real engine shapes.

Verified in the running app on Windows 11: tree of a project given on the
command line, expanding src, a file created on disk appearing live, the
folder picker opening one dialog and opening the chosen folder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 06:41:49 +02:00

5.8 KiB
Raw Blame History

Lutra Roadmap

Stage: pre-alpha (foundation done) · next: M1 editor and project; alpha when the six core workflows work end to end (see docs/roadmap.md › Alpha gate)

Last reviewed: 2026-10-14 · Last updated: 2026-10-15 · Change: minor (project tree works against the engine) · 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: milestone M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, an empty themed window), but no PHP feature exists yet. M1–M3 deliver the MVP.

Headline numbers

Value Kind
Feature breadth (PhpStorm's actions, tool windows, languages, integrations exist) 0% measured
Feature depth (weighted by use, scored by behaviour) ~0.5% (Project view 8% × weight 6) estimated
To MVP (M3) ~190 h (M1 ~60 h, M2 ~50 h, M3 ~80 h) estimated
To full parity ~3,300 h (range 2,000–5,000 h) 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 from merged-commit timestamps after each milestone. 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) ~0.5% ~2,930 target-app-parity.md
UI/UX fidelity 0% ~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) 0% ~40 localization-parity.md
Performance 0% ~100 gaps.md › G12
Stability 5% ~100 gaps.md › G11
Agent automation 10% ~60 AGENTS.md

Stability 5%: no-panic lints, the engine guard and a fuzzed control protocol exist; the recovery journal does not. Agent automation 10%: the control channel (ping, execute, listCommands, screenshot) works; MCP and the CLI do not exist yet. Both are estimated.

Features

Area % One agent (h)
Editor core (buffers, undo, multi-caret, folding, soft wrap) 0% ~120
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 0% ~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 (~60 h): open folder, project tree, tabs, editor, save and recovery, command palette, settings, themes.
  2. M2 syntax and search (~50 h): highlighting, file structure, find in files, go to file/class/symbol.
  3. M3 language server, terminal and CLI (~80 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-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-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