0.9.0

DOC character-run handles can now set directFontSizePoints when an existing exclusive sprmCHps operand is understood and safe to replace. Values must be finite primitive numbers from 1 to 1638 points in exact half-point increments. The writer replaces only the existing two-byte operand, preserving all other bytes. Inherited/missing size slots, shared blobs, opaque formatting contexts, unsafe ownership and stale handles refuse explicitly. It does not append formatting records or resolve inherited styles.

The bounds follow the Microsoft MS-DOC character-properties specification. Nine independent native Word 16 comparisons cover the owned 18-point fixture, 13.5/130/1/1638-point edits, a 12-point baseline, repeated 12-to-13.5-to-12 edits and restoration to 18. Only the selected nine character sizes and their paragraph aggregate changed among the captured fields; reverse edits restore the original bytes exactly. Rendering, pagination and full DOC fidelity are not established by these comparisons.

The typed parseDoc API remains primary. VSD v11 support retains the bounded read/write scope documented in 0.8.0; native Visio fidelity remains unverified.