PM: C4 review, M3 done and MVP feature-complete
Some checks failed
ci / ci (macos-15) (push) Has been cancelled
ci / ci (ubuntu-24.04) (push) Has been cancelled
ci / ci (windows-2025) (push) Has been cancelled

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:
danny 2026-10-22 18:54:43 +02:00
parent 7420d5bdae
commit e5891ddeb4
4 changed files with 13 additions and 10 deletions

View file

@ -9,7 +9,7 @@ Each feature area gets a weight (how much a typical PHP developer uses it) and a
Hours are the estimated agent wall-clock hours for one agent to reach behaviour parity in the area, from zero. They are first estimates made at the end of M0 and are recalibrated after each milestone from merged-commit timestamps.
**Breadth inventory (2026-10-18).** Breadth is counted against the public PhpStorm help table of contents (https://www.jetbrains.com/help/phpstorm/HelpTOC.json): 155 level-1 feature units across 20 sections, without getting-started, reference, tutorial, troubleshooting and FAQ pages. A unit counts when Lutra has at least partial behaviour for it. Now 26/155 (~17%, estimated; M3.4 added completion and hover); the running cycle C4 adds 9 (completion, diagnostics, rename, hover, PHP interpreter, terminal, CLI, MCP server, main menu). Sections with no support yet: version control, debugging, run configurations, testing and profiling, code quality tools, frameworks (Laravel, Symfony, WordPress, others), deployment, database tools, HTTP client, SSH/Docker/WSL, remote development, Dev Containers, AI. Only titles and URLs are used; behaviour is read from each public page when the feature is planned.
**Breadth inventory (2026-10-18).** Breadth is counted against the public PhpStorm help table of contents (https://www.jetbrains.com/help/phpstorm/HelpTOC.json): 155 level-1 feature units across 20 sections, without getting-started, reference, tutorial, troubleshooting and FAQ pages. A unit counts when Lutra has at least partial behaviour for it. Now 32/155 (~21%, estimated): the 23 units of 2026-10-18 plus 9 from C4 (completion, diagnostics, rename, hover and signature help, PHP interpreter, terminal, CLI, MCP server, main menu). Sections with no support yet: version control, debugging, run configurations, testing and profiling, code quality tools, frameworks (Laravel, Symfony, WordPress, others), deployment, database tools, HTTP client, SSH/Docker/WSL, remote development, Dev Containers, AI. Only titles and URLs are used; behaviour is read from each public page when the feature is planned.
## Feature areas
| Area | Weight | Score | Missing | Hours (one agent) | Evidence |
@ -65,6 +65,7 @@ The project tree is the first user-visible feature (Project view 8%, estimated);
| Date | Change | Summary |
|---|---|---|
| 2026-10-22 | minor | C4 review: breadth recounted against the feature map, 32/155 |
| 2026-10-22 | minor | M3.5: Navigation 10% → 13% (est.), go to definition and find references; Refactoring 0% → 3% (est.), rename; hours 102 → 96 and 250 → 244 |
| 2026-10-22 | minor | M3.4: Code completion 0% → 5% (est.), completion, hover and signature help from Phpactor; hours 250 → 240; breadth 26/155 |
| 2026-10-21 | minor | M3.3: Inspections and quick-fixes 0% → 4% (est.), diagnostics from Phpactor and the Problems tab; hours 300 → 290 |