chore(lsp): mark ORCA readiness from runtime evidence

[newtontech]

Summary

• mark ORCA diagnostic readiness as partial with passing agent CLI smoke after [ORCA] Backend runtime/fix-preview slice for input/output diagnostics orca-lsp#94
• update the compatibility matrix to ORCA 0.5.5
• document that ORCA closed-loop repair previews and log diagnostics are wired, while exhaustive version/rule coverage remains open

Test Plan

• npm run typecheck
• npm run test:unit -- --coverage=false --runTestsByPath tests/unit/lsp/registry.test.ts tests/unit/lsp/bohriumRegistryAlignment.test.ts
• npm run lsp:check-family -- --strict --report-path /tmp/lsp-family-report-20260615-007-orca-readiness-latest.json
• npm run lsp:check-latest -- --fail-on-drift
• npm run lsp:check-bohrium-registry -- --strict --bohrium-registry /Users/yhm/Desktop/code/.worktrees-lsp-latest/bohrium_skills/bohrium_skills/lsp-skills/references/lsp_backends.yaml

No-test justification

Registry metadata-only readiness update; existing registry and Bohrium alignment tests cover the contract, and no new runtime behavior or parser path was added in OpenQC.

Fixes #209
Refs newtontech/orca-lsp#92
Refs newtontech/orca-lsp#94