P2 — Client Cutover onto the Pages Graph

[coderhd]

EPIC: H0 — P2: Client Cutover onto the Pages Graph.

After P1 laid the graph substrate, this moves the entire client (dashboard, editor, share modal, invitations, settings, version history) from legacy documents/document_members/document_invitations/document_versions onto pages/page_members/page_invitations — with page-only RLS authority, page invites with accept/decline, and pages-aware version checkpoints. Legacy tables stay as the rollback path.

Merged as PR #7 (squash ef8b03b).

Plan: docs/superpowers/plans/2026-08-15-p2-client-cutover.md

Tasks (all done)

• P2-T1: Foundation migration — page-only authority, page invites, pages-aware versions #15 — P2-T1: Foundation migration — page-only authority, invites, versions
• P2-T2: Server auth — page-only authority in verifyUserRole #16 — P2-T2: Server auth — page-only authority in verifyUserRole
• P2-T3: Client types + graph service layer #17 — P2-T3: Client types + graph service layer
• P2-T4: Dashboard cutover #18 — P2-T4: Dashboard cutover
• P2-T5: Editor route + workspace cutover #19 — P2-T5: Editor route + workspace cutover
• P2-T6: Share modal — page members UI #20 — P2-T6: Share modal — page members UI
• P2-T7: Invitations + invite page cutover #21 — P2-T7: Invitations + invite page cutover
• P2-T8: Settings cutover #22 — P2-T8: Settings cutover
• P2-T9: Version history + API route cutover #23 — P2-T9: Version history + API route cutover
• P2-T10: Whole-branch verification + live DB matrix #24 — P2-T10: Whole-branch verification + live DB matrix