[codex] establish release baseline and routed conversion planning

[Vantalens]

Summary

• align the Windows desktop release baseline with version 2.2.0 and validate MSI/NSIS configuration
• surface routed conversion temperatures and forced warnings in the quality model, including the Markdown raw-HTML export regression fix
• revise the development roadmap around P8-A visibility versus P8-B executable mapper work, with a research-backed design and implementation plan

Context

The current conversion registry exposes route-loss information but does not yet execute cross-model mappers. The new P8-B planning documents keep that distinction explicit, prioritize SemanticDoc <-> WorkbookModel execution, and avoid presenting PPTX/OFD placeholder capability as fidelity-preserving conversion.

Validation

• npm test
• git diff --check
• staged diff checked before commit