Public launch

New Issue

Everything the console needs before a stranger can read the README, run the stack from the quickstart, and trust the operator panel with real members. The engine is built; this milestone is the front door, the first-run experience, and the gaps that keep an operator's happy path from completing.

Done when a newcomer can read the README and understand what the console is in under a minute, run the stack from the documented quickstart without a boot failure that looks like a bug, land on an operator overview worth showing and find their way around it without a guide, complete the operator path from creating a product through pricing and syncing it to selling it, and attach a custom domain to a site; the repository carries the standard open-source hygiene files, and every visible affordance does what it says, with half-built features hidden rather than hinted.

Closed before the tracker moved here: the project front door, first-run friction, purchasability, the custom-domain code, hardening and polish, the operator overview, the first-contact pass, the audit remediation, the model cards, the verification-found hardening, the page anatomy and quality gate, and two security-audit runs remediated. Open: the last custom-domain operations sign-off on the reference deployment, and the issues in this milestone.

Order:

  1. #165, which derives FedWiki's site usage instead of keeping a running total.
  2. The defects that harm members or operators now, most harmful first: #163, #23, #141, #148, #212, #153, #285, then #269, #277, #272, #270 and #271, the subscriptions that bill while delivering nothing, then #287, #290, #291 and #293, then #178, #282 and #295, then #245, #246, #247, #283 and #284, then #196, then #312. None of them depends on the integration contract, so they go before it.
  3. What the contract needs before it starts: #164, what an unlimited limit is, which #171 states explicitly; and #184, the swap stored as two requests.
  4. The integration contract, in order: #171, #172, #173 (after #167, the notice part it uses), and #174 (with #44 and #46).
  5. At any point: #36, #64, #244, #321, and #186, which closes once #165 and #196 have written their locks into the lock order.
  6. Last: the custom-domain operations sign-off on the reference deployment, after #141.
No due date
75% Completed