release: CHANGELOG stops at 1.5.0, changesets are unconsumed, and 1.9.8 has no tag or release #70

Observation on main faf1d88

• package.json and npm are at 1.9.8. CHANGELOG.md has an Unreleased block followed directly by 1.5.0; there are no entries for 1.6.0 through 1.9.8.
• .changeset/ holds four pending changesets (agent-reliability-and-batch-render, converter-sandbox-runtime, native-office-review, safe-office-data-and-review), so releases are being cut without changeset version consuming them.
• Git tags run through v1.9.7; there is no v1.9.8 tag.
• GitHub Releases exist for 1.9.1, 1.9.2, 1.9.4, 1.9.6 and 1.9.7. 1.9.3, 1.9.5 and 1.9.8 have none.
• skills/deckuse/SKILL.md frontmatter still has metadata.version: '1.5.0'.
• The repository description is "A local-first structural editing engine for PPTX files." and the topics are agent, deck, office, pptx. DOCX support and the coding-agent focus are not reflected.

Impact

Users and agents cannot tell what changed between the version they have and the latest one. The README tells agents to install a skill "from the release tag matching the npm package version", which is not possible for 1.9.8.

Acceptance

• scripts/release.sh consumes changesets (or the changeset flow is dropped and the CHANGELOG is written another way) so every published version has an entry.
• CHANGELOG is backfilled for 1.6.0–1.9.8, at least at one line per release.
• Every published npm version has a matching git tag and GitHub Release; the release script fails if the tag is missing.
• The skill metadata version is generated from package.json or removed.
• Repository description and topics mention DOCX and agent use.