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>