Desktop selected-instrument data
Lab Data
Save a canonical instrument list, inspect its local candle state, and explicitly queue the instruments that need refresh before running Mass Effect.
How the Data Flow Works
- Saved lists contain canonical Instrument Catalog identities and are limited to 250 members.
- Ranked volume can help discovery, but it never changes a saved list automatically.
- The Hub asks Flutter's
candle_cachebridge to inspect or update selected instruments. - Refresh work is a manual, visible queue; there is no background corpus subscription.
Prepare a Mass Effect Run
- Create or open a saved list and select the canonical instruments you want to test.
- Inspect local candle status, then explicitly run the refresh queue for missing or stale items.
- Wait for selected instruments to be complete before starting Mass Effect.
- Run Mass Effect with its fixed
1hcandle interval and review the local results.
Local Storage and Reset
Desktop Lab state keeps saved lists and Mass Effect results in app-owned local SQLite databases. Candle payloads remain owned by Flutter's normal candle cache. Resetting Lab data removes only recognized app-owned Lab artifacts; production R2 objects and the retired production update-cache volume are not part of this operation.
Wise Apple Guides