refactor(cli,mcp): replace GitHub Issues board with beads-native implementation

[perasperaactual]

Summary

Replaces the gh issue list-based stackwright board command with a beads-native implementation that reads .beads/issues.jsonl directly. The stackwright_get_board MCP tool is updated in sync.

Changes

• packages/cli/src/commands/board.ts — full rewrite: BeadsIssue type, JSONL file walk-up loader, numeric priority 1–4 → tier mapping, BEADS_NOT_FOUND error code
• packages/cli/src/index.ts — GhIssueRaw → BeadsIssue in public type exports
• packages/cli/test/commands/board.test.ts — updated fixtures + 4 new tests (closed excluded, non-issue type ignored, unknown priority, mixed)
• packages/mcp/src/tools/board.ts — uses i.id / i.issueType, GitHub reference removed from tool description
• packages/cli/AGENTS.md + packages/mcp/AGENTS.md + CLAUDE.md — docs updated
• .changeset/refactor-board-beads-native.md — minor bump, breaking type changes documented

Breaking changes (public types in @stackwright/cli)

• GhIssueRaw removed → BeadsIssue
• BoardIssue.number: number → BoardIssue.id: string
• BoardIssue.labels and BoardIssue.assignees removed
• BoardIssue.issueType?: string added

What is NOT changed

• utils/git.ts — gh() utility untouched (still needed by git open-pr)
• git open-pr command — a separate issue tracks decoupling that from gh

[github-actions]

✅ Visual Regression Test Results

Status: ✅ All visual tests passed!

All screenshots match the baseline. No visual regressions detected! 🎉

[github-actions]

⚡ Performance Benchmark Results

✅ Build Time Benchmarks: PASSED

✅ Bundle Size Benchmarks: PASSED

❌ Runtime Vitals Benchmarks: FAILED

📝 Note: Detailed results are available in the job logs.

🎯 Performance Budgets:

• Build time: <70s total
• First-load JS: <100KB gzipped
• FCP: <1.5s, LCP: <2.5s, TTI: <3s

---

Updated: 2026-05-20T16:13:33.093Z

[github-actions]

♿ Accessibility Test Results

Overall Status: ✅ 0/0 tests passed

🦮 WCAG 2.1 AA Compliance

No WCAG test results available

⌨️ Keyboard Navigation

No keyboard navigation test results available

---

⚠️ No accessibility tests were executed. Check the workflow logs for setup issues.

📊 Detailed Report

Download the full HTML accessibility report from the workflow artifacts for:

• Detailed WCAG violation descriptions
• Specific element selectors and fixes
• Color contrast issues
• Keyboard navigation flow analysis

🔍 Testing Checklist

Our accessibility tests verify:

• ✅ WCAG 2.1 Level AA compliance
• ✅ Color contrast in light and dark modes
• ✅ Tab key navigation through all interactive elements
• ✅ Focus indicators are visible
• ✅ No keyboard traps
• ✅ Skip links and ARIA landmarks
• ✅ Screen reader compatibility

---

Powered by @axe-core/playwright and Playwright