git panel improvements - commit history, pull, push - #77
Merged
Conversation
# Conflicts: # app/lib/widgets/markdown_preview.dart # app/lib/widgets/transcript/markdown_body.dart # bridge/CLAUDE.md # bridge/src/agent-core.ts # bridge/tests/submit-keystroke.test.ts
…starts The new git verbs reach argv positionally, and parseMessageFast skips Zod on that path — so a stash ref of "--index" pops a stash nobody tapped, a commit id of "--output=<path>" turns a read into a write, and "--help" hangs a non-interactive Bun.spawn forever holding the checkout. Refs are now matched against exactly what listStashes emits, shas against a sha pattern, and log paging is clamped. git:sync, git:stash-pop and git:stash-drop are tracked rather than fired: each holds the checkout as its child's cwd, and awaitGitRefreshes is what teardown waits on before git worktree remove. Untracked, a session deleted mid-push takes a Windows sharing violation and is undeletable forever. handleGitSync also answers a throw with a result — git:sync-result is not a replay type, so sending nothing left the panel's spinner turning for the life of the session. The app was applying replies it never correlated: any git:log page landed under the skip it was not asked for, and a late push result cleared a pull's spinner and reported the push's outcome as the pull's. Both now carry a guard. A probe's counts supersede the local pair in the frame reporting its verdict, git:sync-state is forced where the bus would dedup the re-push a resync exists to perform, and five widgets that started async work from void callbacks got detached() — two were carrying a WidgetRef across the await that disposes them. The status-cache suite failed about half the time: bootCore waited only for the first agent:status, so boot's post-refresh re-send landed mid-test. It now drains on the git:sync-state that closes that same .then(), which also makes the counts mean something — the re-send is deduped, so only the pull's own recompute can move them.
bharathm03
changed the title
bharathm03
added a commit
that referenced
this pull request
Sep 2, 2026
#77 added a Handler row to the agent panel's action menu, calling the arm flow by the name it had when that work started. This branch renamed that flow armWithSheet. The declaration and the new call site are in different files, so both sides merged clean and nothing failed until analyze -- the ordinary shape of a semantic conflict. The row is given the header shield's tooltip ordering while it is here: a refusal outranks the coverage notice, because coverage describes what an arm would GET and a refusal decides whether one can happen at all. Its arm path needed nothing -- it goes through armWithSheet, which asks about entitlement before it opens anything.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.