Completed work — summary of already implemented features. Technical debt — accepted follow-up work that is intentionally deferred.
Architecture decisions are captured in AGENTS.md.
- Equipment browsing API — read-only endpoints for catalog navigation (groups, categories, items, brands)
- Admin management overview — CRUD for catalog data (admin only) with contribution logging
Tasks in execution order:
- Foundations — shared patterns for all admin endpoints
- Brands CRUD — create, update, delete brands
- Groups CRUD — create, update, delete groups
- Categories CRUD — create, update, delete categories
- Category properties — manage property definitions and enum options
- Item creation — create items with property values (multi-table transaction)
- Item maintenance — update and delete items
- User inventory API — users add/remove items to their personal gear list
- Frontend — UI for browsing, item detail, user inventory, admin management
- Expand DB-free Vitest handler coverage — the current catalog handlers already use the baseline pattern: direct handler imports plus mocked
event,dbHttp, and auth/body helpers. Extend the same approach to the remaining API endpoints as they stabilize. - Refine category detail loading — in
GET /api/equipment/categories/[slug], fetch enum options only for enum properties instead of loading relation data that is later discarded for non-enum properties.