mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-07 04:12:04 +00:00
Marc-André Bombeck
20f5ae27a0
The switch is stamped on the session row, not held in the tab. Every authenticated spec opens its context from the same storageState file, so the sharing journey switching that jar into the owner's record switched it for whatever spec happened to be mid-navigation on the other worker. The failures land nowhere near the cause: /settings/ai painting "Not part of shared access" instead of the AI panel, an axe scan reading a banner its spec never asked for, a waitForResponse waiting on a request the refused surface never sends. Which spec loses depends on scheduling, which is why it moved between runs. Log the delegate in a second time and hand that jar to the journey. Same account, its own session row, no reach outside the file. The three login captures collapse into one helper while the third one is added, and the fixture's login-bucket reset already covers the extra attempt. The guard matches the two things a switching spec cannot avoid naming, the switcher entry it clicks and the endpoint that entry calls, and checks both that the match set is non-empty and that the shared jar is still what the ordinary specs read. Verified red by pointing the journey back at the shared jar.