In progress
v0.14.4 shipped on 2026-07-31 (52 unit tests for story generation and anonymisation, CLAUDE.md hardware-and-timing invariants refresh, ROADMAP historical audit, CI workflow fix for missing Tauri Linux system dependencies). The version-cut PR is the next Tier C step.
What’s open right now
- Live CAN transport + Tauri commands (Tier B, gated behind OBDLink SX testing on a real E46). Adds
transport/can_listener.rswithListenerMode::{Simulator, OBDLinkSx}and three async commands. The desktop panel’s hardware source flips from “no frames” to “real frames” with no frontend change once this lands. - ENET/DoIP UDP discovery (still honestly not implemented). The CLAUDE.md v0.14.4 refresh specifically preserves this as an open item — it was previously marked “shipped” but the actual broadcast-discovery code path is not in the tree.
- Real-car harness verification (ongoing community work). The
docs/validation/directory carries per-engine verification harnesses; reports from owners feed the verification status of each profile parameter.
Recently shipped
The project ships small, well-bounded cycles of 3 to 5 PRs each. Each cycle has a plan doc under docs/vX.Y.Z_plan.md and ships as a tagged release. The full history lives on the changelog.
v0.14.4 — Story coverage (shipped 2026-07-31)
52 unit tests for the diagnostic story generator and anonymiser. CLAUDE.md invariants refreshed with citations to live source. ROADMAP v0.3.0 historical section audited. CI workflow repaired for Tauri Linux system dependencies.
v0.14.3 — Finish the bench (shipped 2026-07-30)
Three new decoders (fuel rate L/h, engine runtime, fuel rate g/s) wired to N62 profile entries. Per-PID NRC backend + frontend that surfaces unsupported readings without short-circuiting the whole sweep. Remove-from-profile UI for individual PIDs.
v0.14.2 — Live data on the bench (shipped 2026-07-29)
N62 profile enriched with verified 0x5C oil-temp PID. Live Data panel UX polish (polling-rate selector, per-gauge peak tracking, snapshot CSV). N62 / E70 X5 4.8i bench-verification harness doc published.
v0.14.1 — Tauri 2 dialog fix (shipped 2026-07-27)
Replaced window.confirm() with tauri-plugin-dialog's ask() in the webview (Tauri 2 auto-dismissed confirm() on some builds). Simulator regenerate-on-identify models a real car re-detecting faults on a fresh ignition cycle.
v0.14.0 — Live CAN (Tier A shipped 2026-07-25)
Live Gauges panel in the desktop app (6 gauges: RPM, coolant, oil temp, vehicle speed, battery voltage, throttle). Pure JS CAN broadcast decoders for the 6 known E-series broadcast IDs. JS-side simulator broadcast personality. Live Gauges panel mirrored to beemuu.com as a self-contained widget. Real-car verification harness doc.
Earlier
v0.13.0 (per-target KWP response deadline) · v0.12.0 (DTC history commands + recurring-DTC callout) · v0.11.0 (export charts as PNG) · v0.10.0 (plan verification badge) · v0.9.0 (Guided Fault Finding: 11 grounded test plans) · v0.8.0 (community TOML parse gate, B48/S58/N57 profiles) · v0.7.0 (theme toggle, workspace persistence) · v0.6.0 (OBD-II PID auto-discovery) · v0.5.0 (Ground Truth: real-car validation harness) · v0.4.0 (Tuner Friendly: u8_enum decoder). Full history on the changelog.
Ready to claim
The repo carries a "Ready to Claim" list of well-scoped items marked with the 🟢 label. Contributors can open a PR against any of those. The list is maintained by the project maintainers in ROADMAP.md.
Examples of typical ready-to-claim items:
- Add a new engine profile (TOML contribution; schema in
community/profiles/README.md). - Add a new DTC to the catalog (
backend/seed_bmw*.py; cross-checked against the existing DTC index). - Improve the per-engine verification harness doc (
docs/validation/<engine>-real-car.md). - Add a new community opinion (
community/opinions/<code>.toml; schema documented). - Translate an existing guide to a new language (the landing site stays English-only for now).
Open a PR, link the relevant issue, run cargo test + pytest backend/tests/ -q + node --test on the JS suites, and request review. The PR description should call out any protected-path changes at the top.
Backlog
The longer-term backlog lives in the project ROADMAP.md. Items currently in the “backlog — nice to have” bucket include adaptive drift tracker, tuning fingerprint detector, BLE / WiFi adapters, mobile companion app, and the proposed read-only USB OBDLink over WiFi. These are aspirational; the project commits to them only when they reach a cycle’s plan doc.
How cycles work
Each cycle follows a consistent shape:
- Cycle plan PR. A markdown plan document under
docs/vX.Y.Z_plan.mdlands first as a Tier A PR. This is the public negotiation step: contributors weigh in on scope before code lands. - Slice PRs. The cycle’s work ships as 3 to 5 small PRs. Each is independently reviewable. PRs are flagged at the top of the description by tier (A, B, or C) and by which protected paths they touch.
- Version bump PR. After the slice PRs merge, a single PR bumps the version surface (
Cargo.toml,tauri.conf.json,package.json, README badge). The CHANGELOG.md section lands in this PR with all the per-PR notes. - Git tag + release. Pushing the
vX.Y.Ztag triggers the GitHub Actions release workflow, which builds the Windows installer and publishes the draft release.
Tier A is auto-merge eligible for docs, frontend, community data and tests. Tier B (transport, protocol, commands.rs) requires human review. Tier C (release cuts, deploys, nginx changes) is always a human decision.
Roadmap questions
What is in progress right now?
v0.14.4 shipped on 2026-07-31. The next step is the version-cut PR + git tag (Tier C). The v0.14.5 cycle is the next planned iteration.
What is ready to claim?
The ROADMAP.md Ready to Claim list (🟢). Typical items: new engine profiles, new DTCs, verification harnesses, community opinions.
Where is the canonical roadmap?
github.com/ohgeeceee/beemuu/blob/main/ROADMAP.md
How are cycles structured?
Cycle plan PR → 3-5 slice PRs → version-bump PR → git tag → installer build. Tier A auto-merges; Tier B needs human review; Tier C is a human decision.