Three fixes for validation consistency:
1. bd create --validate now uses LintIssue() instead of ValidateTemplate(),
bringing it to parity with bd lint. A non-empty --acceptance field now
satisfies the "Acceptance Criteria" requirement without needing the
heading in --description. (GH#2468 parity)
2. --dry-run no longer bypasses --validate. Validation now runs before the
dry-run exit, so users get feedback on template issues during preview.
3. New validation.on-close config option (none|warn|error, default: none).
When enabled, warns on terse close reasons (<20 chars) or default
"Closed" reasons. Mirrors existing validation.on-create pattern.
Co-Authored-By: seanmartinsmith <114885497+seanmartinsmith@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Previously, bd lint required the literal text "Acceptance Criteria" (or
"Success Criteria" for epics) to appear inside the acceptance_criteria
field content. Now a non-empty field satisfies the requirement regardless
of whether a markdown heading is present.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
LintIssue() only checked issue.Description when validating required
template sections. If acceptance criteria were stored in the dedicated
AcceptanceCriteria field, lint incorrectly reported them as missing.
Now concatenates both fields before validation so required sections
found in either field satisfy the lint check.
Closes#1472
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Executed-By: beads/crew/leeloo
Rig: beads
Role: crew