docs(roadmap): record implementation status per track, add Matter to LATER

[HuggeK]

The roadmap hadn't moved since #961 (2026-08-19) while a lot of tracked work landed. This PR annotates every NOW/NEXT track — and the LATER rows that moved — with a dated Status 2026-09-02 note recording what is actually implemented on master, verified against the code and its tests rather than PR titles. It also adds one new LATER direction: Matter support via matter.js.

Highlights of what the verification found:

• No NOW track fully clears its exit bar yet, but the access boundary is essentially done (missing only three named tests), and the battery-to-EV lease's control core is complete — its gaps are the missing energy budget and the Advanced-only UI.
• The energy ledger is real, the views aren't on it: daily/settlement still derive from the legacy history tables, the ledger has no cold tier, and the session receipt named in this document does not exist.
• The FTW app lane's "open work" list was fully stale — all three items shipped (on-box pairing tab, per-device revocation, plan/history/prices/EV over the protocol; push went Web-Push-with-blind-courier instead of Noise frames). The list is rewritten to say so with PR references.
• The OCPP gateway LATER row effectively delivered itself (feat(ocpp): merge master onto OCPP 1.6J + 2.0.1 for review #979, feat(ocpp): charging needs, TLS, per-charger credentials and a device row #999, fix(ocpp): first UI enable works, and the save tells the truth about restarting #1015) without a formal promotion; the note records what shipped and the one gate remnant (no lease-on-OCPP test).
• feat(mpc): Core is the champion — Python demoted to measurement shadow #1030 changed a premise: the Go DP is now the champion planner and Python a measurement shadow, which is reflected in the solar-gate and forecast-track notes.

New LATER row — Matter support (matter.js). A TypeScript matter.js process as an optional module behind a narrow versioned contract, mirroring the optimizer's rules: independent failure/update semantics, a safe unavailable state, devices entering control only as capability-declared devices with autonomous defaults, and the fabric never becoming a second commander.

@frahlg — the Matter row's placement (after Excess-PV sinks, since Matter plugs are the natural dump-load transport) and its gate wording are proposals; reorder or tighten as you see fit.

How the status notes were produced

Four parallel read-only verification passes over master at 4ba2f12, one per lane, each grounding every verdict in file/line evidence, test names, and git log PR attribution:

• NOW: access boundary + energy ledger (admission policy chain Integrate FTW P0 beta scope #602→fix(api): allow LAN owner pairing while the house password is off #995; ledger schema, sign-convention and tier tests; the missing reconciliation/cold-tier/receipt pieces).
• NOW: battery-to-EV lease + mobile/optimizer UX (lease lifecycle, 16 stop reasons, restart preflight; plan-brief/Ask-why coverage; the regex-only nature of the "viewport" tests).
• NEXT household charging tracks 1–6 (what exists vs the named modes, bands, freeze intents, fuse tree, DP fallback, deadline goals).
• NEXT forecasts 7–9 + app lane + LATER sweep (provenance-as-diagnostics, scenario bands off the control path since feat(mpc): Core is the champion — Python demoted to measurement shadow #1030, dead cycle_cost_ore_kwh wire field, shipped app items, OCPP status, open perf(web): stop dashboard render loops when their view is hidden #881/perf(state): batch energy-ledger SQL inside each control tick #882).

The notes deliberately record evidence gaps (untested behaviour) separately from unbuilt behaviour, matching the document's "exit evidence" framing.

Why the notes live in the table rather than a separate status doc

The roadmap's own rule is that a track moves only on evidence. Putting the dated status next to each exit-evidence cell keeps the claim and its current truth in one place, and the next update replaces the notes instead of growing a parallel document. A one-paragraph rule at the top says the notes are evidence, not promises.

Documentation-only change, so no changeset per the release rules. Companion PR srcfl/ftw-web#9 makes the website's "Public roadmap" chip actually link here.

🤖 Generated with Claude Code

https://claude.ai/code/session_015HBnpxLWTu2NtekaEPEDGF

[miravoss26]

Docs-only status update to the roadmap table: adds dated "Status 2026-09-02" notes to every NOW/NEXT track plus a new Matter (matter.js) LATER row, rewrites the stale FTW-app "open work" list, and updates the OCPP/passive-battery/V2X LATER rows.

• Every status claim cites concrete PR numbers as evidence, and the methodology (4 parallel read-only verification passes grounded in file/line/test evidence) is documented in a collapsible section — good practice for a claim-heavy doc change.
• No code touched, single file (docs/roadmap.md), 43+/28- lines. No secrets, no injection surface, no new deps — nothing for the security lens to flag.
• CI green (brand-cleanup, changeset-check, repo hygiene, go test+vet all pass; the code-test jobs correctly skipped for a docs-only diff).
• Consistent with the companion PR (srcfl/ftw-web#9) which links the marketing site to this same doc.

Safe to merge from my read — I didn't re-verify every linked PR's code against the specific claims (that's a large surface for a docs review), but the sourcing is unusually rigorous for a status update.

[frahlg]

Status notes belong in the table, and the ones I spot-checked against master hold: ledger rows are deleted after two years with no cold archive (EnergyLedgerRetention), cycle_cost_ore_kwh is on the wire struct but never set when core builds externalStorage, DELETE /api/app-link/devices/{id} exists, OCPP 1.6J+2.0.1 is on master, and the app pairing/revocation items really did ship.

Nit, not blocking: the lease has fifteen BatteryBoostStopReason constants, not sixteen. Matter as LATER after Excess-PV sinks is the right placement — optional module, never a second commander.