chore: release v0.6.2

[siriusctrl]

Summary

• bump the root fmtview package, fmtview-core, the root core dependency constraint, Cargo.lock, and the npm package to 0.6.2
• move the tail-first follow attachment fix from Unreleased into dated 0.6.2 release notes
• retain an empty Unreleased section for subsequent changes

This is release preparation only. It does not create a tag, publish either crate, publish npm, or merge the branch.

Release contents

0.6.2 fixes live tail-first timelines becoming immediately detached when pretty-printed JSON breadcrumbs change the first frame's visible height. Committed appends remain attached and advance automatically.

Validation

• all root, core, dependency, lockfile, and npm version synchronization checks report 0.6.2
• release-note extraction finds a non-empty 0.6.2 section
• cargo fmt --all --check
• cargo check --workspace --all-targets --locked
• cargo clippy --workspace --all-targets --locked -- -D warnings
• cargo test --workspace --all-targets --locked: 384 passed, 0 failed, 13 ignored
• cargo metadata --locked --no-deps
• cargo publish -p fmtview-core --dry-run --locked: packaged and verified successfully, 145 files
• npm package dry-run, tarball creation, temporary installation, and shim execution: passed; tarball contains the expected five files and reports fmtview 0.6.2

The root fmtview cargo dry-run packages successfully and then stops at registry dependency resolution because crates.io currently offers fmtview-core 0.6.1/0.6.0, not 0.6.2. This is the expected core-first release boundary documented by the repository: the release workflow publishes core, waits for registry availability, and only then dry-runs/publishes the root package.

The local npm smoke used a local 0.6.2 binary to validate package shape and the shim. The tag-triggered release workflow remains responsible for supplying the static musl artifact.