Migration-Path

Phase 1: GitHub canonical, barocss-hub experimental. Phase 2: barocss-hub as a dual-write mirror. Phase 3: barocss-hub canonical, GitHub mirror. Phase 4: GitHub is optional export/backup.

Under direction B (D-048)

• The phases stay; what "barocss-hub canonical" means changes: in phase 3 the barocss-hub server is the canonical repository (the authoritative replica), and GitHub is a mirror exported from it. Developers and agents use thin clients or the server API; nobody needs a full clone.
• Phase 2 dual-write runs through the server: a bridge on the server mirrors between GitHub and the server's op set (design not yet specified; [open question]).
• Prerequisites before phase 2: the HTTP server with required auth (Online-First 6.5, E-B1), live sessions (6.3), thin clients (6.2).
• Superseded: a reading of phase 3 in which every developer's full replica is canonical (direction A, rejected by D-048).