41775bc0 · zzmq.dev@gmail.com/zz
Commit
41775bc0389bfef03158f89b9f2b6a517bc27441
Check login state before ~/.zz/config.json, not after Real bug, confirmed live: configuredRepos(options.repos) was checked unconditionally before login state at all, so a stale local config (written by an earlier not-logged-in session, or a different account entirely) always won over the current identity's own repos -- logging in as a second account still showed the first account's tracked repos, since config.json isn't scoped per-identity and nothing was accounting for that. New order: --repos (explicit, always wins) > the server's own /api/me/repos if logged in to remote (never mixed with config.json) > config.json (the right fallback for the two cases with no server-side list to use instead: remote-not-logged-in, or local) > local discovery > empty. Verified live: logged in as a second real account (zzmq.dev@gmail.com, owns "shirt", tracks thoward37's "pants"), with ~/.zz/config.json still holding the FIRST account's repos from earlier testing -- confirmed the resolution now picks /api/me/repos's two entries (shirt, pants) rather than config.json's stale two (shoes, pants).
Troy Howard <thoward37@gmail.com> -- 2026-10-13T10:25:20.000Z