release: prepare 9.1.0 — dead-feature sweep

[devswha]

Summary

Release preparation for 9.1.0: the CHANGELOG entry and a single version sync from 9.0.0 to 9.1.0. No code changes. Policy: docs/WORKFLOW.md

No Issue: release work requested by the owner on 2026-09-26 ("릴리스까지 전부 진행").

• CHANGELOG.md: new ## 9.1.0 — 2026-09-26 section covering feat!: remove --preview/--ocr/--serve and --xliff from the CLI #951, chore: drop unread config keys and remove --jargon (Tier 1 cleanup) #952, feat!: remove Pro pack delivery (patina pack, /api/packs) #953, feat!: remove the kimi-cli backend #954, chore: remove retired and duplicate dev tooling #955, refactor(web): remove the unread playground funnel analytics #956, chore(deps): bump actions/checkout from 6 to 7 #933 and chore(deps-dev): bump eslint from 10.10.0 to 10.11.0 in the devtools group #934 (every commit in main..dev).
• Semver: minor by owner decision. The rationale line names every removed public surface that strict semver would treat as major (--preview, --ocr, --serve, --xliff, --dry-run, --max-segments, --jargon, patina pack and /api/packs, kimi-cli, PATINA_RHETORIC_POLICY=legacy), so the deviation is explicit.
• Version sync (20 strings, 13 files): package.json, package-lock.json (root and packages[""]), SKILL.md, .patina.default.yaml, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, packages/patina-humanizer/package.json (version and the exact patina-cli pin), README.md (badge, Quick Start line, YAML example), README_KR/ZH/JA.md (badge, YAML example), and the two playground version badges.
• scripts/check-retired-concepts.mjs needs no realignment: since chore(release): reduce the retired-concepts check to its one rule #935 it keys the historical boundary on the 7.0.0 heading, not on line numbers.

Scope and risk

• Contract impact: none beyond the version number. The removals themselves were reviewed and merged in feat!: remove --preview/--ocr/--serve and --xliff from the CLI #951–refactor(web): remove the unread playground funnel analytics #956.
• Size: 13 files, +34 / −20.

Verification

• npm run release:check → 0 ("Release metadata OK for 9.1.0"; retired-concepts: 0 forbidden)
• npm run lint → 0; npm test → 0 (2018 tests: 2017 pass, 1 skipped, 0 fail)
• npm run check:no-private-assets, npm run dogfood → 0
• npm run benchmark:report and npm run benchmark:compare → 0; the regenerated docs/benchmarks differ only in timestamp and Node-version lines (discarded)
• node scripts/release-artifacts.mjs --dry-run … → 0 ("Verified 9.1.0 release artifacts": both tarballs packed, installed together, and --version smoke-tested)
• Base: origin/dev 849a9a4.

Release and rollback

• Next steps (owner-approved): release PR dev → main with a merge commit, then tag v9.1.0. release.yml publishes patina-cli and patina-humanizer and creates the GitHub Release; no GHCR push. Vercel deploys main.
• Rollback: npm latest can be pointed back at 9.0.0 by the owner. The web rollback target is the current production deployment patina-gb0s82zka (dpl_6fiQSeZVG5pTJFa4XV9d4sdB8KR2, 9.0.0).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
patina	Ready	Preview	Sep 26, 2026 10:21am UTC

[devswha]

Independent review (read-only, one pass): APPROVE

Reviewer: separate read-only gate-review agent (did not write the change).

• All eight shipped units (feat!: remove --preview/--ocr/--serve and --xliff from the CLI #951–refactor(web): remove the unread playground funnel analytics #956, chore(deps): bump actions/checkout from 6 to 7 #933, chore(deps-dev): bump eslint from 10.10.0 to 10.11.0 in the devtools group #934) are listed with the right PR numbers; no false or overstated claims. The semver rationale names the removed public surfaces and states the owner's minor decision plainly. The version sync touches exactly the 13 expected files.
• Minor, fixed in the follow-up commit: the rationale said every removed flag and command fails with exit 2, but --model kimi-* now falls back to the HTTP default. The rationale now lists that route and names it as the one exception.
• Nits, no change: PATINA_RHETORIC_POLICY=legacy and the license-key / packs-url keys are now ignored rather than rejected, which the bullets already say. The undocumented hosted jargon request field no longer forces the strict prompt, but it was never part of the documented API.

Verified by the reviewer: every removed flag and command exits 2 (--preview, --ocr, --serve, --xliff, --dry-run, --max-segments, --jargon, pack list, --backend kimi-cli, --register a,b); #952's prompt snapshots change only the terminology header and bullet label; no detection or scoring code changed in main..dev; patina --version → 9.1.0; release:check 0 forbidden. CI: all checks green.