The changelog now keeps itself honest
Every meaningful change to a platform capability now requires its own changelog entry before it can merge - enforced in CI, mapped to the component it touched, timestamped to the minute - while styling and copy tweaks stay out of the noise.
A changelog you can trust is one that cannot be forgotten.
- A new CI gate maps every changed file to the platform component it belongs to - path generation, content generation, assessments, adaptation, outcomes, demand, and the rest - and blocks any pull request that makes a major change to a component without shipping a changelog entry for it and a version bump.
- "Major" is judged by substance, not noise: real logic churn or new capability files trigger the gate; styling, copy, tests, docs, and tooling changes never do - so the changelog records what actually changed for you, not every comma.
- Every new entry now carries a full timestamp, not just a date, so same-day releases stay in honest order.
- Entries keep their existing guarantees: a registered component, a learner-facing summary, and a version that moves with the platform.