- Split database.py into a runtime engine (scoped `kds` DB role, used for
all request handling) and a migration engine (privileged `kitchen` role,
used only at startup to create KDS's own tables and ALTER kitchen_settings)
— KDS previously shared kitchen's full-access DB credential wholesale
- Dispose both engines on shutdown (main.py)
- Fix theme colour clash: KDS was accidentally seeded with kitchen's teal
(#0d9488) instead of its own colour — now #ea580c (orange), regenerated
PWA icons to match
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
KDS uses a minimal Kitchen stub (no resos_* relationship properties) so
back_populates="resos_bookings" etc. caused mapper init to fail on every
request. Changed all four Resos.kitchen relationships to viewonly=True
with no back reference — KDS only reads these, not writes.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
kds_course_bumps.bumped_by_user_id references users.id — SQLAlchemy needs
the User model in Base.metadata to resolve this at startup. Route handlers
still receive a SimpleNamespace from auth.py at runtime.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
settings.py imports Kitchen for the back-reference relationship on
KitchenSettings.kitchen. KDS uses kitchen_db directly so the table exists;
this minimal model satisfies the import without pulling in kitchen-only models.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
