fix(mobile): keep home brand visible during secondary retries - #21388

💭 Investigating Atom imports I need to take a closer look at the changed lines regarding the Atom import from the effect/reactivity package. I'm wondering if the rule is about importing Effect modules from subpath namespaces. It's possible that this isn’t a violation since Atom seems to be exported from the package. I should check if the changes are only related to mobile state and presentation without affecting service consumption. Maybe workspaceConnections atoms might be related to the service too?

1. browse_code — apps/mobile/src/state/workspace.ts

2. browse_code — apps/mobile/src/state/shell.ts

3. browse_code — apps/mobile/src/features/home/workspace-connection-status.ts

4. browse_code — Does the changed apps/mobile/src/state/workspace.ts Atom.make create or consume an Effect Context.Service, or merely derive reactive client state? Identify any Effect service convention violation on changed lines in workspace.ts, workspaceModel.ts, workspace-connection-status.ts.

5. browse_code — apps/mobile/src/state/workspaceModel.ts

6. browse_code — Is effect/reactivity a package entry point for Atom, and is import { Atom } from "effect/reactivity" the established pattern in mobile state files? Answer briefly.

7. browse_code — Confirm effect/reactivity is a subpath barrel whose named Atom export is conventional versus named imports from bare effect; no further detail needed.