changesets

Record what consumers need to know after implementation and focused validation.

Workflow

1. Inspect the complete diff and identify directly affected published packages.
2. Classify impact across source types, runtime behavior, entrypoints, required services, lifecycle, and persisted or wire data.
3. Perform the breaking audit below.
4. Record either a reason no changeset is required or one coherent changeset. When required, read authoring.md.
5. Validate package names, frontmatter, bump policy, and consumer-facing text.

Do not include unrelated worktree changes.

Requirement