cgalo5758
71818de0bd
Implement the ux-first-run change: a state-derived setup checklist on /operator/setup with a landing region that recedes once required steps are done, and empty states that distinguish blocked from empty across operator and member surfaces. Also add production deployment and environment reference docs, plus a config-key completeness test.
Status
A thin index of where member-console development stands. Detail lives in the linked files — this page stays short on purpose.
Where we are
Pre-production. A working Go/HTMX app with OIDC auth, FedWiki site management (create / delete / archive / restore with entitlement-gated quotas and downgrade read-only parking), a core domains registry (verify-once DNS claims, generic placements, entitlement-gated custom domains served through FedWiki), a Discourse forum integration (org-held entitlement, per-person delivery via group membership, live SSO + commerce loop proven), an operator MPA admin panel (curated landing overview, catalog, plan ladders, auto-provisioning, per-org enrollment, unified integrations section with runtime-managed settings), first-class plan management (ladders + the Transition supersession primitive + transition audit), Stripe billing (Checkout upgrade, cancel downgrade, subscription/invoice/payment sync), and Temporal workflows for site/group sync, domain verification, and Stripe fulfillment. Integrations live in registered trees behind an explicit contract; the database spans a single core domain schema plus a domains stream and the stripe, fedwiki, and discourse provider integration schemas with per-stream migration ledgers.
Milestones 1–9 complete; M10 (Open-Source Launch Readiness) resumed as the launch gate.
Current focus
M10 — Open-Source / Public Launch Readiness, resumed 2026-07-23 after M9 closed (9e/9f/9g all landed; Discourse proved the integration contract end-to-end). Done: 10a (front door, including the README operator-dashboard screenshot), 10b (first-run friction), 10c (purchasability), 10d code (custom domains — registry, verification, lifecycle hardening all shipped; production adoption remains as ops), 10f (presentable operator dashboard, including post-merge polish and metric refinement), 10h (audit remediation). Remaining: 10e (hardening & polish), then 10g (first-contact UX re-walk) as the final pass; 10i (model cards) runs in parallel and unblocks the deferred structural audit fixes; the Gitea migration is M10-blocking. See milestones.md for the boards and issues.md for open bugs and carried debt.
Key files
| File | Purpose |
|---|---|
| milestones.md | Milestone definitions and status (active + proposed) |
| issues.md | The home for known issues — backlog, bugs, design feedback |
| strategy.md | Design-alignment philosophy, the four-roadmaps lens, migration strategy, repo structure |
| fedwiki-service.md | FedWiki Service tier → implementation mapping |
| archive/ | Resolved issues and completed-milestone detail |
| MAINTAINING.md | Conventions for keeping status/ healthy |
log/ |
Per-session development logs |
design/ |
Data model and architecture reference (read-only, synced from research repo) |