🐛 Bugfix: Was the backend-api-endpoints.md documentation correct about...

Date: 2026-02-20
Time: 19:28:47 UTC
Session: gspace1-129.4
Agent: documentation
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

Was the backend-api-endpoints.md documentation correct about /api/api/ double prefix affecting many controllers?

Task: Correct misleading documentation about /api/api/ prefix

🎯 Decision Made

Chosen:

No. The docs were wrong. They claimed ~10 controllers had the double prefix issue (global-modules, marketplace, products, orders, universes, unified-modules, global-widgets/flows/templates, universe data) but verification showed only 6 controllers actually had the bug. The others (global-modules, marketplace, products, orders, universes, unified-modules-v2, global-resources, data) were all correctly using paths without 'api/' prefix. The docs were fabricating a widespread issue that didn't exist.

Options Considered:

• No alternatives documented

💭 Reasoning

The docs explicitly said 'Controllers that already embed api/* in their @Controller path will surface as /api/api/...' and listed many controllers. But grep of actual @Controller decorators showed global-modules uses @Controller('global-modules'), marketplace uses @Controller('marketplace'), products uses @Controller('products'), etc. — all correct. The docs were either auto-generated incorrectly or someone assumed all controllers had the pattern after seeing it in a few. Fixed all /api/api/ references in both doc files and the Cursor plan file.

📁 Files Involved

• docs/english/Backend-Api/Api/backend-api-endpoints.md
• docs/english/Backend-Api/Api/backend-api-overview.md
• .cursor/plans/admin_dev_apps_overhaul_64fa42ac.plan.md

🔗 Related

• Decision ID: dev_1771615727865_3c5wfk3
• Session: 129
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation