The kind system classifies work as `feature`, `fix`, or `chore`. These three values are accurate but incomplete — there's no way to distinguish routine feature work from significant new capabilities. A filter button added to an existing page and an entirely new authentication system are both "feature." This matters because kind flows into the proof chain, the website ship log, and will soon drive branch prefix selection (Scope 2: kind-aware branch prefixes). A fourth kind, `milestone`, gives Ana and developers a way to signal "this is announcement-worthy" — enabling downstream consumers to surface significant work differently from routine work.
Contract assertions A015/A016 reference docs-research/supermock/ files that are not tracked in git — untracked directory, cannot be modified in a branch
A002 test asserts on echoed invalid input ('fix + chore'), not on the four-value error string — source inspection confirms correct text but test would pass even if milestone were missing from the error message
obspackages/cli/src/utils/proofSummary.ts→ closed
extractScopeKind regex matches **Kind:** anywhere in file, not section-scoped — pre-existing issue, milestone addition doesn't change the risk profile
Dark mode milestone badge has no background override — inherits light-mode color-mix background. Works because transparent mix renders identically in dark mode, but inconsistent with feature badge which doesn't set explicit dark background either
No test verifies milestone badge CSS class or label output — website has no test suite, so ProofFeed rendering is unverified beyond type checking and build compilation