feat: release 0.2.0 with the console labels at run time, the card-header action and the editor's mode

[rubentalstra]

What changed and why

The 0.2.0 release: the workspace version, the [0.2.0] changelog section and the lock. It ships #126 (milestone v0.2.0: #114, #122, #123) with #116 and #119, which were unreleased since 0.1.7. The release breaks the public API, so it moves the minor version; the changelog section names what each console changes, and the four consoles move to =0.2.0 together in their rollout pull requests.

Screens checked

• Overview, every brand, 1440 and 390, light and dark: the new "Recent files" panel with its "All files" card action, the words and the arrow a tight space apart, in the accent; the list rows now keep the panel's inline padding (the first capture drew them flush with the card edge, fixed in feat: take every console label at run time, one card-header action and the editor's mode in its header #126). Hover and focus of the action are captured by tests/it/states.rs.
• Forms, every brand, 1440 and 390, light and dark: the "Editor headers" card shows "New mapping file" and "Edit synthetic-007.model.yml", the trail's last crumb matching the heading. The first capture drew the edited title in the code face and left a band under each header inside its well; both fixed in feat: take every console label at run time, one card-header action and the editor's mode in its header #126 (the title is a sentence in the body face, a header in a well drops its bottom margin).
• Every other page: the words are unchanged; the gallery's own strings now come from its catalog, and the pseudo-locale stretches them with the library's.
• The 168 refreshed images (every version mark, the overview and the forms page) are in this pull request, captured by its CI at 0.2.0.

Closes no issue: the milestone's issues closed with #126 and #125.

Licensing of contributions

• I accept the terms in CONTRIBUTING.md § Licensing of contributions: I have the right to submit this work, I license it under the project licence of the version it lands in, and I grant the Licensor the relicensing right stated there.

Checklist

• Accessibility decisions cite WCAG 2.2, WAI-ARIA 1.2 or the Authoring Practices, not memory and not another library.
• Rust gates pass: cargo fmt --all --check, cargo clippy --workspace --all-targets -- -D warnings, the wasm32 clippy runs, cargo nextest run --workspace --locked, cargo doc with RUSTDOCFLAGS=-D warnings, and cargo deny check.
• A visible change refreshed the gallery screenshots, and I looked at every image it changed.
• A new or changed component was compared with the four consoles' versions (docs/qa/), and the best one on its merits was restyled to the library's tokens; the winner and the reason are stated below.
• Its interactive states (pointer, focus, open, each tone) are captured by tests/it/states.rs in every brand, light and dark.
• A release pull request says, per screen and per state, what was checked and what was fixed.
• Shell and workflow files are clean: shellcheck --severity=style, actionlint, zizmor --min-severity=low .github/.
• CHANGELOG.md has an [Unreleased] entry, if a console sees the change.
• No patient data in a fixture, test, gallery row or example.
• Every commit is signed.
• No AI or assistant attribution anywhere in the commits or this PR.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud