Several Next.js API routes return hardcoded mock data instead of querying the database, even though Prisma models exist for the data. This was the same class of bug as #48 (capacity planner).
Routes with DB models that use mock data instead:
developer/models/route.ts - Uses hardcoded models from @/lib/data/developer-models instead of querying DevApiAIModeldeveloper/models/[id]/route.ts - Same issuedeveloper/models/[id]/gateways/route.ts - Uses mock data instead of DevApiGatewayOfferintegrations/route.ts - Returns hardcoded INTEGRATIONS array instead of querying IntegrationConfig
Routes with mock data but NO DB model (lower priority, left as-is):
network-analytics/* routes (4 routes) - No DB models, display analyticsorchestrator-manager/orchestrators/route.ts - No DB modelreleases/route.ts - No DB model (future: GitHub API)plugin-publisher/stats/[packageName]/route.ts - Fake timeline
Fix: Migrate the 4 high-priority routes to use Prisma queries.
Several Next.js API routes return hardcoded mock data instead of querying the database, even though Prisma models exist for the data. This was the same class of bug as #48 (capacity planner).
Routes with DB models that use mock data instead:
developer/models/route.ts- Uses hardcoded models from@/lib/data/developer-modelsinstead of queryingDevApiAIModeldeveloper/models/[id]/route.ts- Same issuedeveloper/models/[id]/gateways/route.ts- Uses mock data instead ofDevApiGatewayOfferintegrations/route.ts- Returns hardcoded INTEGRATIONS array instead of queryingIntegrationConfigRoutes with mock data but NO DB model (lower priority, left as-is):
network-analytics/*routes (4 routes) - No DB models, display analyticsorchestrator-manager/orchestrators/route.ts- No DB modelreleases/route.ts- No DB model (future: GitHub API)plugin-publisher/stats/[packageName]/route.ts- Fake timelineFix: Migrate the 4 high-priority routes to use Prisma queries.