Repository navigation
docs: establish an accurate v5 baseline and next update sequence - #374
Conversation
ECC Tools / Security EvidenceCommit: Security evidence gate passed (success) No security-sensitive scanner-evidence gap detected. Mode: enforce Scanned 6 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 clear (success) Scanned 6 changed file(s). No taxonomy bucket signals were detected. Scanned 6 changed file(s). No PR taxonomy bucket signals were 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 / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 6 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 6 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. |
|
🤖 Doc-only change — auto-merge enabled. Will merge once required checks pass. |
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.
The README still names v3.0.0 as current, and the roadmap can imply installed plugins already receive capability-guarded vehicle access. This reconciles the source baseline to v5.0.0, documents the gap between the decision module and installed runtime, records the audited absence of v5 installer assets, and adds the next ten update cycles with acceptance criteria.
Validation: frontend suite 1,132 passed, 1 pre-existing skip; Python 275 passed and 33 subtests passed; git diff --check passed. Rust tests were attempted locally but this host lacks the dbus-1 development library; the main Rust CI job passes. All remaining CI checks must complete successfully before merge. Documentation only; no release, production or hardware behavior changed.