Reading every changelog bullet to understand capability
Manually reading every release bullet is a weak way to understand system change; interpreted release notes and Capability Deltas are needed.
Disappearing action
Human ritual: Read raw changelog bullets and infer what changed for real workflows. Old cost: Release notes mix marketing, bug fixes, breaking changes, security changes, and user-visible capability shifts. Replacement pattern: Interpreted release note that separates announced, inspected, installed, smoke-tested, workflow-tested, and reproduced behavior.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | code.claude.comsource | primary receipt | source_urls |
New Runtime should not publish release summaries as a habit. A release matters when it produces a Capability Delta, changes a system dossier, moves a shift, or updates a project.