dsh-git-badge 0.16.1 → 0.17.1

package/CHANGELOG.md

@@ -10,6 +10,138 @@ npm. 0.6.0 is the first release recorded here.
 
 ## [Unreleased]
 
+## [0.17.1] - 2026-09-17
+
+### Fixed
+
+- **The branch, file-count and PR hovers open on the FIRST hover.** Those three
+  surfaces were only wrapped in the shell's `Tooltip` once the lazy `detail=1`
+  payload arrived. That primitive is uncontrolled — it has no `open` prop and
+  opens from a `mouseenter` it attaches to its child — so a wrapper mounted after
+  the pointer had already arrived could never open for that visit: the first hover
+  did nothing, and worked only after leaving and returning (or after hovering the
+  status mark had already warmed the cache). All four surfaces are now wrapped
+  from the first render, and a label whose detail is still in flight degrades to
+  the base response instead of claiming an empty list — the count restates the
+  file breakdown, the PR token names the PR. The branch's hover child also stays a
+  `span`, so the compare link appearing underneath a resting pointer cannot
+  remount it. The status mark's own card was never affected.
+
+### Changed
+
+- **Internal simplification pass, no user-facing change** (#52): one
+  `singleFlight` now backs the status cache and its in-flight coalescing, one
+  patch engine (`seam/patch.js`) backs both `seam/apply.js` and
+  `seam/postinstall.js`, and the server returns one `nextActions` shape
+  (`{actions, next}`) for the row's action list.
+
+## [0.17.0] - 2026-09-16
+
+### Added
+
+- **The PR token has its own hover: the commits in that pull request.** `PR#47 ✓`
+  now shows the commits on the branch that are not on the base
+  (`git log <base>..HEAD`, capped at 10 with "… and k more"), in the same line
+  format as the branch hover's list — hash, subject, compressed age, full-width
+  with ellipsis. Nothing else rides it: the token already states the number and
+  CI state, so the one question left is what is in it. Hover-gated with the rest
+  of `detail=1`, and the total reuses the ahead count already computed.
+- **`/gh clean [<path>...]` appears in the `/gh` menu behind a risk gate.** The
+  menu is built from status, not from this skill's prose, so the verb is offered
+  there whenever untracked files exist — always last, never as the badge's
+  suggested action, and carrying the host's own `RiskConfirmation`: Confirm
+  stays disabled until "I understand untracked files cannot be recovered" is
+  ticked. That gate names the risk; the agent then names the files
+  (`git clean -n`, quoted back) and asks again before `git clean -f`.
+- **A `/gh clean [<path>...]` verb, confirm-first by construction.** Removing
+  untracked files is the one operation with no reflog and no stash entry, so the
+  verb's first step is always `git clean -n -- <paths>` with the output quoted
+  back verbatim (the user approves the list, not the idea), then an explicit yes,
+  then `git clean -f -- <paths>` on named paths only. `-x`, `-d` and bare
+  `git clean -f` are forbidden — ignored files are often credentials and `-d`
+  turns one path into a tree. It stays out of the badge's ranked suggestions: a
+  destructive action the agent cannot infer intent for is never suggested, only
+  available on request.
+
+### Changed
+
+- **The session row's action token only appears when the session is idle.** A turn
+  in flight is exactly when a git suggestion is noise: the checkout is still
+  moving and the agent has not finished. The row reads its run state from the
+  shell's standard kit — `useSessions`, the same selector hook the workspace UI
+  itself uses — and renders nothing while that session is `running`. The filter is
+  on render, not on the fetch, so the row's hover line is unaffected. On a shell
+  that seeds no such hook the row behaves as before, and the console says which of
+  the two it got.
+- **The PR/CI token stops lagging behind the forge.** The forge read is
+  TTL-bounded and its refresh is request-driven, while an idle chip only asks
+  every 60s — so the old 90s `prTtlMs` silently suppressed every other poll, and
+  a pull request that appeared on GitHub with no local git event to announce it
+  could take ~2.5 minutes to show up. At 20s the TTL no longer outlives the
+  client's poll, so the first refresh after the forge changes picks it up and the
+  worst case falls to roughly the poll interval. Cost: up to one `gh pr view` per
+  open chip per minute, where it was one per ~2 minutes.
+- **The branch hover shows only the merge axis.** `upstream` and `sync` are gone
+  — they stated the same divergence against the branch's own remote, in arrows,
+  when `merge` already states it against the base branch in words. The `merge`
+  row now ALWAYS renders: `ready to merge`, `blocked: draft | review required |
+  checks failing`, `no pull request`, each joined with `N ahead, M behind main`
+  when those counts are known. A row that can be absent is a row the reader has
+  to reconstruct.
+- The commit cells lost their trailing colon (a later change had reintroduced it
+  after the earlier removal), so both hovers read `abc1234  subject · 2h ago`.
+- **One action list, built by the server.** Both halves used to derive the
+  pull/push/commit/pr conditions, and the copies drifted: the card once promoted
+  a client-only extra into its action row, and `/gh pr` was offered on the
+  default branch. The node half now publishes `actions` — the ranked rules in the
+  configured order with the top entry flagged `primary` (also served as `next`,
+  on every response), then the standing options (`pr view <n>`, `pr`, and the
+  flagged `clean`). `merge <n>` becomes a standing entry whenever the PR is
+  mergeable, so it now appears alongside a primary `push`/`pull` instead of only
+  when it wins the ranking. The client renders the list verbatim and keeps only
+  presentation — labels and the clean risk gate; `actions` rides the `pr=1`
+  payload only, so sidebar rows stay lean. Net: ~65 lines of duplicated client
+  rules deleted, and the conditions are unit-tested where the data lives.
+- **The upstream sync numbers ride the branch's hover and link.** `↑a ↓b` were
+  rendered inside the file count's names tooltip and outside the branch's compare
+  link, though they are the branch's standing against its upstream — so they now
+  sit with the branch name: same lineage hover, same compare-view link, and the
+  link's accessible name says "N ahead and M behind upstream". `✎n` keeps its own
+  names tooltip. Visible side effect: the arrows render before a paused-operation
+  token rather than after it.
+
+### Fixed
+
+- **The PR token's hover lines its commits up like the branch hover.** Both lists
+  now come from one renderer: a fixed-width monospace hash cell, so every
+  description starts on the same column and the list reads as a table. The PR
+  list had reused the card's label style, whose `minWidth` and `flex` only apply
+  inside a flex row — on a plain inline span they did nothing, so the hash sat
+  flush against its description with the columns ragged.
+- **The PR token's hover is reachable by hovering the token itself.** The commits
+  it lists are detail-only, and only the status mark and the branch name enabled
+  the `detail=1` fetch — so a pointer that went straight to `PR#47 ✓` had rested
+  on nothing that fetches, and its hover could not open until the mark had been
+  hovered first. The token is now its own detail gate, in both its linked and
+  plain forms.
+- **No more "open a pull request" on `main`, and the hover card shows only the
+  server's verdict.** Two layers disagreed: the node half correctly returned
+  nothing to do for a clean, synced default branch, while the client's extras
+  still offered `/gh pr` — and the card promoted that extra into its `action:`
+  row, so a checkout with nothing to do displayed a suggestion. The node half now
+  resolves the repository's default branch (`refs/remotes/origin/HEAD`,
+  TTL-cached and refreshed out of band like the fetch, so the hot path pays
+  nothing) and flags it on the response; the `pr` extra is suppressed when the
+  branch IS that default; and the card's action row reads the server's `next`
+  directly, leaving the extras to the `/gh` picker where they belong.
+- **The seam suite no longer writes into your real `~/.dsh/git-badge-seam`.**
+  One block spawned the postinstall hook without `SEAM_DATA_DIR`, so the hook
+  resolved its store to the machine's actual data directory: a test run
+  overwrote the real `backup-client.js`/`backup-index.js` and left a
+  `restart-pending.json` behind. It passed on CI only because the runner's
+  `$HOME` is writable — under a read-only `$HOME` it failed with EROFS. The
+  block now takes a throwaway data dir like the rest of the file.
+
 ## [0.16.1] - 2026-09-16
 
 ### Fixed
@@ -171,22 +303,18 @@ npm. 0.6.0 is the first release recorded here.
 
 ## [0.14.1] - 2026-09-15
 
+### Changed
+
 - **Skill alignment:** the `gh` skill gains an explicit handoff — one verb per
   invocation is its whole job; the multi-step PR lifecycle (review, merge,
   verify, cleanup) belongs to the `gh-pr` skill. The `gh-pr` skill states the
   mirror scope: one-shot verbs are `gh`'s, lifecycle is its own. The catalog
   stays global-only; repo conventions stay in `AGENTS.md`.
-
 - **The hover card is 33% wider** (360px → 480px) and its `action:` row now
   carries a trailing what-comment in git-comment convention — e.g.
   `action: /gh push  # push local commits to the remote` — so the row says
   what the invocation does, not just which invocation it is. The picker in the
   (+) menu shares the same descriptions.
-
-## [0.14.1] - 2026-09-15
-
-### Changed
-
 - **The chip's hover card top line is now an `action:` row** — the gh skill
   invocation the checkout justifies (e.g. `/gh push`), in the card's ordinary
   label/value layout, replacing the next-step line's why-plus-copy-chip. The
@@ -578,7 +706,20 @@ npm. 0.6.0 is the first release recorded here.
 - `detail=1` is annotated as having no consumer yet (the hover card remains
   pending). Its comment previously claimed `log -1` while the code ran `log -3`.
 
-[Unreleased]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/compare/v0.8.0...HEAD
+[Unreleased]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/compare/v0.17.0...HEAD
+[0.17.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.17.0
+[0.16.1]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.16.1
+[0.16.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.16.0
+[0.15.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.15.0
+[0.14.1]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.14.1
+[0.14.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.14.0
+[0.13.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.13.0
+[0.12.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.12.0
+[0.11.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.11.0
+[0.10.1]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.10.1
+[0.10.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.10.0
+[0.9.1]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.9.1
+[0.9.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.9.0
 [0.8.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.8.0
 [0.7.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.7.0
 [0.6.0]: https://github.com/Kevin-McIsaac/dsh-workspace-git-badge/releases/tag/v0.6.0

package/README.md

@@ -3,15 +3,15 @@
 Git status badges for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness):
 
 - **Input-row chip** — `● main ↑0 ↓2 ✎3` next to the access picker, showing the git state of the workspace the current conversation is attached to. Works on every install.
-- **Hover card** — rest a pointer on the chip for what won't fit: the file breakdown (`✎3` split into staged / unstaged / untracked), the last three commits, and the stash. Fetched only on hover, so the everyday badge pays nothing for it. Works on every install.
+- **Hover card** — rest a pointer on the chip for what won't fit: the file breakdown (`✎3` split into staged / unstaged / untracked), the last ten commits, and the stash. Fetched only on hover, so the everyday badge pays nothing for it. Works on every install.
 - **PR / CI token** — `● main ↑0 ↓2 PR#142 ✗` when the branch has a GitHub pull request, read through your own `gh` CLI (the plugin never handles a credential). The token **links to the PR** — it opens in a new tab, and underlines when you hover or focus it. Invisible when `gh` cannot answer: not installed, not logged in, no GitHub remote, offline or rate-limited all render the unchanged chip, and a token with no URL to link to stays plain text.
 - **Worktree-aware** — a conversation's directory is fixed when it is created, so a conversation that does its work in a linked `git worktree` would otherwise keep reporting the main checkout. The session registers its checkout (`npx dsh-git-badge-checkout <path>`, run by the git-worktree and `/gh checkout` paths), and the badge describes **that worktree** instead — its branch, counts, tree mark and PR/CI token (`🌳 chore/global-skills-tiering ↑0 ↓2 PR#391 ✓` rather than `● main`). The hover card names the tree in a `worktree` row and adds a `checkout` row with the conversation's own directory, so the main checkout's branch and dirty state stay one hover away. Registrations are advisory: git's own worktree list validates the path, entries expire after 24h, and a workspace-targeted row always reports the checkout the registry owns.
-- **Sidebar session-row action token** — each session row shows the ONE thing that conversation needs from you, or nothing at all: `merge`, `fix CI`, `review`, `resolve`, `pull`, `push`. It is triage rather than status: `merge` appears only when GitHub itself reports `mergeStateStatus: CLEAN`, and every waiting state (draft, blocked, behind, checks still running) stays silent. Hovering the row adds a line naming the checkout and the pull request the action refers to. The token floats to the right of the row, is set heavier than the timestamp beside it, and is coloured by how much it needs you — red for a conflict or a failing build, amber for a requested review, green for `merge`, quiet grey for routine sync. Requires the `sidebar.workspaces.sessionRow` seam; without it the plugin degrades to chip-only and logs what's active to the browser console.
+- **Sidebar session-row action token** — each session row shows the ONE thing that conversation needs from you, or nothing at all: `merge`, `fix CI`, `review`, `resolve`, `pull`, `push`. It is triage rather than status: `merge` appears only when GitHub itself reports `mergeStateStatus: CLEAN`, and every waiting state (draft, blocked, behind, checks still running) stays silent. Hovering the row adds a line naming the checkout and the pull request the action refers to. The token floats to the right of the row, is set heavier than the timestamp beside it, and is coloured by how much it needs you — red for a conflict or a failing build, amber for a requested review, green for `merge`, quiet grey for routine sync. It appears only when the session is **idle** — while a turn is running the row stays quiet, because the checkout is still moving and a suggestion would describe a state that is about to change. Requires the `sidebar.workspaces.sessionRow` seam; without it the plugin degrades to chip-only and logs what's active to the browser console.
 - **Nothing on workspace rows.** A workspace cannot know which worktree its conversations are using, so a per-workspace badge could only guess or report the main checkout. The seam is on the session row for that reason.
 
 The leading **mark** belongs to the input chip: a circle filled with the status colour, or a **tree** when the checkout is a linked `git worktree`. The sidebar row deliberately carries no mark — see the row bullet above, where one word does the job a colour cannot. (`●`/`🌳` stand in for it here — it is a drawn SVG so that it can take the theme's status colours.)
 
-Event-driven freshness: working trees are watched and updates push over SSE — badges flip within ~1s of any commit, stage, or edit, including inside a linked worktree the session registered. One `git status --porcelain=v2` per sample, shared by every surface pointing at the same checkout, plus at most one `gh` read per repository-and-branch per ~90s. The status API takes **no path**: the caller passes a session id (chip and sidebar rows) or a workspace id, and the server resolves the directory itself.
+Event-driven freshness: working trees are watched and updates push over SSE — badges flip within ~1s of any commit, stage, or edit, including inside a linked worktree the session registered. One `git status --porcelain=v2` per sample, shared by every surface pointing at the same checkout, plus at most one `gh` read per repository-and-branch per ~20s. The status API takes **no path**: the caller passes a session id (chip and sidebar rows) or a workspace id, and the server resolves the directory itself.
 
 Diagrams, the hover card's full field list and a walkthrough for git newcomers live
 in the [repo README](https://github.com/Kevin-McIsaac/dsh-workspace-git-badge) —