Fix legacy signer continuity and release v0.10.2

[Ghost-Frame]

Summary

• treat optional legacy_author data as mutable presentation metadata for unlinked historical versions
• retain request identity, archive hash, Ed25519 signature, exact manifest signer-key, and local TOFU enforcement
• document the compatibility contract
• bump the CLI and MCP release versions together to 0.10.2

Production acceptance

A fresh isolated restore of the production catalog was tested with the rebuilt 0.10.2 CLI. All 45 active versions installed, accessibility-engineer activated, and 42 persona names were listed. The released 0.10.1 CLI had failed 19 of those versions after the legacy profile rename.

Validation

• cargo fmt --all -- --check
• cargo clippy --locked --workspace --all-targets -- -D warnings
• cargo test --locked --workspace
• cargo check --locked -p frameshift-cli -p frameshift-mcp -p frameshift-daemon --all-targets --features embeddings
• backup script integration tests
• Wiki canonical-source validation
• fresh restored-catalog install matrix: 45 passed, 0 failed

This remains an early-access prerelease while unsigned Windows early access is enabled.