fix(gensui): build the correct frontend in Dockerfile

[wstlima]

Fixes #6

Summary

gensui/Dockerfile's frontend-builder stage does COPY frontend/..., which only resolves to the Gensui admin UI (gensui/frontend/) if the Docker build context is gensui/ itself. But the same Dockerfile also does COPY pyproject.toml ./, and pyproject.toml only exists at the repo root — not inside gensui/. A single build context can't satisfy both COPYs as originally written.

Building with context: .. (repo root, required for the pyproject.toml COPY) makes COPY frontend/... resolve to shogun/repo/frontend/ — the main Shogun (Tenshu) frontend, not the Gensui admin UI. That frontend targets /api/v1/*, while Gensui's API is mounted under /api/gensui/*.

Effect

The container built and served a frontend successfully (200 on /, masking the problem), but every API call from that UI 404'd because the bundled JS called the wrong backend:

GET /api/v1/health -> 404 {"detail":"Not Found"}
GET /api/v1/system/notifications -> 404
GET /api/v1/setup/status -> 404

Confirmed by grepping the built JS bundle for both prefixes — only api/v1 was present before the fix.

Fix

Reference gensui/frontend/ explicitly in both COPY instructions, so the correct admin UI is built regardless of whether the build context is gensui/ or the repo root.

Test plan

• Built bundle only references api/gensui after the fix
• Page title changes from the Shogun Tenshu UI to "Gensui — Central Command"
• Depends on fix(gensui): add missing bcrypt and pyjwt dependencies #12/fix(gensui): correct frontend dist path resolution #13 being applied first for the container to boot cleanly enough to verify end-to-end