feat: persist current workspace in user sessions
This commit is contained in:
@@ -2,22 +2,21 @@
|
||||
|
||||
## Current
|
||||
|
||||
### `feat/demo-assets`
|
||||
### `feat/current-workspace-session-model`
|
||||
|
||||
Status: in_progress
|
||||
|
||||
DoD:
|
||||
- project has an idempotent PostgreSQL demo seed for live UI screens
|
||||
- demo seed fills workspaces, memberships, invitations, operations, agents, keys and usage
|
||||
- seed is controlled by env and does not live in migrations
|
||||
- docs explain how to enable and use demo data
|
||||
- current workspace is stored in authenticated session, not only in localStorage
|
||||
- workspace switcher updates session state through auth API
|
||||
- shell identity and page data follow session-selected workspace after reload
|
||||
- frontend retains only cache/fallback state, not source-of-truth selection
|
||||
|
||||
## Next
|
||||
|
||||
- `feat/alpine-polish`
|
||||
- `feat/agent-lifecycle-polish`
|
||||
|
||||
## Backlog
|
||||
|
||||
- `feat/current-workspace-session-model`
|
||||
- `feat/agent-lifecycle-polish`
|
||||
- `feat/platform-key-usage`
|
||||
|
||||
Reference in New Issue
Block a user