Read release-notes.md for any visible change. Read migration-guides.md when readers must take action.

Ground each item in delivered changes. Separate end-user improvements, administrator actions, and technical compatibility details. State who is affected, what changed, when action is required, and how to verify success. Never invent versions, dates, issue numbers, support windows, or guarantees.

For a renamed API field, write a short user-facing release note, an operator deployment checklist, and a technical migration guide with old/new payloads, rollout order, and rollback test.