[v1.0] future-branch meta · graduation criteria for promoted features

[Jonathangadeaharder]

Future-branch meta — graduation criteria

Any work promoted to a future/* branch in this repo must clear the same quality bar before merging back to main:

• Unit tests on the new code path (Vitest, ≥85% coverage on changed files)
• PBT (fast-check) suites where input space is large
• Playwright e2e covering the new route(s)
• Visual regression baselines added/updated
• Accessibility checks (axe-core, keyboard navigation, screen reader labels)
• Telemetry-via-abstraction (no direct vendor SDK references in business logic)
• Docs: README section + inline JSDoc on public APIs
• Owner approval (a human reviewer who used the feature end-to-end)

Active / planned future branches

• future/online-play — multiplayer online tables
• future/tournaments — tournament structures + blinds escalation
• future/leaderboards — global + friend leaderboards
• future/multi-table — multi-tabling support

This issue is the index. Add a row when a new future/* branch is created.