docs(changelog): trim history to Jun 23, 2026 and tighten every entry

[indykish]

Trims changelog.mdx to start at Jun 23, 2026 and brevity-passes every surviving entry.

What changed

Trim — cut the 23 entries dated Jun 17, 2026 and older (down to May 27, 2026). The changelog now runs Jul 23 → Jun 23, 2026. All 40 entries in that range are retained.

Tighten — rewrote every remaining entry per docs/CHANGELOG_VOICE.md: leads state the change instead of narrating the prior broken state, bullets follow **Bold lead-noun** — clause, intra-entry duplication removed (leads that restated their own first bullet), repeated glosses deduped across entries, run-on sentences split at the clause, and wordier terms simplified (curated → a set list, provisioned → configured).

	before	after
Whole file	17,186 words	8,455 (−51%)
Kept range (Jun 23+)	11,652 words	8,455 (−27%)
Mean sentence	15.3 words	12.4
Sentences ≥ 28 words	96	24

The 24 remaining long sentences are enumerations — provider lists, error-code lists — where splitting would hurt rather than help.

Load-bearing facts preserved

Verified by set-diffing the original against the rewrite, not by eye:

• 43 error codes (UZ-*) — all present
• 31 API paths (/v1/…, /_um/…) — all present
• Every CLI flag, plus RUNNER_NETWORK_POLICY and GRAFANA_OTLP_*
• All schema and field names — core.fleet_events, failure_detail, cost_nanos, budget_breach, gate_blocked, required_credentials_reasons, and the rest

Deliberate removals

Called out because they touch published values and metadata:

• Dead frozen-pricing block — EVENT_RATE_M65 ($0.01), STAGE_RATE_M65 ($0.10), STAGE_PLATFORM_M66 ($0.001), STAGE_SELF_MANAGED_M66 ($0.0001), and the unused STARTER_CREDIT / EVENT_RATE import from snippets/rates.mdx. Zero surviving entries referenced them; every entry that did was in the pre-Jun-20 range. No rendered money amount changed — $0, $0.00, and $1.20 are all intact.
• One-off tag chips normalized — Fixes → Bug fixes, Improvements → What's new.

Verification

• make test passes (22 tests + documentation check); also runs as a pre-commit hook
• gitleaks detect — no leaks, 462 commits scanned
• MDX brace audit — no unescaped {/} outside code spans or fences
• Structure — 40 <Update> open/close pairs balanced, oldest label Jun 23, 2026

Session notes

• Scope. Indy asked for a worktree, a trim to "June 20 or above", and a pointed rewrite of the elaborate entries. Mid-turn he added: watch for duplicates, simpler wordings, shorter sentences — which drove a second editing pass (the dedupe and sentence-splitting work above).
• Cutoff. "June 20 or above" lands between the Jun 17 and Jun 23 entries; nothing is dated Jun 18–22, so the boundary is unambiguous.
• Branch choice. ~/Projects/docs was sitting on chore/uuidv7-canonical-ids-changelog with an uncommitted Jul 23 <Update>. Per the docs-repo own-branch rule I branched this work off main in a separate worktree and left that change untouched. Indy was flagged that whichever branch merges second will conflict, and directed to ignore it and proceed here.
• History rewrite. CHANGELOG_VOICE.md treats past entries as an archive that may be brevity-passed but not rewritten. Deleting the pre-Jun-20 range goes past a brevity pass — done on Indy's explicit instruction, and the deleted entries remain in git history.
• No linter coverage. scripts/check-documentation.py skips changelog.mdx outright, so voice is unenforced here. I ran the project's own BANNED_PATTERNS against the file by hand and fixed the one hit (provisioned → configured), then expanded the bare acronyms it would have caught elsewhere: HMAC → "a hash-based message authentication code", OTLP → "OpenTelemetry Protocol (OTLP)", CI → "continuous-integration".
• Dead ends. First pass cut ~27% but left line count nearly flat, since MDX bullets are one long line each — word count, not line count, is the real signal. Ranked entries by words to find the remaining fat rather than trusting the diffstat.
• Not done. No other ~/Projects/docs page was touched; this is a changelog-only change with no product behavior behind it, so nothing else needs revising.

🤖 Generated with Claude Code

Greptile Summary

The PR trims the changelog to Jun 23, 2026 and substantially shortens all 40 retained entries.

• Removes all entries dated Jun 17 and earlier.
• Rewrites retained leads and bullets into the changelog voice format.
• Removes pricing imports and constants no longer referenced by surviving entries.
• Normalizes historical tags and section headings.

Confidence Score: 4/5

The PR should not merge until the omitted Jul 23 UI behavior and Jul 11 queue-retry guarantee are restored in concise form.

The archive trim is structurally coherent, but two retained releases lose substantive behavior rather than merely shorter wording, leaving the published release history incomplete.

changelog.mdx

Important Files Changed

Filename	Overview
changelog.mdx	Trims and rewrites the changelog, but the brevity pass drops complete shipped behaviors from two retained entries.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
changelog.mdx:12
**Shipped behaviors disappear from history**

When readers consult the retained Jul 23 and Jul 11 entries, the rewrite omits the live-connection animations and the guarantee that retrying a failed GitHub queue write repairs the write without duplicating successful events, leaving the published release record incomplete.

_{Reviews (1): Last reviewed commit: "docs(changelog): trim history to Jun 23,..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used:

• Knowledge Base — Site infrastructure, validation, and contribution rules

[greptile-apps]

Shipped behaviors disappear from history

When readers consult the retained Jul 23 and Jul 11 entries, the rewrite omits the live-connection animations and the guarantee that retrying a failed GitHub queue write repairs the write without duplicating successful events, leaving the published release record incomplete.

Knowledge Base Used: Site infrastructure, validation, and contribution rules

Prompt To Fix With AI

This is a comment left during a code review.
Path: changelog.mdx
Line: 12

Comment:
**Shipped behaviors disappear from history**

When readers consult the retained Jul 23 and Jul 11 entries, the rewrite omits the live-connection animations and the guarantee that retrying a failed GitHub queue write repairs the write without duplicating successful events, leaving the published release record incomplete.

**Knowledge Base Used:** [Site infrastructure, validation, and contribution rules](https://app.greptile.com/usezombie/-/custom-context/knowledge-base/agentsfleet/docs/-/docs/site-infrastructure.md)

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!