gh-glance 0.19.1 → 0.19.3

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.19.3] - 2026-11-12
+
+### Fixed
+
+- A single contradictory rate-limit reading no longer pauses all panes until
+  the hourly reset. Rejected budget readings now show a failed budget check
+  that retries automatically instead of corrupt coordination state.
+
+## [0.19.2] - 2026-11-06
+
+### Changed
+
+- The fifth section is now named `Events` (`5:Events`) at every width that shows
+  a name, in the tab bar, its view title and the help text. Narrow panes no longer switch it
+  to a different word (`Status`, earlier `Notices`). Full tab names now fit
+  in panes 7 columns narrower.
+- A wait that ends in under two minutes no longer counts toward the `Events`
+  unread badge. The view still lists it. Each wait is measured on its own, so
+  repeated short waits do not add up. Problems, causes that need action and
+  longer waits count as before.
+
 ## [0.19.1] - 2026-11-04
 
 ### Changed
@@ -1430,7 +1451,10 @@ engineering, security, QA and UX. What follows is what changed as a result.
 - The `main` field from `package.json`. It advertised the file as importable,
   but importing it took over the terminal or exited the host process.
 
-[Unreleased]: https://github.com/juan294/gh-glance/compare/v0.19.0...HEAD
+[Unreleased]: https://github.com/juan294/gh-glance/compare/v0.19.3...HEAD
+[0.19.3]: https://github.com/juan294/gh-glance/compare/v0.19.2...v0.19.3
+[0.19.2]: https://github.com/juan294/gh-glance/compare/v0.19.1...v0.19.2
+[0.19.1]: https://github.com/juan294/gh-glance/compare/v0.19.0...v0.19.1
 [0.19.0]: https://github.com/juan294/gh-glance/compare/v0.18.1...v0.19.0
 [0.18.1]: https://github.com/juan294/gh-glance/compare/v0.18.0...v0.18.1
 [0.18.0]: https://github.com/juan294/gh-glance/compare/v0.17.1...v0.18.0

package/README.md

@@ -20,15 +20,15 @@ pane next to your editor) where you want an always-on glance at repo activity
 without switching to the browser.
 
 ```
-[1:Actions (4)]  2:Issues   3:PRs   4:Security   5:Status
+[1:Actions (4)]   2:Issues    3:Pull requests    4:Security    5:Events
 ───────────────────────────────────────────────────────────────────────────
 ╭─ Actions · owner/repo ──────────────────────────────────────────────────╮
 │     TITLE                  │WORKFLOW  │BRANCH        │TIME   │UPDATED   │
 │ ─────────────────────────────────────────────────────────────────────── │
-│ >+  ci: pin actions to com… #443 CI    develop        1m20s   93d ago   │
-│  x  fix: restore the prima… #442 Code… develop        1m28s   93d ago   │
-│  +  chore: bump dependenci… #441 CI    dependa…int-10 30s     93d ago   │
-│  -  docs: update the readme #440 CI    develop        15s     94d ago   │
+│ >+  ci: pin actions to com… #443 CI    develop        1m20s   96d ago   │
+│  x  fix: restore the prima… #442 Code… develop        1m28s   96d ago   │
+│  +  chore: bump dependenci… #441 CI    dependa…int-10 30s     96d ago   │
+│  -  docs: update the readme #440 CI    develop        15s     97d ago   │
 │                                                                         │
 │                                                                         │
 ╰──────────────────────────────────────────────────────────────── 4 of 4 ─╯
@@ -47,9 +47,9 @@ without switching to the browser.
 > red" is answerable without switching to that tab — an `x` means the tab's
 > latest fetch failed, and a `?` in place of the Security count means its
 > endpoints could not be read, which is not the same as there being nothing to
-> report. `5:Status` (`5:Notifications` when the full names fit) gains an
+> report. `5:Events` gains an
 > unread count such as `(3)` when waits or problems arrive while it is closed;
-> see [Notifications](#notifications).
+> see [Events](#events).
 
 <!-- contract:allow-emoji -- the check/cross above stand in for Nerd Font
      Octicons the app actually draws; they are literal examples, not decoration. -->
@@ -89,7 +89,7 @@ current.
   Security -- see [Limitations](#limitations).
 - Tab bar with live counts, pinned to the top of the pane above a divider,
   switchable via `1`-`5`, arrow keys, or `Tab`/`Shift+Tab`
-- **[Notifications](#notifications)** -- `5` opens the pane's status history:
+- **[Events](#events)** -- `5` opens the pane's status history:
   automatic waits, failed refreshes, Security source notes, cleared causes and
   GitHub's own platform status. Only causes that need you stay above a table
 - Adjustable full-table columns, with visible header grips, a keyboard width
@@ -307,8 +307,8 @@ stdout isn't a terminal rather than streaming redraw frames into a pipe.
 | Key | Action |
 |---|---|
 | `1` `2` `3` `4` | Jump to Actions / Issues / Pull Requests / Security |
-| `5` | Open Notifications, the pane's status history. `↑` / `↓` and `PgUp` / `PgDn` scroll it, `r` checks GitHub's status page, and `1`-`4` or `Esc` return to a section. |
-| `←` / `→` | Previous / next tab (Notifications is the fifth position) |
+| `5` | Open Events, the pane's status history. `↑` / `↓` and `PgUp` / `PgDn` scroll it, `r` checks GitHub's status page, and `1`-`4` or `Esc` return to a section. |
+| `←` / `→` | Previous / next tab (Events is the fifth position) |
 | `Tab` / `Shift+Tab` | Next / previous tab |
 | `↑` / `↓` or `j` / `k` | Move the cursor between rows |
 | `PgUp` / `PgDn` | Move a page at a time |
@@ -328,12 +328,12 @@ stdout isn't a terminal rather than streaming redraw frames into a pipe.
 | `?` | Open or close contextual help; `n` / `p` moves through its pages |
 | `q` / `Esc` / `Ctrl+C` | Quit from ordinary navigation; `Esc` leaves feature views, editors and width mode. While editing a query or range, `q` is text and `Ctrl+C` quits. |
 
-### Notifications
+### Events
 
 Lines above a table appear only when you must act: a local coordination store
 that needs `gh-glance --doctor`, a lost GitHub login, an inaccessible
 repository, or a repeated request limit that waits for `r`. Everything else
-goes to the fifth section, `5:Notifications`: automatic waits (budget checks,
+goes to the fifth section, `5:Events`: automatic waits (budget checks,
 quota pacing, other panes), failed refreshes with their raw text, Security
 sources that are not enabled or not available, refreshes, and the moment each
 cause cleared. The table no longer moves when a wait starts or ends.
@@ -364,9 +364,11 @@ only a proxy reaches the internet the row reads "GitHub status unavailable",
 and `GH_GLANCE_GITHUB_STATUS=off` turns it off.
 
 The tab label shows how many waits and problems arrived since you last opened
-the view, for example `5:Notifications (3)`: red when any is a problem or needs
-action, yellow when all are waits. Routine refreshes never change the badge, so
-an idle pane still redraws nothing. The status bar keeps its one-row state
+the view, for example `5:Events (3)`: red when any is a problem or needs
+action, yellow when all are waits. A wait that ends in under two minutes stops
+counting at that point, although the view still lists it. Each wait is measured
+on its own, so repeated short waits do not add up. Routine
+refreshes never change the badge, so an idle pane still redraws nothing. The status bar keeps its one-row state
 (`Paused`, `Stale`, ...) as before.
 
 ### Adjusting column widths
@@ -678,7 +680,7 @@ Environment variables work too, and the flags take precedence:
 | `GH_TOKEN`, `GITHUB_TOKEN`, `GH_ENTERPRISE_TOKEN`, `GITHUB_ENTERPRISE_TOKEN` | Used by the default `gh` provider with `gh`'s host-specific precedence. gh-glance never logs or stores the raw values. One-way credential digests keep private rows access-partitioned; credentials GitHub verifies as the same principal share its quota ledger. App-provider children remove these variables before setting their memory-only installation token. |
 | `GH_CONFIG_DIR` | Selects `gh`'s account configuration and contributes its normalized identity to the cache and governor namespaces. Separate values can isolate simultaneous panes on different accounts; see [No account pinning](#limitations). |
 | `GH_GLANCE_REFRESH=<seconds>` | Minimum active-tab poll interval, 2-3600. Sets the floor for every pane in a shell; `--refresh` takes precedence. See [Rate limit](#rate-limit). |
-| `GH_GLANCE_GITHUB_STATUS=off` | Turn off the GitHub platform status check in Notifications. An `http(s)` URL instead points it at another Statuspage `summary.json` endpoint. Any other value also turns it off and says so in the view. |
+| `GH_GLANCE_GITHUB_STATUS=off` | Turn off the GitHub platform status check in Events. An `http(s)` URL instead points it at another Statuspage `summary.json` endpoint. Any other value also turns it off and says so in the view. |
 | `GH_GLANCE_ICONS=unicode` | Unicode status glyphs and single-cell text substitutes for Nerd Font row icons |
 | `GH_GLANCE_ICONS=ascii` | ASCII-only status and row icons |
 | `GH_GLANCE_NO_ANIMATION=1` | Stop status and run-state motion. Semantic words such as Watching, Checking, and Paused still report what is happening. |
@@ -990,7 +992,7 @@ loads the saved rows for that same target immediately. Their age remains
 explicit through the `stale` label, and the footer still reports the current
 hold; cached data never turns a failure into a false success. A rate limit
 retries automatically, so it does not take rows from the table: a sustained
-hold is listed in [Notifications](#notifications) with its cause (Core,
+hold is listed in [Events](#events) with its cause (Core,
 GraphQL, or the tab that hit it) and next automatic retry, and the badge turns
 yellow. Only a hold that needs you, such as a repeated limit that waits for
 `r`, stays above the table with its action and the age of the last complete
@@ -1107,7 +1109,7 @@ monitor makes no GitHub request or coordination write.
   Advanced Security](https://docs.github.com/en/code-security/getting-started/github-security-features).
   On repos/plans without it, `gh-glance` doesn't crash or spam errors -- it
   lists each disabled source, such as `Code scanning: not enabled (needs GitHub
-  Advanced Security)`, in [Notifications](#notifications) instead of above the
+  Advanced Security)`, in [Events](#events) instead of above the
   table (when no alerts are shown, the Security panel collapses them into one
   line such as `Code scanning, Secret scanning: not enabled here`), and still
   displays whatever it *can* get (Dependabot alerts work independently of
@@ -1196,11 +1198,11 @@ GH_GLANCE_ICONS=ascii gh-glance
 | `GraphQL: Could not resolve to a Repository...` in older gh-glance versions | The response has the same ambiguity: a missing or renamed target, or a private repository not visible to the active account. Run `gh-glance --doctor --probe`. |
 | Actions says `not available for this repository` while Repository access is `ok` | The repository resolved, but that endpoint is unavailable; inspect the corresponding `--doctor --probe` block. |
 | Row icons are blank boxes | Your terminal font is not a Nerd Font. Use `GH_GLANCE_ICONS=unicode`. |
-| Notifications lists a Security "not enabled" note | Code scanning and secret scanning need GitHub Advanced Security. Dependabot alerts work independently. The note appears only when the feature genuinely is unavailable: auth, SSO and network failures show the real error instead. |
+| Events lists a Security "not enabled" note | Code scanning and secret scanning need GitHub Advanced Security. Dependabot alerts work independently. The note appears only when the feature genuinely is unavailable: auth, SSO and network failures show the real error instead. |
 | `none of the git remotes ... point to a known GitHub host` | `gh` is not authenticated for that host. Run `gh auth login --hostname <host>`. |
 | Security tab empty on an enterprise host in an older gh-glance version | Older versions could route alert endpoints separately. Current gh-glance routes every API call and the governor to one effective host; use `--repo host/owner/name`, `GH_HOST`, or a qualified `GH_REPO`, then confirm the resolved host with `--doctor`. |
 | Tabs start failing after working for a while | The enterprise SAML session lapsed. Re-authorize in the browser; the dashboard recovers within about 30 seconds. Run `gh-glance --doctor --probe` to confirm. |
-| A tab's count is red | That tab's last fetch failed. The error is listed in Notifications (`5`); when it needs you (login, repository or endpoint access), it also stays above that tab's table, translated into what to do about it where `gh-glance` recognises the failure. |
+| A tab's count is red | That tab's last fetch failed. The error is listed in Events (`5`); when it needs you (login, repository or endpoint access), it also stays above that tab's table, translated into what to do about it where `gh-glance` recognises the failure. |
 | Security tab shows `?` instead of a number | The alert endpoints could not be read at all -- an expired SAML session, a token without `security_events`, or an org OAuth restriction. `?` means "unknown", not "zero"; run `gh-glance --doctor --probe` to see which probe failed and how it was classified. |
 | `Watching` with `next 2m` | The active tab has a shared budget probe or safe grant scheduled. The interval names this grant only; it is not a recurring polling interval. Pressing `r` raises safe priority but cannot bypass the lane or reserve. |
 | `Shared` | This pane is using a generation acquired for matching local subscribers. This is coalescing, not quota scarcity. |
@@ -1208,7 +1210,7 @@ GH_GLANCE_ICONS=ascii gh-glance
 | `Paused` without a reset time | Budget or coordinator evidence is unknown, corrupt, locked, or unwritable. No data call is started. Run `gh-glance --doctor`; also check the config directory permissions and whether another live process owns its private lock. |
 | `--doctor` reports an acquisition lock as `orphaned` | A dead owner or an aged incomplete lock record was found. A running pane retries recovery through the private lock protocol; plain doctor only inspects it. If the state does not change, inspect the reported lock age and the config directory permissions. |
 | `--doctor` reports an acquisition lock as `busy` | A live or unconfirmed owner, or a recent incomplete lock record, is present. Keep the other pane running and check again after the reported age advances; plain doctor does not steal a lock. |
-| Rows stay old while the footer shows a coordination reason | The rows remain last-known-good data. The reason persists until a valid shared snapshot or completed cleanup clears that acquisition failure; a healthy rate-budget probe alone does not prove that acquisition succeeded. The footer shows the source age and Notifications (`5`) gives the longer reason. |
+| Rows stay old while the footer shows a coordination reason | The rows remain last-known-good data. The reason persists until a valid shared snapshot or completed cleanup clears that acquisition failure; a healthy rate-budget probe alone does not prove that acquisition succeeded. The footer shows the source age and Events (`5`) gives the longer reason. |
 | A failing tab seems to have stopped retrying | Recognized endpoint failures back off rather than re-spawning `gh` at the floor. Press `r` to request a higher-priority retry, or `R` to also clear the endpoint backoff; either way the retry waits for a safe grant, so the tab remains Watching or Paused. |
 | `unknown argument: -v` | `-v` used to mean `--version` and no longer does, because this CLI also has `--verbose`. Use `--version` or `--verbose` explicitly. |
 | Cached rows plus `Paused`, `Stale`, or `Disconnected` | The rows are last-known-good data while the live source is blocked, overdue, or unavailable. A cache read never advances source success. The footer never calls stale or disconnected rows `Watching`. |

package/index.mjs

@@ -6163,13 +6163,14 @@ function budgetFromObservation(raw, previous, nowMs, {
   ) return { status: "invalid" };
   const epoch = `${normalized.limit}:${normalized.resetMs}`;
   // Endpoint responses can carry cached or endpoint-specific rate headers.
-  // They may refine the counter inside the epoch established by its claimed
-  // observer, but only that observer may move the resource into a new epoch.
+  // Only the claimed observer may move the epoch in either direction. A
+  // backwards move must be newer than the stored evidence to replace it.
   if (!allowEpochChange && (!previous || previous.epoch !== epoch)) {
     return { status: "ignored", epoch };
   }
   if (previous) {
-    if (normalized.resetMs < previous.resetMs) return { status: "ignored" };
+    if (normalized.resetMs < previous.resetMs &&
+        (!allowEpochChange || receivedAt <= previous.observedAt)) return { status: "ignored" };
     if (budgetEpoch(previous) === epoch && normalized.used < previous.used) {
       if (!allowEpochChange) return { status: "ignored" };
       // The claimed observer can lag a newer endpoint response within the
@@ -6272,7 +6273,7 @@ function publishProbe(scope, leaseId, nonce, budgets, nowMs, resource) {
         clearProvenBlock: true,
         allowEpochChange: true,
       });
-      if (observed.status === "invalid") return { ok: false, reason: "corrupt" };
+      if (observed.status === "invalid") return { ok: false, reason: "probe-failed" };
       if (observed.status !== "ignored") {
         // The observer's own cost is local spend. Left out, the external-factor
         // reconciliation below attributes it to other clients, and the governor
@@ -6288,7 +6289,7 @@ function publishProbe(scope, leaseId, nonce, budgets, nowMs, resource) {
         if (observed.epochChanged && state.epochs[resource] !== null) resetResources.push(resource);
       }
     }
-    if (changedResources.length === 0) return { ok: false, reason: "corrupt" };
+    if (changedResources.length === 0) return { ok: false, reason: "probe-failed" };
     if (!retireClaimedQuiescentDebt(state, resource, claim)) {
       return ACCOUNTING_OVERFLOW;
     }
@@ -12362,7 +12363,7 @@ const { version } = JSON.parse(readFileSync(new URL("./package.json", import.met
 // this file already applies to argv vectors and to classify().
 const KEY_TABLE = [
   ["1 2 3 4", "Actions / Issues / Pull requests / Security"],
-  ["5", "Notifications: status history; Up / Down scroll, r checks GitHub status, Esc returns"],
+  ["5", "Events: status history; Up / Down scroll, r checks GitHub status, Esc returns"],
   ["Left / Right", "Previous / next tab"],
   ["Tab / Shift+Tab", "Next / previous tab"],
   ["Up / Down, j / k", "Move the cursor between rows"],
@@ -12530,7 +12531,7 @@ Environment:
                             (--refresh takes precedence)
   GH_GLANCE_GITHUB_STATUS=off
                             Turn off the githubstatus.com check in
-                            Notifications (an http(s) URL replaces the endpoint)
+                            Events (an http(s) URL replaces the endpoint)
   GH_GLANCE_ICONS=unicode   Unicode status glyphs and text row substitutes
   GH_GLANCE_ICONS=ascii     ASCII-only status and row icons
   GH_GLANCE_NO_ANIMATION=1  Stop motion; semantic status words remain
@@ -16828,7 +16829,7 @@ function contextHelpPages({ view, target, tab, remoteSetup = false }, keys = key
     issues: "Issues shows open issues in the selected repository.",
     prs: "Pull requests shows open requests to merge changes into the selected repository.",
     security: "Security shows alerts returned by the checked sources; unavailable sources can hide alerts.",
-    notifications: "Notifications lists status events for this pane: waits, refreshes, failures and cleared causes.",
+    notifications: "Events lists what happened in this pane: waits, refreshes, failures and cleared causes.",
   };
   const title = remoteSetup ? "No GitHub remote found" : view.title;
   const action = remoteSetup ? "Close help with ?, then Enter to start gh repo create; or restart with gh-glance --repo owner/name."
@@ -17026,6 +17027,9 @@ const VERDICT_NOTICE_LEVELS = Object.freeze({
   "auth-problem": "action", unavailable: "action", "no-remote": "action", "rate-limited": "wait",
 });
 const NOTIFICATION_LOG_MAX = 500;
+// A wait that ends within this long left nothing to look at: it stays in the
+// history but does not count as unread. Each episode is measured on its own.
+const SHORT_WAIT_MS = 120_000;
 // Tabs whose requests draw on each rate resource; a cause on that resource
 // holds them up. The cost table is fixed, so this is computed once.
 const NOTICE_RESOURCE_TABS = Object.freeze(Object.fromEntries(RATE_RESOURCES.map((resource) =>
@@ -17058,7 +17062,8 @@ function fetchErrorLevel(error) {
 // one affecting the same tab, came after it); an ended entry never reopens, so a recurring condition reads
 // as a new episode. An entry the bound already dropped cannot be ended, so its
 // "Cleared" line is silently skipped. Earlier-session history is context, not
-// news, so it never raises the badge.
+// news, so it never raises the badge, and neither does a short wait that has
+// already cleared.
 function createNotificationLog({ max = NOTIFICATION_LOG_MAX, now = Date.now } = {}) {
   const entries = []; // oldest first
   let nextId = 1;
@@ -17126,6 +17131,7 @@ function createNotificationLog({ max = NOTIFICATION_LOG_MAX, now = Date.now } =
     let yellow = false;
     for (const entry of entries) {
       if (entry.level === "info" || entry.source === EARLIER_SESSION_SOURCE || entry.id <= seenId) continue;
+      if (entry.level === "wait" && entry.endedAt !== null && entry.endedAt - entry.firstAt < SHORT_WAIT_MS) continue;
       unread += 1;
       if (entry.level === "wait") yellow = true;
       else red = true;
@@ -17980,14 +17986,16 @@ const MIN_TABLE_WIDTH = Math.max(...TABS.map((t) => minimumWidthFor(t.header)));
 const MIN_COMPACT_WIDTH = Math.max(...TABS.map((t) => minimumWidthFor(t.compactHeader)));
 
 // The tab bar is laid out independently of the table. Full labels are used
-// whenever they fit the measured bar (~97 columns with counts on every tab, less
+// whenever they fit the measured bar (~90 columns with counts on every tab, less
 // with fewer); short labels need ~76. Once the bar has dropped to short labels,
 // full ones return only with this many spare columns, so a pane parked on the
 // boundary, or a count gaining a digit, does not flip labels back and forth and
 // defeat the unchanged-frame optimization. Below the short width the bar drops
 // names and keeps digits and counts (see tabBarEntries).
 const TAB_LABEL_HYSTERESIS = 4;
-const NOTIFICATIONS_LABEL = Object.freeze({ full: "Notifications", short: "Status" });
+// One name at every tier: a label that changes with the pane width reads as a
+// different feature.
+const NOTIFICATIONS_LABEL = Object.freeze({ full: "Events", short: "Events" });
 
 function tabFailureSuffix({ count, failed, brokenCI }) {
   if (count == null) return failed ? " x" : "";
@@ -23663,6 +23671,7 @@ export {
   inspectGovernor,
   governorHealth,
   refreshSharedBudget,
+  refreshResourceBudget,
   readCoreBudget,
   readSharedBudgetSources,
   safe,
@@ -23876,6 +23885,7 @@ export {
   cleanupQueueForResource,
   presentRecovery,
   RECOVERY_COPY,
+  HARD_STORAGE_REASONS,
   NOTICE_LEVELS,
   NOTIFICATION_LOG_MAX,
   noticeLevel,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gh-glance",
-  "version": "0.19.1",
+  "version": "0.19.3",
   "description": "A live-refreshing GitHub dashboard for your terminal: Actions, Issues, Pull Requests, and Security alerts in one narrow pane",
   "type": "module",
   "bin": {