v0.5.2 — jargon lists, a scoped-write fix, and a CI gate

Covers everything since v0.4.2 (0.4.3, 0.5.0 and 0.5.1 were never released on their own).

What's new

• User jargon lists: Rule 18 and /iceberg:jargon (#8). Pick an industry pack, name your own words, or both; /iceberg:edit and /iceberg:score apply the list automatically once .iceberg/jargon.txt exists.
• Write access is scoped (#10, #11). edit no longer pre-approves Write (it asks before overwriting your file), and score, jargon and the score agent are limited to ./.iceberg/**. This clears the upload scanner's unscoped-write finding.
• A CI gate on every PR (#10, #12). It fails on unscoped Write/Edit/Bash grants, whole-environment reads in shipped code and committed executables, and runs claude plugin validate --strict.
• Directory icon (#9) and a README that discloses the Stop hook (#7).

No binaries: iceberg is skills and agents only, so there is nothing to attach to this release.

v0.4.2

Launch: new README, landing page, strict-valid manifests.

• README and landing page rewritten around a before/after example.
• Sample grades verified with the scorer: Before is F, After is A (35 words, 0 violations).
• Manifests pass claude plugin validate --strict.

iceberg v0.4.0

• Three opt-in extended rules, off by default: --no-em-dash (strip em dashes), --no-weakeners (strip mid-document clauses that undercut a claim outside a labeled Limitations/Caveats section), --strip-ai-commentary (strip self-referential assistant voice and dev-cycle narration)
• fix: Stop hook built its JSON with unescaped file interpolation — a crafted .iceberg/last-score.txt could inject sibling decision/reason keys into the hook output (h/t @builtbyproxy, #1)
• fix: the #1 fix's tr step errored on a multi-byte UTF-8 character split by the 2000-byte truncation cut; truncation now happens inside jq on the decoded string (#3)

iceberg v0.2.1

• fix: add disallowedTools: Skill to iceberg-edit and iceberg-score agents to prevent skill recursion in subagents

v0.2.0

Current release — Hemingway writing rules for technical documentation.