Capture native write rules and prepare version-specific generation checks

[swackhamer]

OxiDex needs native write rules and version-specific evidence before generated reading can expand into generated writing. This captures lossless writer declarations and actual loaded write/check procedure facts, adds an optional inactive scalar-string candidate compiler with explicit omissions, and provides an inactive raw TIFF primitive for source-resolved set/delete operations.

The release planner and official catalog capture record immutable selected identities and require old OxiDex versus old native, new OxiDex versus new native, and the native release delta. Newer parsing fixes, tags, types and formatting are authoritative; unsupported new behavior remains a visible gap.

No production writer route is activated. The 22 candidates from one native table and the 388-release catalog are source/planning counts, not generated-writing or upgrade-conformance percentages. JPEG integration, helper translation and executable version rehearsals remain follow-up work.

Validation at 16432502:

• Official two-tier regeneration reproduced all 32 artifacts with zero changes.
• Canonical Python suite: 831 passed, zero failures or skips.
• Independent source mutations cover writer identity/provenance, loader behavior, catalog completeness and plan bindings.
• The raw TIFF primitive passed 16 focused tests and independent review of directory aliasing, malformed links and append-size bounds.
• Full workspace/all-feature Cargo: 6,022 passed, zero failed, 124 ignored; full Clippy and formatting passed. Ignored tests are not counted as exercised.
• Follow-up 66f28379 preserves requested dependency bindings and rejects same-source version pairs. All 57 affected Python tests pass; a binding-only mutation changes rendered Rust and that candidate compiles. The immutable 11.78/12.64 plan still verifies.
• Runtime Rust and canonical generated artifacts are unchanged after the full gate; final documentation records the repaired scope.

Final hosted acceptance at 675a736e: all five required checks passed. The first 20-minute table-verification attempt was cancelled during native mutations; the 35-minute retry retained all steps and completed successfully.