Risks and Technical Debt

Tracked debt, with its planned resolution. Small enough to be honest about.

Pre-service-layer web code. The oldest controllers and exception handling predate the service-layer rework and are scheduled for rewrite with the API-layer phase - including replacing generic exceptions with domain exceptions and moving the last derived getter off an entity into a DTO.
Legacy frontend. The separate React app is frozen (known cosmetic defects included) until the Angular frontend in this repository replaces it; it is retired, not migrated.
Single environment. No staging tier (section 02): pull requests get the full test gate, but production is the first runtime environment every merge meets. Accepted for a system whose data is disposable.
Credential lifecycle. A password-expiry feature for user accounts is designed but unscheduled; demo accounts must be exempt so the public demo cannot lock itself out.
Scaling triggers, not scaling debt. The monolith is a decision with named exit conditions (ADR 007, ADR 010) - reaching them is growth, not debt.