Operations
Smoke Validation
What smoke should prove after migration reset and reseed
Smoke must prove
- platform bootstrap succeeds from DB
- tenant resolution is correct
- runtime repositories hit the correct tenant DB
- workspace creation works with valid owner data
- app resolution works from entitlements
- worker config reads and updates through platform APIs
Development rule
Optional flows may be skipped when rate-limited in dev, but the reason should be explicit.
Smoke should fail loudly for:
- broken bootstrap
- broken tenant routing
- broken runtime schema
- broken first-party app resolution