beads/internal/validation
kev ba284fd6e9 feat(lint): accept Acceptance Criteria heading for epics (#3834)
bd lint required "## Success Criteria" for epics but "## Acceptance
Criteria" for bug/task/feature/story. Agents repeatedly trip on this
epic-only exception. Now an epic satisfies the requirement with either
heading, while Success Criteria stays canonical for new epics.

The OR-rule lives in validation.ValidateTemplate: when the issue type is
epic and the missing required heading is "success criteria", a present
"acceptance criteria" heading also satisfies it. This is additive — every
existing Success-Criteria epic still passes — and it does NOT add a second
entry to RequiredSections (which would require BOTH headings). Because bd
lint, bd create --validate, and bd doctor --check=conventions all route
through ValidateTemplate, the fix covers all three.

The alias is epic-scoped: a feature/task/bug is still not satisfied by a
"Success Criteria" heading (covered by a regression test).

Updated lint --help and regenerated CLI_REFERENCE.md, website lint.md
(all versions), and llms-full.txt; freshness checks pass.

Non-goals: not changing the canonical heading for new epics; not relaxing
requirements for any other type.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-07 23:00:30 -04:00
..
bead.go fix(create): normalize trailing hyphen in dbPrefix before prefix validation (#4233) 2026-06-16 10:21:06 -07:00
bead_test.go fix(create): normalize trailing hyphen in dbPrefix before prefix validation (#4233) 2026-06-16 10:21:06 -07:00
issue.go fix(close): refuse silent close on actor/assignee mismatch (#3734) 2026-07-05 23:51:45 -07:00
issue_test.go fix(close): refuse silent close on actor/assignee mismatch (#3734) 2026-07-05 23:51:45 -07:00
template.go feat(lint): accept Acceptance Criteria heading for epics (#3834) 2026-07-07 23:00:30 -04:00
template_test.go feat(lint): accept Acceptance Criteria heading for epics (#3834) 2026-07-07 23:00:30 -04:00