Summary
api_public base defines its own repository layer (bases/bot_detector/api_public/src/app/repositories/) for report, player, feedback, and labels queries. The SQLAlchemy ORM models for these same entities already live in components/bot_detector/database/api_public/.
This splits model and query logic across brick boundaries — table definitions in the component, query logic in the base.
Proposed Change
Migrate the repositories from api_public base into components/bot_detector/database/api_public/, keeping models and queries co-located per the feature-based component pattern described in AGENTS.md.
Context
Migration artifact from earlier architecture. The intent was always to consolidate these into the database component.
Summary
api_publicbase defines its own repository layer (bases/bot_detector/api_public/src/app/repositories/) for report, player, feedback, and labels queries. The SQLAlchemy ORM models for these same entities already live incomponents/bot_detector/database/api_public/.This splits model and query logic across brick boundaries — table definitions in the component, query logic in the base.
Proposed Change
Migrate the repositories from
api_publicbase intocomponents/bot_detector/database/api_public/, keeping models and queries co-located per the feature-based component pattern described in AGENTS.md.Context
Migration artifact from earlier architecture. The intent was always to consolidate these into the database component.