Repository navigation
release: v5.0.1 Connection Recovery - #377
Conversation
ECC Tools / Security EvidenceCommit: Security evidence gate passed (success) No security-sensitive scanner-evidence gap detected. Mode: enforce Scanned 16 changed file(s). No missing scanner-evidence signal was detected. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy review recommended (neutral) Detected 2 PR taxonomy bucket(s): Install Manifest Integrity, CI/CD Recommendation. Scanned 16 changed file(s). Roadmap taxonomy buckets: Install Manifest IntegrityInstall manifests, plugin metadata, and shipped skills should stay synchronized with user-facing setup guidance. Signals:
Paths:
CI/CD RecommendationCI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work. Signals:
Paths:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 16 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 16 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Security EvidenceCommit: Security evidence gate passed (success) No security-sensitive scanner-evidence gap detected. Mode: enforce Scanned 16 changed file(s). No missing scanner-evidence signal was detected. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy review recommended (neutral) Detected 2 PR taxonomy bucket(s): Install Manifest Integrity, CI/CD Recommendation. Scanned 16 changed file(s). Roadmap taxonomy buckets: Install Manifest IntegrityInstall manifests, plugin metadata, and shipped skills should stay synchronized with user-facing setup guidance. Signals:
Paths:
CI/CD RecommendationCI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work. Signals:
Paths:
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 16 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 16 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
![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: 20609eb4e5
ℹ️ 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".
| {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://beemuu.com/"},{"@type":"ListItem","position":2,"name":"Press","item":"https://beemuu.com/press.html"}]} | ||
| </script> | ||
| </head><body><a class="skip-link" href="#main">Skip to content</a><header class="site-header"><a class="brand" href="/"><span class="brand-mark">B</span>BeeEmUu</a><nav><a href="/bmw-k-dcan-diagnostics.html">K+DCAN</a><a href="/bmw-enet-doip-diagnostics.html">ENET</a><a href="/bmw-fault-codes.html">Fault codes</a><a href="https://github.com/ohgeeceee/beemuu">GitHub</a></nav></header><main id="main"><section class="guide-hero"><p class="breadcrumbs"><a href="/">BeeEmUu</a> / Press</p><p class="eyebrow">Press kit</p><h1>Press kit & brand assets.</h1><p class="lede">Brand assets, project story, contact info, v5.0.0 release highlights, and the “not affiliated with BMW AG” disclaimer. For media, writers, and people writing about the project.</p><div class="guide-meta"><span>Brand assets</span><span>Updated October 2026</span><span>GPL-3.0-or-later</span></div></section><section class="v2-highlight"><h2>BeeEmUu v5.0.0 — what's new</h2><p>The chrome and theme release styles the app shell that previously fell through to browser defaults. Highlights include:</p><ul><li><strong>App-shell chrome</strong> — the status bar, session bar, log annotations and shortcut legend, byte-watch grid, diagnostics columns, traffic table, modals and export panes now carry authored rules instead of default grey.</li><li><strong>Controls themed from one source</strong> — 79 interactive elements, including the theme toggle and the profile, address, compare, import and scrubber inputs, resolve light and dark from the shared token layer.</li><li><strong>Print stays paper</strong> — the deliberately light print report surface is excluded, so documents keep their paper look under the dark theme.</li><li><strong>A visual guard</strong> — a rendered-DOM check fails the build if any chrome surface loses its rules or the dark theme paints a near-white surface.</li></ul><a class="button" href="https://github.com/ohgeeceee/beemuu/releases/tag/v5.0.0">Download v5.0.0</a></section><div class="guide-layout"><aside class="toc"><strong>On this page</strong><a href="#brand">Brand</a><a href="#story">Project story</a><a href="#v3">v5.0.0 highlights</a><a href="#contact">Contact</a><a href="#disclaimer">Disclaimer</a><a href="#license">License</a></aside><article class="article"><h2 id="brand">Brand</h2><p>The BeeEmUu wordmark is a single capital “B” in a 2-pixel border, set in the same DM Sans typeface as the rest of the site. The same wordmark is used as the “brand-mark” in the page header.</p><h3>Wordmark (SVG, white-on-dark)</h3><p>Inline SVG used by every page:</p><pre><a class="brand" href="/"> | ||
| </head><body><a class="skip-link" href="#main">Skip to content</a><header class="site-header"><a class="brand" href="/"><span class="brand-mark">B</span>BeeEmUu</a><nav><a href="/bmw-k-dcan-diagnostics.html">K+DCAN</a><a href="/bmw-enet-doip-diagnostics.html">ENET</a><a href="/bmw-fault-codes.html">Fault codes</a><a href="https://github.com/ohgeeceee/beemuu">GitHub</a></nav></header><main id="main"><section class="guide-hero"><p class="breadcrumbs"><a href="/">BeeEmUu</a> / Press</p><p class="eyebrow">Press kit</p><h1>Press kit & brand assets.</h1><p class="lede">Brand assets, project story, contact info, v5.0.1 release highlights, and the “not affiliated with BMW AG” disclaimer. For media, writers, and people writing about the project.</p><div class="guide-meta"><span>Brand assets</span><span>Updated October 2026</span><span>GPL-3.0-or-later</span></div></section><section class="v2-highlight"><h2>BeeEmUu v5.0.1 — what's new</h2><p>The chrome and theme release styles the app shell that previously fell through to browser defaults. Highlights include:</p><ul><li><strong>App-shell chrome</strong> — the status bar, session bar, log annotations and shortcut legend, byte-watch grid, diagnostics columns, traffic table, modals and export panes now carry authored rules instead of default grey.</li><li><strong>Controls themed from one source</strong> — 79 interactive elements, including the theme toggle and the profile, address, compare, import and scrubber inputs, resolve light and dark from the shared token layer.</li><li><strong>Print stays paper</strong> — the deliberately light print report surface is excluded, so documents keep their paper look under the dark theme.</li><li><strong>A visual guard</strong> — a rendered-DOM check fails the build if any chrome surface loses its rules or the dark theme paints a near-white surface.</li></ul><a class="button" href="https://github.com/ohgeeceee/beemuu/releases/tag/v5.0.1">Download v5.0.1</a></section><div class="guide-layout"><aside class="toc"><strong>On this page</strong><a href="#brand">Brand</a><a href="#story">Project story</a><a href="#v3">v5.0.1 highlights</a><a href="#contact">Contact</a><a href="#disclaimer">Disclaimer</a><a href="#license">License</a></aside><article class="article"><h2 id="brand">Brand</h2><p>The BeeEmUu wordmark is a single capital “B” in a 2-pixel border, set in the same DM Sans typeface as the rest of the site. The same wordmark is used as the “brand-mark” in the page header.</p><h3>Wordmark (SVG, white-on-dark)</h3><p>Inline SVG used by every page:</p><pre><a class="brand" href="/"> |
There was a problem hiding this comment.
For anyone using the press page to learn what is new, this section now labels and links the content as v5.0.1, but the paragraph and all four bullets still describe the app-shell chrome/theme work from v5.0.0. The v5.0.1 changelog and release notes instead identify connection recovery and stale Live Gauges handling, so the page misattributes the previous release's features and omits the current ones; update the highlights or leave this section explicitly labeled v5.0.0.
Useful? React with 👍 / 👎.
| The current source version is **v5.0.1 — "Connection Recovery"** (2026-10-19). | ||
| It adds connection retry guidance and stale-reading handling to the v5.0.0 platform. |
There was a problem hiding this comment.
After this line declares v5.0.1 current, readers following the immediately preceding canonical-roadmap link still see ROADMAP.md report Current source version: v5.0.0 (2026-10-15). This leaves the repository's stated source version inconsistent; update the roadmap baseline and include it in the release stamping/version-surface check.
AGENTS.md reference: AGENTS.md:L163-L165
Useful? React with 👍 / 👎.
| @@ -0,0 +1,36 @@ | |||
| # BeeEmUu v5.0.1 — Connection Recovery | |||
There was a problem hiding this comment.
For tag-triggered releases, .github/workflows/release.yml lines 87–90 supplies a hard-coded boilerplate releaseBody, and a repository-wide search finds no workflow or script that reads this newly added file. Consequently the v5.0.1 GitHub release linked from the homepage and press page will not display these recovery details, validation caveats, or rollback instructions; wire this file into the release action or otherwise use its contents as the release body.
Useful? React with 👍 / 👎.
| ("frontend/index.html", 'href="/downloads.html"'), | ||
| ("frontend/index.html", "Choose your installer"), |
There was a problem hiding this comment.
On future releases these two independent substring checks can pass without any working installer CTA: frontend/index.html already contains several /downloads.html navigation links and a separate second “Choose your installer” button, so a broken or removed hero CTA still satisfies both needles elsewhere in the file. Since this verifier gates the automated release-stamp commit, match the label and href within the same anchor (or parse the HTML) so it actually detects the regression it claims to check.
Useful? React with 👍 / 👎.
Tier C — release and production rollout explicitly authorized by the owner in chat ("push to production").
Prepare a patch release containing #374 and #375. Synchronize the app manifests, lockfiles, README release badge, changelog and generated site version surfaces to 5.0.1; add release notes and rollback instructions. Fix the release-stamp verifier to check the existing install-center CTA instead of an obsolete versioned download button.
Validation: JavaScript 1,136 passed / 1 existing skip; Python 275 passed and 33 subtests passed; version stamp self-verification and GitHub Pages artifact checks passed; git diff --check passed. Implementation commit #375 has all GitHub checks passing, including both Rust suites and Rust security analysis. Local Rust testing remains unavailable because dbus-1 development libraries are missing.
Rollout: after checks, build Windows/Linux installers from this exact source through the existing Release workflow, verify attached assets before publication, then deploy GitHub Pages and check the public download center. No backend or database change is needed. Current live site is GitHub Pages; the documented API hostname does not resolve, so this release does not claim to restore hosted API service. Preserve the previous installers for rollback.