Lutra/docs/target-app-parity.md
danny 1fc46daa8e M0: import starter package (rules, roadmap, progress docs)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 20:22:22 +02:00

2 KiB

Target-app parity

Status: baseline, nothing ships · Last updated: 2026-10-13 · Target: PhpStorm 2026.x

How this is measured

Each feature area gets a weight (how much a typical PHP developer uses it) and a score (how much of the documented behaviour Lutra has, judged by behaviour, not by menu items). The headline depth is the weighted sum. Every score is marked measured or estimated and must point to evidence (tests, commands, screenshots of Lutra). Behaviour references come from public PhpStorm documentation only, noted with URLs in plan/phpstorm/.

Feature areas

Area Weight Score Missing Hours (one agent) Evidence
Editor core 12 0% everything — —
Project view, VFS 6 0% everything — —
Navigation 10 0% everything — —
Search and replace 6 0% everything — —
Code completion 10 0% everything — —
Inspections and quick-fixes 8 0% everything — —
Refactoring 7 0% everything — —
Code style and formatting 4 0% everything — —
Git 8 0% everything — —
Terminal 3 0% everything — —
Run configurations 2 0% everything — —
Debugger 5 0% everything — —
Testing 4 0% everything — —
Composer and interpreters 2 0% everything — —
Frameworks 5 0% everything — —
Database tools 3 0% everything — —
HTTP client 1 0% everything — —
Web languages 2 0% everything — —
Docker and remote 1 0% everything — —
Settings, keymaps, themes 1 0% everything — —
Plug-ins 0.5 0% everything — —
AI features 0.5 0% everything — —

Weights are a first estimate and are reviewed at the end of M0.

Revision history

Date Change Summary
2026-10-13 major Baseline