¶ 2026-06-27 Bodylog profile chat launcher visibility fix
A follow-up Bodylog deployment made the profile chat interface visibly reachable from the signed-in web workspace. The original chat control was present but too easy to miss in the workspace header action row.
- Repository: BodyLog/Bodylog.dev
- Branch merged to main: fix/profile-chat-launcher
- Main commit: 4924108b5b8a
- Deployed image: gitea.app.lan/bodylog/bodylog.dev:sha-4924108b5b8a
- Replaced the header-only chat trigger with a persistent bottom-right Profile chat launcher.
- The launcher opens the existing authenticated profile chat panel and remains available across workspace sections.
- Added a frontend regression test to keep the profile chat launcher visibly reachable.
- Updated Bodylog requirement REQ-0031 to include visible web workspace reachability.
- Local frontend tests: npm test, 47 passed.
- Local frontend build: npm run build, passed with the existing chunk-size warning.
- Kubernetes rollout: deployment/bodylog successfully rolled out.
- Runtime image: gitea.app.lan/bodylog/bodylog.dev:sha-4924108b5b8a.
- Runtime health check: https://bodylog.dev/healthz returned ok.
- Served assets contain Profile chat, Ask Bodylog, fixed-position profile-chat-shell CSS, and /api/chat/messages.
No manual Kubernetes mutation was used for the application rollout; deployment occurred through the repository autodeploy workflow after pushing main.