Add planning controls to RFC review dashboard

[SoundBlaster]

Motivation

PR #10 turns the 60 review cards into a dependency-aware backlog, but the generated dashboard does not expose that planning data or let maintainers work through a focused queue.

Goals

• Make profile, maturity, target, dependency, and readiness metadata visible on every card.
• Let maintainers filter the backlog and navigate only the resulting card set.
• Preserve pinned RFC highlights, connector behavior, and wide/compact layouts.

Changes

• Add profile, priority, coverage, maturity, target, and readiness filters with visible/ready/blocked counters.
• Add card footers for profile, maturity, target, readiness, depends_on, and derived blocks.
• Make dependency chips select their target while relaxing only filters that hide it.
• Make Next/Previous operate on the filtered set and scroll to the selected card; compact navigation remains sticky.
• Extract and test a pure dashboard state layer for inverse edges, readiness, filtering, navigation, and filter relaxation.
• Embed the full validated dashboard payload with single-pass placeholder substitution and script-breakout-safe JSON serialization.
• Add explicit accessible pin toggles, stable card-specific labels, filtered-state build markers, and reserved filter sentinel IDs.
• Enforce repository-wide whitespace validation in GitHub Actions against the complete committed tree.

Validation

• make review-check PYTHON=/tmp/agent-surface-maintenance-uv/bin/python (33 Python tests, 6 Node tests)
• node --check review/dashboard-state.js
• node --check review/dashboard-ui.js
• node --check review/check_review.mjs
• git diff --check
• git diff --check 4b825dc642cb6eb9a060e54bf8d69288fbee4904 HEAD
• Two independent read-only reviews: no remaining P0–P2 findings.

Boundaries and Non-Goals

• Does not change RFC prose, review priorities/statuses, dependency mapping, maturity assignments, or target releases.
• Does not add authoritative evidence resolvers for maturity above specified.
• Does not persist derived blocks or readiness.

Notes

• Stacked on PR Migrate RFC review cards to planning metadata #10 (codex/review-card-planning-metadata).
• Browser policy blocks direct automation of the local file:// artifact, so screenshot/DOM measurement remains a manual pre-ready gate; no alternate browser workaround was used.