[BUG] PR #2114: Fix Mermaid Accessibility & README Validation Failures
Summary
PR #2114 attempts to address Mermaid diagram accessibility and README frontmatter validation failures, but the PR itself has multiple CI failures and missing template sections that prevent merge.
Definition of Ready (DoR)
Critical Issues Found
1. Missing npm Scripts ✅ FIXED
- Status: Fixed
- Root Cause: CI workflow invokes
npm run validate:branch-name, npm run validate:issue-fields, etc. but scripts are not defined in package.json
- Solution: Add missing script definitions to package.json
- Files Modified: package.json
2. Mermaid Diagram Validation ⏳ PENDING
- Status: Requires verification in CI
- Issue: Accessibility check and colour contrast check failed
- Solution: Ensure changed-files-list handling works correctly
3. README Frontmatter Validation ⏳ PENDING
- Status: Requires verification in CI
- Issue: README.md files have frontmatter validation issues
- Solution: Ensure frontmatter validator properly targets changed files only
4. PR Template Enforcement ✅ FIXED
- Status: Updated with all required sections
- Solution: Linked issues reference and DoD checklist added
Definition of Done (DoD)
Success Criteria
Links
[BUG] PR #2114: Fix Mermaid Accessibility & README Validation Failures
Summary
PR #2114 attempts to address Mermaid diagram accessibility and README frontmatter validation failures, but the PR itself has multiple CI failures and missing template sections that prevent merge.
Definition of Ready (DoR)
Critical Issues Found
1. Missing npm Scripts ✅ FIXED
npm run validate:branch-name,npm run validate:issue-fields, etc. but scripts are not defined in package.json2. Mermaid Diagram Validation ⏳ PENDING
3. README Frontmatter Validation ⏳ PENDING
4. PR Template Enforcement ✅ FIXED
Definition of Done (DoD)
Success Criteria
Links