[Migration] Complete Private Project Import: Stock Management, DB Alignment...

[eloiberlinger1]

[Migration] Complete Legacy Project Import: Stock Management & DB Alignment

Context

Following the transition to Open Source and the initial editor import (facilitated by Claude Code), several core modules from the previous private version still need to be migrated. This issue tracks the integration of the warehouse/stock management system and the database restructuring required to support multi-tenancy for climbing gyms.

Roadmap & Tasks

1. 🏗️ Database Schema Alignment

• Audit and adapt the differences between the legacy private schema and the new repository structure.
• Ensure data integrity between Editor sessions and available hold stocks.

2. 📦 Stock Management Interface

• Import React components for the "Stock Manager" dashboard.
• Refactor UI components to match the current project's design system and tailwind config.
• Map frontend components to the new API endpoints.
• Restore logic for hold filtering (by brand, type, color, and texture).

3. 🔐 Gym-Specific Connections (Multi-tenancy)

• Implement/Import the logic for gym isolation (ensuring Gym A cannot see Gym B's data).
• Set up dedicated dashboard views for gym administrators.
• Configure authentication middleware to handle gym-based features.

4. 🧹 Integration & Quality Control

• Clean up imported code to resolve ESLint and TypeScript warnings.
• Document any new environment variables required for the stock module.
• Verify the end-to-end flow: selecting a hold from the real inventory within the 3D Editor.

Technical Notes

The Editor is currently functional but operates with isolated/mock data. This migration will "reconnect" the editor to a live catalog of holds managed through the Stock Manager.

Assignee: @eloiberlinger1
Labels: migration, backend, feature, internal