feat(v0.10.0): plan verification badge in walkthrough header (Tier A)

[ohgeeceee]

Summary

v0.10.0 — Plan verification badge (Tier A frontend + data loader). Completes the data contract PR #5 installed: the meta.verified marker in community/testplans/*.toml now flows all the way to the walkthrough header as a badge.

This PR is Tier A — frontend + an additive change to the non-protected testplans.rs data loader. No protected paths (transport/protocol/commands.rs) touched.

What it does

• The walkthrough panel header now shows a badge based on each plan's meta.verified:
  • NEEDS VERIFICATION (amber) — the default "needs verification" state every plan ships with.
  • ✓ Verified (green) — once a real-car harness walk upgrades it (docs/validation/testplans.md).
  • No badge when the marker is absent (legacy/unknown plans).

Structure

Rust (src-tauri/src/testplans.rs) — additive:

• PlanMeta gains verified: Option<String>; TestPlan gains verified: Option<String>; to_plan threads it through. No deny_unknown_fields, so plans without the marker still parse as None.
• parse_roundtrip_maps_all_fields now asserts the marker threads through; shipped_testplans_branch_integrity and shipped_corpus_loads still green.

UI (src/js/main.js, src/index.html, src/css/app.css):

• loadTestPlan reads plan.verified and renders #walkthrough-verified; plan_verified_state() maps the TOML string to label + class. Light + dark themes, matching the existing .unverified-tag amber convention.

Verification

• cargo test --lib testplans → 5 passed (parse roundtrip, did range, shipped corpus load, case-insensitive query, branch-integrity gate).
• node --test src/js/test/*.test.cjs → 56 passed (unchanged).
• node scripts/lint-toml.js → 0 problems (35 files).
• node --check src/js/main.js → exit 0.

Files

src-tauri/src/testplans.rs   | +verified field on PlanMeta + TestPlan, threaded via to_plan; test assertion
src/js/main.js              | loadTestPlan badge render + plan_verified_state()
src/index.html              | #walkthrough-verified span in the walkthrough head
src/css/app.css             | .walkthrough-verified (light + dark, unverified/verified)
CHANGELOG.md                | 0.10.0 section

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 914ff145d7

ℹ️ 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".

[chatgpt-codex-connector]

Move badge rendering after the plan lookup

When any DTC row is clicked, this expression reads plan, but that binding exists only inside the later try block. It therefore throws ReferenceError: plan is not defined before get_test_plan is invoked and outside the error handler, causing loadTestPlan (and the surrounding Promise.all) to reject while the walkthrough remains stuck. Render the badge after the awaited plan has been retrieved.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Keep these changes unreleased until versions are bumped

Changing the heading to 0.10.0 declares these accumulated changes released, but package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json, and the application entry in Cargo.lock all still identify the product as 0.6.0 (as does the README's latest-release section). Consequently, any artifact built from this commit is still packaged and reported as 0.6.0 despite the changelog claiming 0.10.0, which can break release identification and updater version comparisons. Retain the Unreleased heading here or perform the repository's standard coordinated release-version bump.

Useful? React with 👍 / 👎.