Files
fusion/packages
Josemi Liebana 7f01b5341c fix(dashboard): use per-project chatStore in chat session API routes
In multi-project mode, all /chat/sessions* handlers used options.chatStore
(the home-dir project's store) regardless of the projectId query param.
Sessions in secondary projects were invisible via the API.

Root cause: registerChatRoutes accessed options.chatStore directly instead
of routing through resolveProjectChatContext (already used correctly in
registerChatRoomRoutes for the rooms API).

Fix: introduce resolveScopedChatStore(projectId) helper that delegates to
resolveProjectChatContext, replacing all ten options.chatStore usages.
Falls back to default store when engineManager is absent (backward compat).

Tests: add two cases to verify engine-scoped chatStore is used when
engineManager is configured for the requested projectId.
2026-05-22 13:35:50 +02:00
..
2026-05-19 22:09:26 -07:00
2026-05-19 22:09:26 -07:00
2026-05-19 22:09:26 -07:00
2026-05-19 22:09:26 -07:00
2026-05-19 22:09:26 -07:00
2026-05-19 22:09:26 -07:00