GIT section — TERMINAL closed vs TERMINAL open

Same workspace, same moment, in all three panels: the PR merged, so main is 1 ahead of the branch, and one later save is 1 ahead of main. The only thing that changes is whether a TERMINAL is attached. Panels 1 and 2 are the proposal; panel 3 is what the app renders today in that same situation.

1 · TERMINAL closed — unchanged
GIT
demo-voertuigen
Lukasz/waterstof (1 behind, 1 ahead of main, 0 drift)
in sync (21e8177 Save waterstof-vloot-profiel.vjob)
Update from main Reconcile Hard reset
Create PR Terminal

Counters are live: the backend fetched main and the branch on this poll.

2 · TERMINAL open — proposed
GIT
demo-voertuigen
Lukasz/waterstof (TERMINAL active - autosync off)
sync paused (21e8177 Save waterstof-vloot-profiel.vjob)
Update from main Reconcile Hard reset
Create PR Terminal

No number is shown that the backend didn't just verify. dirty, unpushed and the last commit stay live — they're true without a fetch — so pending-push still lights up during a terminal session. The three grey buttons are already disabled while a TERMINAL is attached today; nothing changes there.

3 · TERMINAL open — today, the bug
GIT
demo-voertuigen
Lukasz/waterstof (0 behind, 6 ahead of main, 0 drift)
in sync (21e8177 Save waterstof-vloot-profiel.vjob)
Update from main Reconcile Hard reset
Create PR Terminal

Numbers frozen at the last fetch before the terminal opened, and — because the stale drift and unpushed read 0 — a green in sync tick for a branch nobody has looked at in 20 minutes. This is the screen that was on demo1.

the two rows this mock is about — everything else is scaffold (the pod frame and the gitea logo box are drawn, not real)

Dial it in

330px
the GIT section is a resizable rail item — drag this to find where each wording starts clipping
amber #d97706 = the tier the existing “sync unknown” already uses