ctrlrelay 0.16.0__tar.gz → 0.16.2__tar.gz

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/CHANGELOG.md

@@ -7,6 +7,50 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.16.2] - 2026-11-01
+
+Status page changes only. **No config edit is required.**
+
+### Added
+
+- The Today counters (dispatched, PRs opened, merged, failed, blocked,
+  messages sent) are buttons: each opens today's events of that kind under
+  the counters. A failed run shows why (exit code, the run's summary and its
+  stored output), a blocked one the question, PRs link to the PR. New
+  `/api/events?kind=<kind>&day=today` (#271, closes #257)
+
+### Changed
+
+- A GitHub API bucket whose reset time has passed since the last read shows
+  as "refilled at <time>, not read since" instead of "unknown"; search,
+  which refills every minute, usually shows that way (#272)
+- More space under the header and between the Machines strip and "Who has
+  what" (#271)
+
+### Fixed
+
+- The live feed now scrubs credential shapes from event details: a
+  question an agent asked could show a token on the page (#271)
+
+## [0.16.1] - 2026-11-01
+
+Fixes the chat bridge, which did not start on 0.16.0. **No config edit is
+required.** If you upgraded to 0.16.0, upgrade to this.
+
+### Fixed
+
+- `ctrlrelay bridge start` (what the bridge service runs) exited at startup
+  on 0.16.0 with `BridgeServer.__init__() missing 1 required keyword-only
+  argument: 'node'`, for Telegram and Mattermost alike, so chat questions
+  and answers stopped. It now passes the machine's name and the shared
+  setting, like `python -m ctrlrelay.bridge` (#265)
+
+### Changed
+
+- The bridge's systemd unit is described as "ctrlrelay chat bridge
+  (Telegram or Mattermost)", and the docs call it the chat bridge. An
+  installed unit keeps its old description until it is re-rendered (#266)
+
 ## [0.16.0] - 2026-11-01
 
 Several machines can now run ctrlrelay on one GitHub account, each claiming
@@ -1957,7 +2001,9 @@ pipeline).
   per-phase implementation plans (Phase 0 through Phase 4).
 - `docs/Claude_Code_Project_Guide.md` — project development guide.
 
-[Unreleased]: https://github.com/AInvirion/ctrlrelay/compare/v0.16.0...HEAD
+[Unreleased]: https://github.com/AInvirion/ctrlrelay/compare/v0.16.2...HEAD
+[0.16.2]: https://github.com/AInvirion/ctrlrelay/compare/v0.16.1...v0.16.2
+[0.16.1]: https://github.com/AInvirion/ctrlrelay/compare/v0.16.0...v0.16.1
 [0.16.0]: https://github.com/AInvirion/ctrlrelay/compare/v0.15.0...v0.16.0
 [0.15.0]: https://github.com/AInvirion/ctrlrelay/compare/v0.14.0...v0.15.0
 [0.14.0]: https://github.com/AInvirion/ctrlrelay/compare/v0.13.0...v0.14.0

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ctrlrelay
-Version: 0.16.0
+Version: 0.16.2
 Summary: Local-first orchestrator for headless coding agents across multiple GitHub repos
 Project-URL: Homepage, https://github.com/AInvirion/ctrlrelay
 Project-URL: Documentation, https://ainvirion.github.io/ctrlrelay/
@@ -128,11 +128,11 @@ are on the roadmap (see [Roadmap](#roadmap)).
       new issue  │       │  blocked session
                  │       │
       ┌──────────▼──┐  ┌─▼───────────────────┐
-      │ dev pipeline│  │ Telegram bridge     │
-      │ in worktree │  │ (socket ↔ bot API)  │
+      │ dev pipeline│  │ chat bridge         │
+      │ in worktree │  │ (socket ↔ chat API) │
       │ agent CLI   │  └──────────┬──────────┘
       └──────┬──────┘             │
-             │ PR opened          │ DM you
+             │ PR opened          │ asks you
              ▼                    ▼
       ┌────────────┐         ┌─────────┐
       │ PR watcher │         │   You   │
@@ -207,7 +207,7 @@ Run as a supervised daemon (launchd on macOS / systemd on Linux) — see
 
 - [Getting started][docs-start]
 - [Configuration][docs-config]
-- [Telegram bridge][docs-bridge]
+- [Chat bridge (Telegram or Mattermost)][docs-bridge]
 - [Feedback loop][docs-feedback]
 - [CLI reference][docs-cli]
 - [Operations (launchd / systemd / scheduled jobs)][ops-docs]

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/README.md

@@ -87,11 +87,11 @@ are on the roadmap (see [Roadmap](#roadmap)).
       new issue  │       │  blocked session
                  │       │
       ┌──────────▼──┐  ┌─▼───────────────────┐
-      │ dev pipeline│  │ Telegram bridge     │
-      │ in worktree │  │ (socket ↔ bot API)  │
+      │ dev pipeline│  │ chat bridge         │
+      │ in worktree │  │ (socket ↔ chat API) │
       │ agent CLI   │  └──────────┬──────────┘
       └──────┬──────┘             │
-             │ PR opened          │ DM you
+             │ PR opened          │ asks you
              ▼                    ▼
       ┌────────────┐         ┌─────────┐
       │ PR watcher │         │   You   │
@@ -166,7 +166,7 @@ Run as a supervised daemon (launchd on macOS / systemd on Linux) — see
 
 - [Getting started][docs-start]
 - [Configuration][docs-config]
-- [Telegram bridge][docs-bridge]
+- [Chat bridge (Telegram or Mattermost)][docs-bridge]
 - [Feedback loop][docs-feedback]
 - [CLI reference][docs-cli]
 - [Operations (launchd / systemd / scheduled jobs)][ops-docs]

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/SECURITY.md

@@ -25,7 +25,7 @@ mitigation within **14 days** for high-severity issues.
 In-scope:
 
 - The `ctrlrelay` CLI and its pipelines (`dev`, `secops`, scheduled jobs).
-- The Telegram bridge and socket transport.
+- The chat bridge (Telegram or Mattermost) and socket transport.
 - Anything in `src/` and `config/`.
 
 Out-of-scope:

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/docs/cli.md

@@ -27,7 +27,7 @@ ctrlrelay [--version] <command> ...
 | `ctrlrelay status` | Show active locks and the 5 most-recent sessions. |
 | `ctrlrelay config ...` | Configuration helpers. |
 | `ctrlrelay skills ...` | Skill discovery / audit. |
-| `ctrlrelay bridge ...` | Manage the Telegram bridge daemon. |
+| `ctrlrelay bridge ...` | Manage the chat bridge daemon (Telegram or Mattermost). |
 | `ctrlrelay run ...` | Run a pipeline interactively. |
 | `ctrlrelay ci ...` | CI helpers used by the dev pipeline prompt. |
 | `ctrlrelay poller ...` | Manage the issue-poller daemon. |
@@ -128,7 +128,7 @@ Lists discovered skills as a table (name, path).
 
 ## `ctrlrelay bridge`
 
-See [Telegram bridge]({{ '/bridge/' | relative_url }}) for the full setup walkthrough.
+See [Chat bridge]({{ '/bridge/' | relative_url }}) for the full setup walkthrough.
 
 ### `bridge start`
 

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/docs/configuration.md

@@ -302,7 +302,7 @@ transport:
 | Key | Type | Required | Default | Description |
 |---|---|---|---|---|
 | `type` | enum | no | `"file_mock"` | One of `"telegram"`, `"mattermost"`, `"file_mock"`. |
-| `telegram` | object | required when `type=telegram` | — | Telegram bridge settings — see below. |
+| `telegram` | object | required when `type=telegram` | — | Telegram settings — see below. |
 | `mattermost` | object | required when `type=mattermost` | — | Mattermost bridge settings — see below. |
 | `file_mock` | object | required when `type=file_mock` | — | Local-file fake transport, used for tests/dev. |
 
@@ -321,7 +321,7 @@ reach anybody.
 | `question_ttl_seconds` | int | `172800` (48h) | How long an **unanswered** question stays routable before it is retired. Minimum `3600`. Without a ceiling those rows never die — a question whose PR was merged by hand weeks ago stays a live target for an orphan reply. The hourly `question_expiry_sweeper` also retires a question early once every issue/PR it cites is closed or merged. |
 | `question_retention_days` | int | `90` | How long a **finished** question (expired, or answered and resumed) is kept before the hourly sweeper deletes it. Minimum `1`. Open questions are never deleted. The kept history is what lets a re-asked question be marked as a repeat. |
 
-See [Telegram bridge]({{ '/bridge/' | relative_url }}) for the full setup walkthrough.
+See [Chat bridge]({{ '/bridge/' | relative_url }}) for the full setup walkthrough.
 
 ### transport.mattermost
 

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/docs/development.md

@@ -52,7 +52,7 @@ pytest --cov=src/ctrlrelay --cov-report=term-missing
 `pyproject.toml` sets `pythonpath = ["src"]` and `testpaths = ["tests"]` so
 pytest finds the package without an extra install step on a fresh checkout.
 
-The Telegram bridge tests stub the network — no real bot token is required to
+The chat bridge tests stub the network — no real bot token is required to
 run the suite. Tests that exercise the dev / secops pipelines use the
 `file_mock` transport so they stay hermetic.
 
@@ -112,7 +112,7 @@ ctrlrelay/
 │   ├── cli.py                   # Typer CLI entry point
 │   ├── core/                    # Dispatcher, worktree, state, config, ...
 │   ├── pipelines/               # dev, secops, post_merge
-│   ├── bridge/                  # Telegram bridge daemon
+│   ├── bridge/                  # chat bridge daemon (Telegram, Mattermost)
 │   ├── transports/              # SocketTransport, FileMockTransport
 │   └── dashboard/               # Optional dashboard push client
 ├── tests/                       # pytest suites (one file per module)

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/docs/getting-started.md

@@ -24,7 +24,7 @@ and running the dev pipeline against a real GitHub issue. Allow about 15 minutes
 Optional:
 
 - [`uv`](https://github.com/astral-sh/uv) for faster installs.
-- A Telegram bot if you want the human-in-the-loop bridge — see [Telegram bridge]({{ '/bridge/' | relative_url }}).
+- A Telegram bot or a Mattermost server if you want the human-in-the-loop bridge — see [Chat bridge]({{ '/bridge/' | relative_url }}).
 
 ## Install
 
@@ -127,8 +127,8 @@ What happens:
 
 If Claude blocks asking a question, the answer mechanism only works when a
 transport is connected. With `file_mock`, you'll see the question on the console
-but cannot resume. Switch to the Telegram transport to actually answer — see
-[Telegram bridge]({{ '/bridge/' | relative_url }}) and [Feedback loop]({{ '/feedback-loop/' | relative_url }}).
+but cannot resume. Switch to the Telegram or Mattermost transport to actually
+answer — see [Chat bridge]({{ '/bridge/' | relative_url }}) and [Feedback loop]({{ '/feedback-loop/' | relative_url }}).
 
 ## Your first poller tick
 
@@ -151,7 +151,7 @@ To run the poller as a long-lived background service, see [Operations]({{ '/oper
 ## Where to next
 
 - [Configuration]({{ '/configuration/' | relative_url }}) — every key in `orchestrator.yaml`.
-- [Telegram bridge]({{ '/bridge/' | relative_url }}) — how to set up the human-in-the-loop channel.
+- [Chat bridge]({{ '/bridge/' | relative_url }}) — how to set up the human-in-the-loop channel.
 - [Feedback loop]({{ '/feedback-loop/' | relative_url }}) — what `BLOCKED_NEEDS_INPUT` actually does end-to-end.
 - [CLI reference]({{ '/cli/' | relative_url }}) — every subcommand and flag.
 - [Operations]({{ '/operations/' | relative_url }}) — running ctrlrelay as a service.

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/docs/index.md

@@ -26,8 +26,8 @@ isolated git worktree, opens a PR, and asks you on Telegram when it gets stuck.
   write your first config, run the dev pipeline against an issue.
 - **[Configuration]({{ '/configuration/' | relative_url }})** — every key in
   `orchestrator.yaml`, with defaults and what they actually do.
-- **[Telegram bridge]({{ '/bridge/' | relative_url }})** — BotFather walkthrough,
-  starting the bridge, troubleshooting Telegram delivery.
+- **[Chat bridge]({{ '/bridge/' | relative_url }})** — setting up Telegram or
+  Mattermost, starting the bridge, troubleshooting delivery.
 - **[Feedback loop]({{ '/feedback-loop/' | relative_url }})** — how
   `BLOCKED_NEEDS_INPUT` checkpoints reach you and how your reply resumes the
   paused Claude session.

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/docs/operations.md

@@ -184,7 +184,7 @@ installer uses. Save under `~/.config/systemd/user/`.
 
 ```ini
 [Unit]
-Description=ctrlrelay Telegram bridge
+Description=ctrlrelay chat bridge (Telegram or Mattermost)
 After=network-online.target
 
 [Service]
@@ -264,6 +264,7 @@ loopback or on the home network.
 | `/` | The page. Refreshes itself every `web.refresh_seconds`. |
 | `/api/status` | Everything on the page, as JSON (the contract is in `src/ctrlrelay/web/status.py`). A section that could not be read is `null` and `errors` says why; `[]` means "read, and empty". The feed holds at most the newest `feed_limit` (200) events: `feed_total` is how many the history window holds (`null` if unreadable) and `feed_truncated` is `true` when some were left out, in which case the page says "showing newest N of M". |
 | `/api/events?since=<epoch seconds>` | The feed, newest first, at most `limit` (200) events. Without `since`, the last `web.history_days` days. Carries the same `feed_total` and `feed_truncated`, plus the `limit` used. |
+| `/api/events?kind=<kind>&day=today` | One Today counter's events, for the server's local day, newest first, at most 200: `{kind, events, total, truncated, error}`. `kind` is `dispatched`, `pr_opened`, `merged`, `failed`, `blocked` or `message_sent`. A `failed` or `blocked` event also carries `reason`: `exit_code`, the run's `summary` (up to 500 characters) and `output_tail` (up to 2,000), both scrubbed of credential shapes again before they are sent, the `question` asked, and `session: "not found"` when the run's row is gone. `events` is `null` with `error` set when they could not be read. A query with `kind` and anything other than exactly `kind` and `day=today` is refused with 400, except that one with `since` is the feed, as before. A summary or question longer than 500 characters ends in "…". On the page, clicking a Today counter shows this list under it, read again with every refresh. |
 
 The page header shows how long ago it last heard from the server ("updated
 12s ago", ticking every second) and a dot that is green while the last good
@@ -290,7 +291,10 @@ machine last read it: `read_at`, and for `core`, `search` and `graphql` each
 `{remaining, limit, resets_at, state}` with `state` one of `ok`, `low`, `out`,
 or `unknown` once its reset time has passed (the numbers are then old), or
 `"unknown"` in place of the object for a bucket it could not read; the whole value is `"unknown"`
-before any reading. The page shows it in the **Usage** box. Low and used-up
+before any reading. The page shows it in the **Usage** box; a bucket whose
+reset time has passed since the last read shows as "refilled at <time>, not
+read since" (GitHub refills it at that time), and `search`, which refills
+every minute, usually shows that way. Low and used-up
 buckets are described in [configuration: github_api]({{ '/configuration/' | relative_url }}#github_api).
 Which bucket a `gh` command spends is worked out from the command where the
 command says: `gh api` REST paths are `core`, `gh api graphql` is `graphql`,

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "ctrlrelay"
-version = "0.16.0"
+version = "0.16.2"
 description = "Local-first orchestrator for headless coding agents across multiple GitHub repos"
 readme = "README.md"
 requires-python = ">=3.12"

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/src/ctrlrelay/cli.py

@@ -1846,10 +1846,14 @@ def bridge_start(
         from ctrlrelay.core.state import StateDB
         state_db = StateDB(config.paths.state_db)
 
+        # #248: this machine's name on every post, and whether other
+        # machines read the same chat (Mattermost only).
         server = BridgeServer(
             socket_path=socket_path,
             handler=handler,
             state_db=state_db,
+            node=config.node_id,
+            shared=bool(getattr(chat_config, "shared", False)),
         )
 
         loop = asyncio.new_event_loop()

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/src/ctrlrelay/templates/systemd/bridge.service.template

@@ -1,5 +1,5 @@
 [Unit]
-Description=ctrlrelay Telegram bridge
+Description=ctrlrelay chat bridge (Telegram or Mattermost)
 After=network-online.target
 
 [Service]

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/src/ctrlrelay/web/server.py

@@ -45,7 +45,7 @@ from ctrlrelay.core.obs import get_logger, log_event
 from ctrlrelay.core.usage import UsageStore, pause_for, usage_json
 from ctrlrelay.web.fleet import PeerReader
 from ctrlrelay.web.health import read_server_health
-from ctrlrelay.web.status import build_status, list_feed
+from ctrlrelay.web.status import DAY_KINDS, build_status, list_day_events, list_feed
 
 _logger = get_logger("web.server")
 
@@ -206,6 +206,23 @@ class _Handler(BaseHTTPRequestHandler):
             self._json(200, srv.status())
         elif url.path == "/api/events":
             query = urllib.parse.parse_qs(url.query, keep_blank_values=True)
+            if "kind" in query and "since" not in query:
+                # One Today counter's events (#257). A query with ``since``
+                # is the feed, as it was before ``kind`` existed.
+                kinds, days = query.get("kind"), query.get("day")
+                if (
+                    len(kinds) != 1 or kinds[0] not in DAY_KINDS
+                    or days != ["today"] or set(query) != {"kind", "day"}
+                ):
+                    self._json(400, {
+                        "error": "kind must be one of " + ", ".join(sorted(DAY_KINDS))
+                        + ", with day=today and nothing else",
+                    })
+                    return
+                self._json(200, list_day_events(
+                    db_path=srv.config.paths.state_db, kind=kinds[0],
+                ))
+                return
             values = query.get("since")
             if values is None:
                 since = srv.default_since()

{ctrlrelay-0.16.0 → ctrlrelay-0.16.2}/src/ctrlrelay/web/static/index.html

@@ -90,6 +90,17 @@ ul.plain > li { padding: 7px 0; border-bottom: 1px solid var(--line); }
 ul.plain > li:last-child { border-bottom: 0; }
 .today { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 8px; }
 .today .n { font-size: 22px; font-weight: 700; }
+.today button.card {
+  font: inherit; color: inherit; text-align: left; cursor: pointer; width: 100%;
+}
+.today button.card:hover { border-color: var(--accent); }
+.today button.card[aria-pressed="true"] { border-color: var(--accent); box-shadow: 0 0 0 1px var(--accent); }
+#today-list { margin-top: 10px; }
+#today-list .reason { font-size: 13px; color: var(--muted); margin: 2px 0 0; }
+#today-list pre {
+  white-space: pre-wrap; word-break: break-word; font-size: 12px; margin: 6px 0 0;
+  max-height: 260px; overflow: auto; background: var(--tag); padding: 8px; border-radius: 6px;
+}
 .feed .when { color: var(--muted); font-size: 12px; font-variant-numeric: tabular-nums; min-width: 4.5em; }
 .feed .detail { color: var(--muted); font-size: 13px; overflow-wrap: anywhere; }
 a { color: var(--accent); text-decoration: none; }
@@ -108,8 +119,8 @@ a:hover, a:focus-visible { text-decoration: underline; }
 .usage .bar { height: 6px; background: var(--line, #ddd); border-radius: 3px; margin: 2px 0 6px; }
 .usage .bar > span { display: block; height: 100%; border-radius: 3px; background: currentColor; }
 .usage .bar.high { color: var(--bad); }
-.fleet { margin: 0 20px 12px; }
-.strip { display: flex; flex-wrap: wrap; gap: 10px; }
+.fleet { margin: 18px 20px 4px; }
+.strip { display: flex; flex-wrap: wrap; gap: 10px; margin-bottom: 18px; }
 .strip .machine { border: 1px solid var(--line); border-radius: 8px; padding: 8px 12px;
   min-width: 190px; background: var(--panel); font-size: 13px; }
 .strip .machine.bad { border-color: var(--bad); }
@@ -164,6 +175,7 @@ details > summary .count { font-weight: 400; margin-left: 6px; }
     <section>
       <h2>Today</h2>
       <div id="today"><p class="unknown">loading…</p></div>
+      <div id="today-list" aria-live="polite"></div>
     </section>
   </div>
   <div>
@@ -782,18 +794,32 @@ function renderGitHubBudget(api, now, lines) {
   }
   ["core", "search", "graphql"].forEach(function (name) {
     var b = api[name];
-    if (!b || typeof b !== "object" || typeof b.remaining !== "number" ||
-        b.state === "unknown") {
-      lines.push(el("div", "line", "GitHub " + name + " unknown"));
-      return;
-    }
-    var high = b.state === "low" || b.state === "out";
-    lines.push(el("div", "line" + (high ? " high" : ""),
-      "GitHub " + name + " " + b.remaining + " of " + b.limit + " left" +
-      (b.state === "out" ? " (used up)" : "") + ", " + untilText(b.resets_at, now)));
+    var high = b && !refilled(b, now) && (b.state === "low" || b.state === "out");
+    lines.push(el("div", "line" + (high ? " high" : ""), budgetLine(name, b, now)));
   });
 }
 
+// One bucket's line. A reading whose reset time has passed is old: GitHub
+// has refilled that bucket since, so say that rather than "unknown" (search
+// refills every minute and is read every few, so it is usually in this state).
+function refilled(b, now) {
+  var reset = b && typeof b === "object" ? Date.parse(b.resets_at) : NaN;
+  return !isNaN(reset) && reset / 1000 <= now;
+}
+
+function budgetLine(name, b, now) {
+  if (!b || typeof b !== "object" || typeof b.remaining !== "number") {
+    return "GitHub " + name + " unknown";
+  }
+  if (refilled(b, now)) {
+    return "GitHub " + name + " refilled at " + clock(Date.parse(b.resets_at) / 1000) +
+      ", not read since";
+  }
+  if (b.state === "unknown") { return "GitHub " + name + " unknown"; }
+  return "GitHub " + name + " " + b.remaining + " of " + b.limit + " left" +
+    (b.state === "out" ? " (used up)" : "") + ", " + untilText(b.resets_at, now);
+}
+
 function renderUsage(data, now) {
   var target = document.getElementById("usage");
   var n = data.node;
@@ -835,21 +861,121 @@ function renderUsage(data, now) {
   put(target, lines);
 }
 
+// The event kind each Today counter counts (#257); the counter's own key
+// differs only for messages.
+var TODAY_KIND = { messages_sent: "message_sent" };
+var todayOpen = null;
+// Each list request is numbered; only the newest one may draw, so a slow
+// answer for an earlier refresh or another counter never replaces a newer one.
+var todaySeq = 0;
+// The kind whose list request is still out. A refresh does not start
+// another for it (on a slow server every answer would be overtaken and the
+// list would stay at "loading…"); a click always does.
+var todayBusy = null;
+// A refresh skipped while a request was out: read again when it lands, so
+// the list does not lag the count by more than one answer.
+var todayStale = false;
+
 function renderToday(data) {
   var target = document.getElementById("today");
   var t = data.today || {};
   var grid = el("div", "today");
   TODAY.forEach(function (pair) {
     var v = t[pair[0]];
-    var cell = el("div", "card");
+    var kind = TODAY_KIND[pair[0]] || pair[0];
+    var cell = el("button", "card");
+    cell.type = "button";
+    cell.setAttribute("aria-pressed", todayOpen === kind ? "true" : "false");
+    cell.title = "Show today's " + pair[1];
     if (typeof v === "number") { cell.appendChild(el("div", "n", v)); }
     else { cell.appendChild(el("div", "n unknown", "unknown")); }
     cell.appendChild(el("div", "muted", pair[1]));
+    cell.addEventListener("click", function () {
+      todayOpen = todayOpen === kind ? null : kind;
+      renderToday(lastData || data);
+      if (todayOpen) { put(document.getElementById("today-list"), [empty("loading…")]); }
+      loadTodayList(true);
+    });
     grid.appendChild(cell);
   });
   put(target, [grid]);
 }
 
+// The list behind the open counter, read again with every refresh so it
+// follows the count.
+function loadTodayList(force) {
+  var target = document.getElementById("today-list");
+  var kind = todayOpen;
+  if (!kind) { todaySeq++; todayBusy = null; put(target, []); return; }
+  if (!force && todayBusy === kind) { todayStale = true; return; }
+  var seq = ++todaySeq;
+  todayBusy = kind;
+  todayStale = false;
+  fetch("/api/events?kind=" + encodeURIComponent(kind) + "&day=today", { cache: "no-store" })
+    .then(function (resp) { return resp.json(); })
+    .then(function (data) { if (seq === todaySeq) { renderTodayList(data); } })
+    .catch(function (err) {
+      if (seq === todaySeq) {
+        put(target, [unknown("unknown: the list could not be read (" +
+          (err && err.message ? err.message : "error") + ")")]);
+      }
+    })
+    .then(function () {
+      if (seq !== todaySeq) { return; }
+      todayBusy = null;
+      if (todayStale && todayOpen === kind) { loadTodayList(false); }
+    });
+}
+
+function renderTodayList(data) {
+  var target = document.getElementById("today-list");
+  if (!Array.isArray(data.events)) {
+    put(target, [unknown("unknown: " + (data.error || "the list could not be read"))]);
+    return;
+  }
+  if (data.events.length === 0) { put(target, [empty("none today")]); return; }
+  var list = el("ul", "plain");
+  data.events.forEach(function (ev) {
+    var li = el("li", "card");
+    var row = el("div", "row");
+    row.appendChild(el("span", "when", clock(ev.ts)));
+    if (ev.repo) {
+      row.appendChild(ghLink(ev.url,
+        ev.repo + (typeof ev.issue_number === "number" ? "#" + ev.issue_number : ""), "repo"));
+    }
+    if (ev.session_id) { row.appendChild(el("span", "muted", ev.session_id)); }
+    li.appendChild(row);
+    var r = ev.reason;
+    if (r) {
+      if (r.session === "not found") {
+        li.appendChild(el("p", "reason", "the run's record is gone"));
+      }
+      if (typeof r.exit_code === "number") {
+        li.appendChild(el("p", "reason", "exit code " + r.exit_code));
+      }
+      if (r.question) { li.appendChild(el("p", "reason", "asked: " + r.question)); }
+      if (r.summary) { li.appendChild(el("p", "reason", r.summary)); }
+      if (r.output_tail) {
+        var more = el("details");
+        more.appendChild(el("summary", null, "output"));
+        more.appendChild(el("pre", null, r.output_tail));
+        li.appendChild(more);
+      }
+      if (!r.question && !r.summary && !r.output_tail && typeof r.exit_code !== "number"
+          && r.session !== "not found") {
+        li.appendChild(el("p", "reason", "no reason was recorded"));
+      }
+    } else {
+      var text = detailText(ev.detail);
+      if (text) { li.appendChild(el("div", "detail", text)); }
+    }
+    list.appendChild(li);
+  });
+  var note = data.truncated === true
+    ? el("p", "empty", "showing newest " + data.events.length + " of " + data.total) : null;
+  put(target, note ? [note, list] : [list]);
+}
+
 function detailText(detail) {
   if (detail === null || detail === undefined) { return ""; }
   if (typeof detail !== "object") { return String(detail); }
@@ -917,6 +1043,7 @@ function render(data) {
   renderWaiting(data);
   renderSkipped(data);
   renderToday(data);
+  loadTodayList();
   renderFleet(data, now);
   renderUsage(data, now);
   renderServer(data);