v0.14.5 — Open & committed.

Candidate slices

Items the maintainers are considering for v0.14.5. None of these are committed; the final list lands in docs/v0.14.5_plan.md when the cycle is opened.

• ENET/DoIP UDP broadcast discovery — the long-standing Tier B item preserved in the v0.14.4 CLAUDE.md refresh. Adding the UDP broadcast + response handling on port 13400 would unblock the DoIP path for owners who don’t have a router.
• More DTC catalog coverage — P2002/P2003 (DPF), P0401/P0402 (EGR), and the rest of the P-codes in the catalog.
• Dashboard improvements — GitHub releases feed, uptime stats, the public /api/release-info endpoint.
• More engine profiles — S65 (V8 M3), S62 (V8 M5), N62 TU variants.
• Per-ECU freeze-frame schemas — extend the freeze/ directory to cover every target address Beemuu probes.

Open questions

For each candidate slice, the maintainers need to decide:

1. Is it well-scoped?

   Some slices are well-scoped (add a DID, add a decoder) and ship in a single PR. Others are open-ended (a real-car validation harness) and need a maintainer commitment before the cycle opens.

2. Is it Tier A, B, or C?

   Tier A (docs, community TOML, frontend, tests) auto-merges. Tier B (transport, protocol, commands.rs) needs human review. Tier C (release cuts, deploys) is always a human decision.

3. Does it need a real-car validation report?

   If the slice changes how Beemuu talks to a car, the change lands unverified. A subsequent harness report in docs/validation/ flips the label.

Contribute

If you have a slice in mind, open a PR against main with a description of what you’d add. The maintainers will either merge it directly (Tier A) or roll it into the next cycle’s plan doc.

FAQ