🤖 automated
Found dogfooding #1640/#1644/#1645 on main (chain write-up: #1204 (comment)).
What happened. On the Overview, the Routine work card has a Run in picker that scopes the per-project routines (#1640). I set it to tf-1334-dogfood, clicked Run now (correctly scoped), opened the run, came back to the Overview — and the picker read gemstack again, the first registered project. The next click fired a quick triage on gemstack, the real repo. It was stopped at 40 seconds with nothing committed, but it had already pushed an empty tf-triage-quick to the repo's origin — which is #1643's trap, now armed for the next gemstack triage until someone deletes the branch.
Why it matters. The picker decides which repo spends quota and gets branches pushed, and it silently forgets the choice on the most common navigation there is (open a run, come back). The first project in the registry is the user's main repo, so the failure mode is always "the wrong click lands on the real codebase". The tooltip does name the project ("Starts one agent in gemstack …"), which is how it is catchable — but only by reading the tooltip before every click.
Fix shape. Remember the pick across navigations — the session store the rest of the dashboard already uses is enough; persisting it as a preference would also make it survive reloads. Defaulting to the project whose page the user came from would cover the open-run-and-return case on its own.
Repro. Overview → set Run in to any project but the first → open any run from the sidebar → Overview.
🤖 automated
Found dogfooding #1640/#1644/#1645 on
main(chain write-up: #1204 (comment)).What happened. On the Overview, the Routine work card has a
Run inpicker that scopes the per-project routines (#1640). I set it totf-1334-dogfood, clicked Run now (correctly scoped), opened the run, came back to the Overview — and the picker readgemstackagain, the first registered project. The next click fired a quick triage on gemstack, the real repo. It was stopped at 40 seconds with nothing committed, but it had already pushed an emptytf-triage-quickto the repo's origin — which is #1643's trap, now armed for the next gemstack triage until someone deletes the branch.Why it matters. The picker decides which repo spends quota and gets branches pushed, and it silently forgets the choice on the most common navigation there is (open a run, come back). The first project in the registry is the user's main repo, so the failure mode is always "the wrong click lands on the real codebase". The tooltip does name the project ("Starts one agent in gemstack …"), which is how it is catchable — but only by reading the tooltip before every click.
Fix shape. Remember the pick across navigations — the session store the rest of the dashboard already uses is enough; persisting it as a preference would also make it survive reloads. Defaulting to the project whose page the user came from would cover the open-run-and-return case on its own.
Repro. Overview → set
Run into any project but the first → open any run from the sidebar → Overview.