Monetization core: shared billing (clients/ledger/holds/Stripe), factory intake (client repos + issue provisioning), eval farm intake/results, delivery receipts. Two front-ends, one billing core.
The guard asserted gitea_saas/server.py was absent from the tree. That held only until #2 (which owns the app factory) merged; afterwards it fired against #2's own file rather than anything #9 shipped, and was the single failure when issue-9 was merged onto main. issue-9 adds exactly two files (gitea_saas/dashboard.py, tests/test_dashboard.py) and never contained server.py, so the invariant the docstring describes was always satisfied. It is now checked directly, via AST, so mount_dashboard's docstring example (app = Flask(__name__)) is not mistaken for a real call. |
||
|---|---|---|
| gitea_saas | ||
| tests | ||
| ARCHITECTURE.md | ||
| pyproject.toml | ||
| README.md | ||
| requirements.txt | ||
gitea-saas-core
Monetization core: shared billing (clients/ledger/holds/Stripe), factory intake (client repos + issue provisioning), eval farm intake/results, delivery receipts. Two front-ends, one billing core.