Lutra/docs/target-app-parity.md
danny 5dac918b14 M1.1: text buffer with UTF-16 positions, edit batches and line endings
lutra-text gets Buffer on a ropey rope: byte/char/UTF-16/line counts,
byte offset <-> (line, column) in UTF-16 code units or chars, absolute
UTF-16 offsets, atomic Edit batches in LSP TextEdit[] semantics, and
\n / \r\n / \r detection with a keep-the-file's-ending save policy.
All conversions return TextError instead of panicking.

ropey 1.6.1 (MIT) without unicode_lines, so only the LSP/CodeMirror
line breaks split lines. proptest moves into workspace deps.

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

4.5 KiB
Raw Blame History

Target-app parity

Status: M1 in progress (text buffer landed), 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 user-visible; only the engine text buffer exists ~120 (est.) crates/text: rope buffer, positions, edits (M1.1, unit tests + proptests)
Project view, VFS 6 0% everything ~40 (est.) —
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.

What ships (M1, in progress)

Nothing user-visible yet, so every score stays 0%.

  • M1.1 text buffer (crates/text): Buffer on a ropey rope with byte, char, UTF-16 and line counts; byte offset to line and column in UTF-16 code units or chars and back, all fallible (out of range, inside a character, inside a CRLF, inside a surrogate pair); atomic Edit batches in LSP TextEdit[] semantics that reject reversed, out-of-range and overlapping ranges; / / detection with a keep-the-file's-ending save policy. 23 unit tests and 6 proptests (round-trips on emoji, ZWJ sequences, CJK and combining marks; random edit batches checked against a String model, never panicking).

Revision history

Date Change Summary
2026-10-14 minor M1.1 text buffer evidence (Editor core, score unchanged)
2026-10-14 minor Hours per area, weights reviewed, M0 evidence
2026-10-13 major Baseline