fix(history): prompt to rebuild unsupported revision graphs

[forhappy]

Summary

• keep history projection strict instead of mapping legacy sidecar names
• identify the affected revision and offer a native Rebuild graph action in Codebase Evolution
• validate revision graphs before semantic diff work and route recovery through compass history rebuild

Compatibility

• immutable legacy realizations remain untouched and unreadable by the current graph projection
• users explicitly rebuild affected revisions; no backward-compatibility mapping is bundled
• the history realization schema and SQLite store format remain unchanged

Verification

• cargo test -p compass-history --locked
• cargo clippy -p compass-history --all-targets --all-features --locked -- -D warnings
• focused extension tests for rebuild recovery and history arguments
• full extension test suite: 124 tests
• npm run typecheck -w editors/vscode
• npm run build -w editors/vscode
• npm run typecheck:js
• npm run test:js (viewer 204 tests, extension 124 tests, Playwright 83 tests)
• node scripts/check_viewer_assets.mjs
• cargo fmt --all -- --check
• sh scripts/check_product_boundary.sh
• git diff --check