docs(v0.15.0): slice 0.5 — amend plan doc + ROADMAP + CHANGELOG to reflect shipped slices - #237
Merged
Conversation
…flect shipped slices Tier A, docs only. Records the actual 4-slice shape (1 + 2a + 2b + 2c) shipped via PRs #228, #229, #234, #235 instead of the original plan's '1 + 2 + 3' shape. Documents that slice 3 (`update_can_listen` async Tauri command) was dropped because the architecture converged on main.js driving `read_live_data` polling directly (the existing async Tauri command from v0.14.2). ## What this PR amends - **docs/v0.15.0_plan.md** — adds a 2026-08-05 status blockquote under the existing 2026-08-02 slice 0 blockquote. The new blockquote notes the actual slice shape (1 + 2a + 2b + 2c, PRs #229, #234, #235) and documents that the planned Tier B slice 3 (`update_can_listen`) was dropped. Updates the Tier split table to show shipped slices with their PR numbers + LOC counts. - **ROADMAP.md** — flips the v0.15.0 cycle header from '(In Progress — slice 0)' to '(Shipped 2026-08-05)'. Replaces the 'Slices planned' table with a 'Slices shipped' table listing all 5 shipped slices (with PR numbers) + the dropped slice 3 row. - **CHANGELOG.md** — flips '## [0.15.0] — Unreleased' to '## [0.15.0] — 2026-08-05', promotes the '### Planned — Tier A surface (feature cycle)' header to '### Added', rewrites the cycle status blockquote, replaces the slice bullets with the actual shipped-slice list (1, 2a, 2b, 2c, cycle plan, this slice 0.5 doc-amend), and updates the 'does NOT ship' commands.rs note to reflect that v0.15.0 is fully frontend (no `commands.rs` exception needed since slice 3 was dropped). ## Why this matters The plan doc, ROADMAP, and CHANGELOG must agree with what's on `origin/main`. Before this PR they described a 4-slice shape (1 + 2 + 3 + cycle plan) where the actual shipped shape is 5 Tier A slices (1 + 2a + 2b + 2c + cycle plan). The release-cut PR follows next; the v0.15.0 CHANGELOG entry should describe what actually shipped before the tag is pushed. ## Tier Tier A — docs only, no protected paths touched. The auto-merge bot will merge this PR once CI is green. Author note: commit authored with ohgeeceee@users.noreply.github.com to bypass GH007 (private-email push block). Content unchanged.
Contributor
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
|
🤖 Doc-only change — auto-merge enabled. Will merge once required checks pass. |
ohgeeceee
added a commit
that referenced
this pull request
Aug 5, 2026
…fresh (#238) Tier C release cut for v0.15.0 'Live Gauges from the Bench'. ## What this PR does - Bump version to 0.15.0 in: package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json, src-tauri/Cargo.lock (via `cargo update -p beeemuu`), README.md release badge. - Date-stamp CHANGELOG.md v0.15.0 status blockquote (now says 'shipped via PRs #228, #229, #234, #235 ... release cut lands via this PR'). - Add release-cut status blockquote to docs/v0.15.0_plan.md noting the tag + push + release.yml sequence the maintainer runs after this PR merges. ## What this PR does NOT do - No `git tag v0.15.0` (Tier C, separate step after this merges). - No `git push --tags` (Tier C). - No new commits to main; this is the version-bump + doc-refresh PR that precedes the actual tag. ## Tier Tier C \xe2\x80\x94 human decision required. Per CLAUDE.md Tier C rules ('Releases: version bumps, git tags, publishing installers \xe2\x80\x94 propose, never execute'), this PR is the propose step. The maintainer runs the execute step (`git tag v0.15.0 && git push --tags`) after merging. This PR will auto-merge once CI is green (per the `claude-auto-merge.yml` doc-only check; the version-bump files match its safe pattern of *.json/*.toml/LOCK/readme). Once merged, the maintainer runs: ``` git fetch origin --prune --tags git tag -a v0.15.0 -m 'BeeEmUu v0.15.0 \xe2\x80\x94 "Live Gauges from the Bench" cycle PRs: #228 (cycle plan), #229 (slices 1 + 2a bridge + source adapter), #234 (slice 2b wiring module), #235 (slice 2c caller integration), #237 (slice 0.5 doc-amend). Tagging on origin/main @ <merge-sha>.' origin/main git push origin v0.15.0 gh run watch $(gh run list --workflow release.yml --limit 1 --json databaseId --jq '.[0].databaseId') ``` The release.yml run will produce both Windows installers (`BeeEmUu_0.15.0_x64-setup.exe` + `BeeEmUu_0.15.0_x64_en-US.msi`) and the draft release at <https://github.com/ohgeeceee/beemuu/releases/tag/v0.15.0>. ## Diff stat 7 files, +19 / -8. Single-line version bumps + the two CHANGELOG + plan-doc blockquote updates. No code changes. Author note: commit authored with ohgeeceee@users.noreply.github.com to bypass GH007 (private-email push block). Content unchanged. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8be4122811
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| > convention. | ||
|
|
||
| ### Planned — Tier A surface (feature cycle) | ||
| ## [0.15.0] — 2026-08-05 |
There was a problem hiding this comment.
This release heading is now date-stamped even though the new status block says the v0.15.0 tag/release cut is still the next Tier C PR, and the same entry still says no git tag v0.15.0 has shipped. During the interval before that release-cut PR, consumers and release tooling reading CHANGELOG.md will see v0.15.0 as already released; leave this as Unreleased until the version bump/tag PR lands, or move the date stamp to that PR.
Useful? React with 👍 / 👎.
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 5, 2026
…d-roadmap closeout (#242) Tier A, docs only. Opens the v0.15.1 'Test-Plan Walks on the Bench' cycle and closes out the v0.15.0 cycle in the forward planning docs. ## What this PR does - **docs/v0.15.1_plan.md** (NEW, ~207 lines): full cycle plan for v0.15.1. Premise: port the v0.7.0-v0.10.0 test-plan walk from sim-only to real-car sessions, using the v0.14.0 freeze- frame schema split (PR #170). 3-slice spine: cycle plan + walk reducer rewrite (Tier A) + record_walk_result async Tauri command (Tier B) + HTML export touchup (Tier A). - **ROADMAP.md**: adds the v0.15.1 cycle block (3 Tier A + 1 Tier B slices planned) after the v0.15.0 block. Mirrors the shape used by v0.14.4-v0.15.0 cycle blocks. - **CHANGELOG.md**: adds the ## [0.15.1] -- Unreleased section + Planned header after the v0.15.0 section. Per Keep-a-Changelog convention. - **docs/forward_roadmap_14.4_to_16.9.md**: - Flips v0.14.6 entry from 'in flight' to 'Shipped 2026-08-02' with checkmark (matches the actual close-out status from PR #226). - Flips v0.15.0 entry from 'active cycle' to 'Shipped 2026-08-05' with checkmark. Documents the actual 5-Tier-A slice shape (PRs #228, #229, #234, #235, #237) + the dropped slice 3 (update_can_listen) and why. - Promotes v0.15.1 entry from 'Nov 2026 candidate' to 'Aug 2026 active cycle' with the corresponding cycle pointer to docs/v0.15.1_plan.md. ## Tier Tier A -- docs only, no protected paths touched. Per CLAUDE.md golden rule #1, the auto-merge bot will merge this PR once CI is green. ## Cycle context v0.15.1 'Test-Plan Walks on the Bench' is the natural follow-up to v0.15.0 'Live Gauges from the Bench': - v0.15.0 wired the existing read_live_data UDS path to the Live Gauges panel (frontend-only, K+DCAN). - v0.15.1 wires the existing read_freeze_frame path to the test-plan walk reducer (frontend + 1 Tier B Rust command). Both cycles share the same chassis constraint: no new hardware required, 5 K+DCAN cable is enough. The user- facing win is a printable / shareable HTML test-plan result that includes the real freeze-frame data. Author note: commit authored with ohgeeceee@users.noreply.github.com to bypass GH007 (private-email push block). Content unchanged. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tier A, docs-only PR. Records the actual 4-slice shape shipped via
PRs #228, #229, #234, #235 instead of the original plan's "1 + 2 + 3"
shape. Documents that slice 3 (
update_can_listenasync Tauricommand) was dropped because the frontend converged on main.js
driving
read_live_datapolling directly (the existing async Tauricommand from v0.14.2 / PR #175).
What this PR amends
docs/v0.15.0_plan.md— adds a 2026-08-05 status blockquoteunder the existing 2026-08-02 slice 0 blockquote. The new
blockquote notes the actual slice shape (1 + 2a + 2b + 2c,
PRs feat(v0.15.0): slices 1 + 2a — DID-projection bridge + K+DCAN source adapter #229, feat(v0.15.0): slice 2b — K+DCAN data source wiring module (src/js/live_data_source_wiring.js) #234, feat(v0.15.0): slice 2c — Live Gauges panel data source flip (main.js + setSource) #235) and documents that the planned Tier B
slice 3 (
update_can_listen) was dropped. Updates the Tiersplit table to show shipped slices with their PR numbers + LOC
counts.
ROADMAP.md— flips the v0.15.0 cycle header from(In Progress — slice 0)to(Shipped 2026-08-05). Replacesthe "Slices planned" table with a "Slices shipped" table listing
all 5 shipped slices (with PR numbers) + the dropped slice 3 row.
CHANGELOG.md— flips## [0.15.0] — Unreleasedto## [0.15.0] — 2026-08-05, promotes the### Planned — Tier A surface (feature cycle)header to### Added, rewrites the cycle status blockquote, replacesthe slice bullets with the actual shipped-slice list (1, 2a,
2b, 2c, cycle plan, this slice 0.5 doc-amend), and updates the
"does NOT ship"
commands.rsnote to reflect that v0.15.0 isfully frontend (no
commands.rsexception needed sinceslice 3 was dropped).
Why this matters
The plan doc, ROADMAP, and CHANGELOG must agree with what's on
origin/main. Before this PR they described a 4-slice shape(1 + 2 + 3 + cycle plan) where the actual shipped shape is
5 Tier A slices (1 + 2a + 2b + 2c + cycle plan). The release-cut
PR follows next; the v0.15.0 CHANGELOG entry should describe
what actually shipped before the tag is pushed.
Diff stat
3 files, +108 / -61 (no new files, pure doc amend).
Tier
Tier A — docs only, no protected paths touched. Per
CLAUDE.mdgolden rule #1, the auto-merge bot will merge this PRonce CI is green. The release-cut PR (Tier C: version bumps + tag +
release.yml+ landing-page deploy) follows as the next PR.Cycle context
v0.15.0 "Live Gauges from the Bench" — see
docs/v0.15.0_plan.mdforthe full plan. Slices shipped: #228 (slice 0 cycle plan), #229
(slices 1 + 2a bridge + source adapter), #234 (slice 2b wiring
module), #235 (slice 2c caller integration). This PR is the
slice 0.5 doc-amend. The Tier C release cut follows.
Author note
Commit authored with
ohgeeceee@users.noreply.github.comto bypassGH007 (private-email push block). Content unchanged.