Lutra/docs/target-app-parity.md
danny 5d49b57b9c M1.2: vfs with ignore rules, polling watcher and safe file IO
- Project::open canonicalises the root (no \?\ prefix on Windows where
  safe); typed errors for missing and non-directory paths.
- Lazy children(dir): dirs first, case-insensitive; kind, ignored flag
  and role (vendor/ library, node_modules/ excluded, .git hidden).
- Ignore rules via the ignore crate: .gitignore, .ignore,
  .git/info/exclude, global git excludes, with git precedence.
- Watcher: std-only polling (100 ms, watched dirs only) with
  create/modify/remove/rename events and a Failed event on root loss.
  notify is CC0-1.0 and fails cargo deny; owner decision pending.
- read_text with a 32 MiB cap, UTF-8 + BOM, typed InvalidUtf8 and
  UnsupportedEncoding; write_atomic via temp file + rename, keeping
  permissions and refusing read-only files.
- 28 tests on temp dirs (30 on Unix: permission and symlink write tests).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 19:24:02 +02:00

4 KiB
Raw Blame History

Target-app parity

Status: baseline after M0, no PHP feature ships · Last updated: 2026-10-14 · 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/.

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.

Feature areas

Area Weight Score Missing Hours (one agent) Evidence
Editor core 12 0% everything ~120 (est.) —
Project view, VFS 6 0% everything visible: project tree, file commands, native file watching (only polling so far) ~38 (est.) lutra-vfs (M1.2): lazy sorted listing, ignore rules (.gitignore, .ignore, info/exclude, global excludes, Lutra defaults), polling watcher, capped UTF-8 reads, atomic writes; 28 tests on temp dirs (crates/vfs/tests)
Navigation 10 0% everything ~120 (est.) —
Search and replace 6 0% everything ~80 (est.) —
Code completion 10 0% everything ~250 (est.) —
Inspections and quick-fixes 8 0% everything ~300 (est.) —
Refactoring 7 0% everything ~250 (est.) —
Code style and formatting 4 0% everything ~120 (est.) —
Git 8 0% everything ~150 (est.) —
Terminal 3 0% everything ~30 (est.) —
Run configurations 2 0% everything ~50 (est.) —
Debugger 5 0% everything ~120 (est.) —
Testing 4 0% everything ~80 (est.) —
Composer and interpreters 2 0% everything ~50 (est.) —
Frameworks 5 0% everything ~300 (est.) —
Database tools 3 0% everything ~250 (est.) —
HTTP client 1 0% everything ~60 (est.) —
Web languages 2 0% everything ~200 (est.) —
Docker and remote 1 0% everything ~120 (est.) —
Settings, keymaps, themes 1 0% settings UI, keymaps, theme switching (theme tokens exist in lutra_engine::theme) ~60 (est.) —
Plug-ins 0.5 0% everything ~120 (est.) —
AI features 0.5 0% everything ~60 (est.) —

Sum: about 2,930 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.

Weights were reviewed at the end of M0 and kept: nothing built so far gives a reason to change them.

What ships (M0, 2026-10-14)

No PHP feature. The foundation, verified on Windows 11:

  • cargo xtask ci passes all 13 steps (fmt, clippy with no-panic lints, tests, lints self-test, layers, assets, clean-room, cargo-deny licences, pnpm install, ESLint, vue-tsc, Vitest, frontend licences).
  • Commands app.about and app.quit with unit tests; a panicking command is caught by the guard (crates/engine/src/engine.rs tests).
  • Control channel: app.ping, engine.execute, engine.listCommands, ui.screenshot, with proptests and a TCP integration test (crates/control), and checked against the running app.
  • The desktop window opens themed from Rust tokens and shows the product name and version that the frontend gets from app.about over IPC.

Revision history

Date Change Summary
2026-10-14 minor Project view evidence: lutra-vfs (M1.2), score unchanged
2026-10-14 minor Hours per area, weights reviewed, M0 evidence
2026-10-13 major Baseline