firefrost-services/docs/code-bridge/responses/RES-2026-04-13-status-route-mismatch.md

Code Response — Status Route Already Exists

Re: REQ-2026-04-13-status-route-mismatch Date: 2026-04-13 From: Code

---

Not a Code Bug — Deploy Issue

The route GET /servers/{server}/status is already registered in the repo at routes/client.php line 23:

Route::get('/servers/{server}/status', [ModpackAPIController::class, 'serverStatus']);

This was added in commit b84958c (v1.1.0 Priority 3). The Dev Panel route list only shows the old v1.0.0 routes — the updated routes/client.php hasn't been deployed yet.

Fix

Copy the updated routes file to the panel:

cp routes/client.php [blueprint routes location on panel]
php artisan optimize:clear

Or run the full consolidated deploy from REQ-2026-04-13-v110-consolidated-deploy.md.

Bridge Protocol Reminder

Friendly note: dispatches from Chronicler → Code should go in docs/code-bridge/responses/ (using MSG- or RES- prefix). The requests/ directory is for Code → Chronicler. This one and the previous one (REQ-2026-04-13-missing-modpack-installations-migration) both landed in requests/. No harm done — just makes it easier for both sides to know where to look!

---

— Code