PM: C4 review, M3 done and MVP feature-complete
Breadth recounted against the feature map (32/155), M3 measured at ~14 h of agent time (factor 0.17), full-parity hours re-scaled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
7420d5bdae
commit
e5891ddeb4
4 changed files with 13 additions and 10 deletions
13
ROADMAP.md
13
ROADMAP.md
|
|
@ -1,21 +1,21 @@
|
|||
# Lutra Roadmap
|
||||
|
||||
**Stage: pre-alpha (M2 done)** · next: M3 language server, terminal, CLI and MCP (the MVP); alpha when the six core workflows work end to end (see [docs/roadmap.md › Alpha gate](docs/roadmap.md#alpha-gate))
|
||||
**Stage: pre-alpha (M3 done: MVP feature-complete)** · next: hardening and Git (M4); 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-15 · **Last updated:** 2026-10-22 · **Change:** minor (M3.5: go to definition, find references, rename; after M3.4 completion) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only
|
||||
> **Last reviewed:** 2026-10-22 · **Last updated:** 2026-10-22 · **Change:** minor (C4 review: M3 done, breadth recounted, factor 0.17) · **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:** M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, a themed window). M1 lets you open a folder, browse it in the project tree, edit and save files in tabs, get unsaved text back after a crash, run every command from a palette and change settings and the theme in a settings dialog. M2 added PHP highlighting, find in files, a file structure view and go to file, class or symbol; PHP language intelligence (completion, diagnostics, go to definition) comes with M3. 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 lets you open a folder, browse it in the project tree, edit and save files in tabs, get unsaved text back after a crash, run every command from a palette and change settings and the theme in a settings dialog. M2 added PHP highlighting, find in files, a file structure view and go to file, class or symbol; M3 completed the MVP: diagnostics, completion, hover, signature help, go to definition, find references and rename via Phpactor, an integrated terminal, the `lutra` CLI and an MCP server. It stays pre-alpha until Git (M4) lands and the six core workflows are verified on macOS, Windows and Linux.
|
||||
|
||||
## Headline numbers
|
||||
|
||||
| | Value | Kind |
|
||||
|---|---|---|
|
||||
| **Feature breadth** (PhpStorm's actions, tool windows, languages, integrations exist) | **~18%** (28 of 155 feature units of the public PhpStorm help have at least partial support; ~21% after the running cycle C4) | estimated |
|
||||
| **Feature breadth** (PhpStorm's actions, tool windows, languages, integrations exist) | **~21%** (32 of 155 feature units of the public PhpStorm help have at least partial support) | estimated |
|
||||
| **Feature depth** (weighted by use, scored by behaviour) | **~5.1%** (Editor core 11% × weight 12, Navigation 13% × weight 10, Code completion 5% × weight 10, Inspections 4% × weight 8, Refactoring 3% × weight 7, Project view 8% × weight 6, Search and replace 8% × weight 6, Terminal 15% × weight 3, Settings 7% × weight 1, of 101) | estimated |
|
||||
| **To MVP (M3)** | **~12 h left** (M3 = 80 h raw × 0.15; done so far: M1 ~5.6 h, M2 ~6.1 h, measured); was ~190 h before calibration | estimated (factor per cycle: C1 0.07, C2 0.10, C3 0.14) |
|
||||
| **To full parity** | **~450 h** at the current factor of ~0.15 (range 300–3,300 h; the factor has risen each cycle, and deep areas such as type inference and inspections have no data yet) | estimated |
|
||||
| **MVP (M1–M3)** | **done** in ~26 h of agent time (M1 ~5.6 h, M2 ~6.1 h, M3 ~14 h, measured); was ~190 h before calibration | measured (factor per cycle: C1 0.07, C2 0.10, C3 0.14, C4 0.17) |
|
||||
| **To full parity** | **~520 h** at the current factor of ~0.18 (range 300–3,300 h; the factor has risen each cycle, and 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`](AGENTS.md) forbids it, so everything is measured from our code against public documentation.
|
||||
|
||||
|
|
@ -101,6 +101,7 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
|
|||
|
||||
| Date | Change | Summary |
|
||||
|---|---|---|
|
||||
| 2026-10-22 | minor | C4 review: M3 done (MVP feature-complete, ~14 h measured), breadth recounted 28 → 32 units (~21%), factor 0.17, full parity ~520 h at ×0.18 |
|
||||
| 2026-10-22 | minor | M3.4: Code completion 0% → 5% (est.), feature depth ~4.1% → ~4.6%, breadth 24 → 26 units |
|
||||
| 2026-10-22 | minor | M3.5: Navigation 10% → 13% (est.), Refactoring 0% → 3% (est.), feature depth ~4.6% → ~5.1%, breadth 26 → 28 units |
|
||||
| 2026-10-21 | minor | M3.3: Inspections 0% → 4% (est.), feature depth ~3.8% → ~4.1%, breadth 23 → 24 units |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue