Lutra/docs/target-app-parity.md
danny 3f190a635e M1.2: native file watching via notify
- notify 8.2.0 (CC0-1.0) behind the existing Watcher API, allowed by a
  crate-scoped [[licenses.exceptions]] entry in deny.toml (owner
  decision 2026-10-14, noted in AGENTS.md and NOTICE).
- Native notifications only mark directories dirty; after 100 ms of
  quiet (at most 10 intervals) dirty dirs are rescanned and diffed, so
  events, debouncing and rename pairing match the polling backend.
- Polling stays as fallback when the native watcher cannot start, and
  per directory when a native watch is refused. Lost events or watcher
  errors trigger a full rescan; root loss is checked on every tick.
- Additive API: WatchOptions::backend (Auto, Polling) and
  Watcher::is_native.
- Watch tests run on both backends (34 vfs tests on Windows).

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

4.1 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 ~37 (est.) lutra-vfs (M1.2): lazy sorted listing, ignore rules (.gitignore, .ignore, info/exclude, global excludes, Lutra defaults), native file watching via notify with a polling fallback, capped UTF-8 reads, atomic writes; 34 tests on temp dirs, watcher tests run on both backends (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: native file watching (M1.2b), score unchanged
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