From 851d438e2a0fb22a3e2c7cdc9ff6c076460ea39c Mon Sep 17 00:00:00 2001 From: danny Date: Thu, 15 Oct 2026 18:38:39 +0200 Subject: [PATCH] PM: review cycle 1 Stage line, feature breadth estimate, M1-M3 hours recalibrated x0.1 after cycle C1 (2.5 h agent time for 37 h estimated). Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- ROADMAP.md | 21 +++++++++++---------- docs/roadmap.md | 13 +++++++------ docs/target-app-parity.md | 3 ++- 4 files changed, 21 insertions(+), 18 deletions(-) diff --git a/README.md b/README.md index 3d55274..86351b1 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ claude mcp add lutra -- lutra mcp ## Status -**Pre-alpha (2026-10-15): M1 in progress.** You can open a folder, browse it in the project tree with live updates from disk, and edit and save files in tabs (plain text for now); syntax highlighting and PHP features come next. The MVP (M1–M3) is estimated at about 190 agent hours. [**ROADMAP.md**](ROADMAP.md) has the stage and what's next, +**Pre-alpha (2026-10-15): M1 in progress.** You can open a folder, browse it in the project tree with live updates from disk, and edit and save files in tabs (plain text for now); syntax highlighting and PHP features come next. The MVP (M1–M3) is estimated at about 20 agent hours after calibrating on the first cycle (2.5 h done). [**ROADMAP.md**](ROADMAP.md) has the stage and what's next, [`docs/target-app-parity.md`](docs/target-app-parity.md) the parity assessment and [`docs/gaps.md`](docs/gaps.md) the ranked work list. **First target (MVP, M1–M3):** open a project, project tree, tabs, editor with highlighting, find in files, diff --git a/ROADMAP.md b/ROADMAP.md index 77b5f57..2051d81 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1,23 +1,23 @@ # 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](docs/roadmap.md#alpha-gate)) +**Stage: pre-alpha (M1 in progress)** · next: the rest of M1 (recovery, palette, settings, themes), then M2 syntax and search; alpha when the six core workflows work end to end (see [docs/roadmap.md › Alpha gate](docs/roadmap.md#alpha-gate)) -> **Last reviewed:** 2026-10-14 · **Last updated:** 2026-10-15 · **Change:** minor (tabs and editor in the app) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only +> **Last reviewed:** 2026-10-15 · **Last updated:** 2026-10-15 · **Change:** minor (cycle C1 review: estimates recalibrated) · **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`](docs/target-app-parity.md) and the work list in [`docs/gaps.md`](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. +**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) | **0%** | measured | +| **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.4%** (Editor core 8% × weight 12, Project view 8% × weight 6, of 101) | 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 | +| **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 from merged-commit timestamps after each milestone. PhpStorm is **not** inspected: the clean-room rule in [`AGENTS.md`](AGENTS.md) forbids it, so everything is measured from our code against public documentation. +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`](AGENTS.md) forbids it, so everything is measured from our code against public documentation. ## By dimension @@ -68,9 +68,9 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a ## 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.** +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 @@ -86,6 +86,7 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a | Date | Change | Summary | |---|---|---| +| 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 | diff --git a/docs/roadmap.md b/docs/roadmap.md index 552c8c7..ad08333 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -2,14 +2,14 @@ > **Status:** M0 done, M1 in progress · **Last updated:** 2026-10-15 -Hours are agent wall-clock hours for one agent; M0 is measured, the rest estimated. +Hours are agent wall-clock hours for one agent; M0 and M1 so far are measured, the rest estimated. Since cycle C1 (factor 0.07) M1–M3 are scaled ×0.1; M4–M6 keep their first raw estimates (multiply by ~0.1 for the calibrated value). | Milestone | Goal | State | Hours | |---|---|---|---:| -| M0 | Foundation: workspace, lints, quality gate, command registry, control channel, empty window | done 2026-10-14 (CI workflow written, not yet run: no remote) | ~2 (measured) | -| M1 | Editor and project: open folder, tree, tabs, editor, save, recovery, palette, settings, themes | in progress (M1.1 text, M1.2 VFS, M1.5 tree UI, M1.3 engine workspace, M1.4 desktop bridge, M1.6 tabs and editor) | ~60 | -| M2 | Syntax and search: highlighting, structure, find in files, go to file/class/symbol | not started | ~50 | -| M3 | LSP, terminal, CLI: completion, diagnostics, go to definition, hover, rename; terminal; `lutra` CLI and MCP — **MVP** | not started | ~80 | +| M0 | Foundation: workspace, lints, quality gate, command registry, control channel, empty window | done 2026-10-14 (CI workflow written, not yet run: hosted on Forgejo, runners unknown) | ~2 (measured) | +| M1 | Editor and project: open folder, tree, tabs, editor, save, recovery, palette, settings, themes | in progress (M1.1 text, M1.2 VFS, M1.5 tree UI, M1.3 engine workspace, M1.4 desktop bridge, M1.6 tabs and editor) | ~6 (2.5 measured for M1.1–M1.6) | +| M2 | Syntax and search: highlighting, structure, find in files, go to file/class/symbol | not started | ~5 | +| M3 | LSP, terminal, CLI: completion, diagnostics, go to definition, hover, rename; terminal; `lutra` CLI and MCP — **MVP** | not started | ~8 | | M4 | Git: status, diff, commit, branches, log, blame, conflicts | not started | ~150 | | M5 | Debugger (Xdebug via DAP), PHPUnit/Pest runner, Composer, run configurations | not started | ~300 | | M6 | Own indexer and inspections; Symfony, Laravel, Shopware, WordPress support | not started | ~1,100 | @@ -25,12 +25,13 @@ Alpha is reached when these six core workflows work end to end on macOS, Windows 5. Commit, diff and switch branches with Git. 6. Drive all of the above from the CLI, the control channel and MCP. -By the estimates above the alpha gate needs M1–M4 plus cross-platform verification, about 350 h. +By the raw estimates the alpha gate needs M1–M4 plus cross-platform verification, about 350 h; calibrated with cycle C1's factor, about 35 h of agent time. Calendar time is dominated by reviews and owner decisions, not agent time. ## Revision history | Date | Change | Summary | |---|---|---| +| 2026-10-15 | minor | Cycle C1 review: M1–M3 hours recalibrated ×0.1, M0 CI note | | 2026-10-15 | minor | M1.6 tabs and editor | | 2026-10-15 | minor | M1.4 desktop bridge | | 2026-10-14 | minor | M1 in progress | diff --git a/docs/target-app-parity.md b/docs/target-app-parity.md index 1e06d1f..e471f81 100644 --- a/docs/target-app-parity.md +++ b/docs/target-app-parity.md @@ -35,7 +35,7 @@ Hours are the estimated agent wall-clock hours for one agent to reach behaviour | Plug-ins | 0.5 | 0% | everything | ~120 (est.) | — | | AI features | 0.5 | 0% | everything | ~60 (est.) | — | -Sum: about 2,920 h. Adding UI fidelity (~150 h), localization (~40 h), performance (~100 h) and stability hardening (~100 h) gives the ROADMAP's ~3,300 h to full parity. The range is wide (2,000–5,000 h): completion, inspections, refactoring and frameworks depend on an own type-inference engine whose size is hard to judge before M6. +Sum: about 2,920 h. Adding UI fidelity (~150 h), localization (~40 h), performance (~100 h) and stability hardening (~100 h) gives the ROADMAP's ~3,300 h to full parity. These are the raw first estimates. Cycle C1 (M1.1–M1.6) took 2.5 h of agent time for 37 h estimated (factor 0.07), so the calibrated full-parity figure is ~330 h if that speed holds for deeper areas; the ROADMAP shows the range 300–3,300 h until M2/M3 give data for language work. The range is wide (2,000–5,000 h): completion, inspections, refactoring and frameworks depend on an own type-inference engine whose size is hard to judge before M6. Weights were reviewed at the end of M0 and kept: nothing built so far gives a reason to change them. @@ -61,6 +61,7 @@ The project tree is the first user-visible feature (Project view 8%, estimated); | Date | Change | Summary | |---|---|---| +| 2026-10-15 | minor | Calibration note after cycle C1 (factor 0.07) | | 2026-10-15 | minor | Editor core 0% → 8% (estimated): tabs and editor in the app (M1.6) | | 2026-10-15 | minor | Project view 0% → 8% (estimated): tree runs against the engine in the app (M1.4) | | 2026-10-14 | minor | Project view evidence: project tree UI (M1.5), score unchanged |