Skip to content

docs: add CHANGELOG.md #114

@AbstractNucleus

Description

@AbstractNucleus

What: No CHANGELOG.md.

Why: The decisions register captures architectural choices but not the user-facing change log. Operators upgrading a deployment have no quick way to see what changed.

Approach: Adopt Keep a Changelog format. Backfill from recent PR titles is fine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions