fix(os): preserve seeded contexts when reloading from OSIS #126
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_os!126
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_fix_context_dropdown_drop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
reload_contexts_from_backendwas replacing thecontextssignal with whateverhero_osis_basereturned. Becausegeomindis a hardcoded WASM seed (not registered in OSIS), creating any other context in OSIS would silently dropgeomindfrom the Switch Context dropdown — leaving the user unable to navigate back to it from the UI.Replace with merge: backend wins for matching names, locally-known contexts (the seeded
geomind) survive if the backend has not registered them yet. Same fix applied to the mobile reload path.Related Issue
N/A (caught live while triaging contexts).
Changes
Test Results
Playwright in browser via tunnel (release build deployed to herodev):
audit-ctx, Switch Context dropdown now listsGeomind+audit-ctx(was:audit-ctxonly)Geomindswitches the URL to/space/geomind/voiceand the toolbar updates toGeomind83a0e8b9379b598f0e7c