feat(ui): declutter the sidebar onto a shared target menu #100

Merged
lz merged 14 commits from feat/target-menu into main 2026-09-04 17:24:35 +02:00
Owner

Stacked on #99, which is stacked on #98. Merge in order. Third of the four PRs in the issue #96 spec — designs D3, D4, D5, D6, D9, D10, D11.

Seven commits, each independently green, in the order they build on each other.

What changed

A session row is 2 hit targets, down from 5. The name opens the terminal — the one action worth a first-class target — and ⋯ (or right-click anywhere on the row) opens everything else. Deleted: ViewButtons, the five-button .card-actions row, the inline <Previews> block under every session, the per-row ×, and the card's duplicated mounts readout.

The workspace shell moved to the top of its card. That fixes the naming complaint at its root: start agent was ambiguous because it sat on the workspace header next to Start/Stop (the container). It's now Start/Stop shell agent on the row it controls, and container power is Start/Stop workspace in the workspace menu.

Ports and Settings became dock panels. DockView gains both. Settings is a panel and not a modal deliberately — a modal blocks the terminal, and editing an env var while watching the agent restart is a normal thing to want.

Identity is a dim wash; the left border means status alone. Three of the eight SESSION_PALETTE hues are byte-identical to --running / --warn / --danger, so the two channels could read as each other. sessionColourRgb() is derived from the hex palette, with a test pinning them together. Two alphas (--wash-row 0.10, --wash-tile 0.22) because a wash that reads on a 330px row disappears on a 40px rail tile.

The rail is segmented capsules with a hover card. One bordered column per workspace; the shared border is what makes a session read as belonging to it. Measured 37 × 24 = 888px² per segment, against 81px² for the dot it replaces, and clear of WCAG 2.2 SC 2.5.8's 24×24 on both axes — which the old dot failed outright. The hover card opens on :focus-visible too; the segments are buttons and a keyboard user got nothing at all before.

Right-click a dock tab gets the same menu, so collapsing the sidebar is lossless.

Mobile gets a panels pill. Reaching the dock used to require opening a panel — openPanel() was showDock()'s only caller, so forward always mutated the layout while coming back was free.

Issue #95, absorbed

No confirm on revoke · operator-created ports auto-approve (approval gates the agent callback; a port typed into the operator's own UI has already expressed that intent) · the remapped host port is shown when it differs from the requested one.

Verification

pnpm test 110 files / 1049 tests · pnpm run typecheck 4864 files, 0 errors · pnpm run lint clean.

Browser-driven against a seeded instance, since the suite is node-only and proves nothing about rendering:

checked result
sidebar audit 0 view icons, 0 inline preview blocks, 1 ports chip (only the session that has one)
session row 2 buttons (3 with a ports chip)
menu portalled to <body>, clamped in viewport, live port count in the hint
Ports panel renders, 1 preview row, real host URL
Settings panel renders; env/mounts labelled — set on lz/agent-nexus
tab right-click menu opens with ✓ on the docked view
rail 3 capsules, segment 37×24 = 888px², wash on docked segments, progress segment, warn pip
hover card portalled, in viewport, opens on keyboard focus
mobile 390px pill visible with identity dots, switches to the dock without opening a panel, list scrolls
long-press full-width bottom sheet with dim scrim

Deliberately not included

  • "Restart agent" in the session menu. There is no restart-session endpoint, and a menu row that does nothing is worse than an absent one.
  • A workspace submenu on session tabs. The tab variant carries views + Close + Close others only: removing a session from under one of its own open panels isn't something to offer at the pointer, and a tab has no sensible place for container controls.
  • Editable env/mounts in the Settings panel. Both tables are keyed on repo_full_name, so an editable table under a "workspace" heading would silently reconfigure siblings.

Two preview tests pinned the pre-#95 behaviour and were updated rather than worked around, plus a new case for a bind failure degrading to pending instead of failing the create.


Added after the spec audit

A five-agent pass over the shipped code against the spec and the mock found this PR carried the bulk of what was missing. All of it is now here.

The blocking criterion was false. "Every action reachable from the sidebar is reachable from a dock tab's context menu" — the tab menu was a hand-written fourth shape with four views plus Close, so ~10 actions had no route. The cause was three near-identical onPick switches, each knowing a different subset of MenuAction. menu-actions.ts is now the only dispatcher, and the two -tab variants are composed from the sidebar's own item builders, so the criterion holds by construction. target-menu.test.ts pins the superset relation across all four toggled-row combinations — verified by rebuilding session-tab by hand and watching it go red.

Session-agent lifecycle did not exist product-wide, which is why the menu had no Restart/Stop and D6 had no Agent section. POST/DELETE on sessions/:id/agent now restart and stop claude without touching the row or the worktree. Stop respawns the tmux window as bash rather than killing it, because convergeSessions restores a session whose window is missing — killing it would be silently undone within one 10s poll.

D6 was a stub — two links, zero <button>. It now carries live agent state with Restart/Stop, the agent-teams toggle, created + usage, image + capability chips, container state with Start/Stop, the repo's env keys, and both Remove actions.

WorkerDTO had no worker_image. One missing field blocked three surfaces; the rail's hover card row labelled "image" printed container_name.

The rail had no context menu, against Decision 2 — leaving the collapsed sidebar able to open terminals and nothing else.

Also: the hover card gains usage and docked views; the mobile pill's 4-dot cap now shows an overflow dot instead of lying about the count; the edge swipe (D11) is implemented with its thresholds in a pure, tested module; the ports panel body says Ports rather than Previews; and /api/quota stopped being fetched once per workspace card.

SessionRow and ProvisionProgress come out of the two sidebar files, which is what finally makes their net line count fall (662 → 627) as the spec requires, rather than rise.

Browser-verified at 1400px and 390px: both tab menus (12 and 15 rows, no duplicates), the rail menu, "New session…" from the collapsed rail expanding and focusing the right form, both settings scopes, the corrected image row, the overflow dot, and the edge swipe in both directions plus its scroll guard.

Verified in a real container, and reviewed

Ran the session-agent endpoints against a live worker (real image, real clone, real claude). Stop → converge → restart behave as designed: the window survives a stop as bash, convergeSessions correctly leaves it alone, and restart reuses the same window with --resume on the same conversation id.

That run found a pre-existing bug the suite could not see: the per-session health probe is /bin/sh -c "<script>" that greps every proc cmdline for --remote-control <workspace · session> — and the script text contains that pattern, so it matched its own entry and exited 0. A session name that had never existed reported claude as running. Invisible on main because nothing could produce the state it hides in; stop is exactly that state. Now matched by CWD.

Then /simplify (4 agents) and /pr-review (2 adversarial). What they caught, all fixed:

  • setSessionAgent dropped -e NEXUS_SESSION_ID — found independently by two agents. tmux does not remember a window's original -e, so a restarted session lost notify-preview / notify-artifact permanently (fact #16).
  • respawn-window -t nexus:<name> resolves an all-digit name as an INDEX — verified against real tmux 3.3a. Restart on a session named 1 SIGKILLs a different session's claude and leaves it dead where convergeSessions will never look. Same hole in deleteSession's kill-window, older and worse. Both now resolve a window ID.
  • Stop left sessions.status = 'running', so the rail showed green while the expanded sidebar showed a red error for the same deliberately-stopped agent.
  • Restart claimed to resume a conversation it had not — resumeFlag emits nothing for the empty id migration 0012 backfilled, so an upgraded install silently got a fresh conversation.
  • Neither action waited for claude; both now do, and return {confirmed} so the toast can say "not up yet".
  • The workspace-tab menu offered open-shell twice, and my guard test compared labels — so did my manual browser check, because I wrote both.
  • Silent failures: goto outside its try, "Copy branch name" returning quietly with a stale clipboard, "New session…" on a booting workspace doing nothing visible, a failed env fetch rendering as "None set", and a transient image-list failure latched for the life of the page.
  • A session Settings panel restored from localStorage rendered the workspace pane — with a live "Remove workspace…" — during the window between listWorkers and listSessions.

22 tests added for the endpoints and the dispatcher, plus 5 for the review findings. Every guard was confirmed to go red against the behaviour it describes.

**Stacked on #99**, which is stacked on #98. Merge in order. Third of the four PRs in the issue #96 spec — designs D3, D4, D5, D6, D9, D10, D11. Seven commits, each independently green, in the order they build on each other. ## What changed **A session row is 2 hit targets, down from 5.** The **name** opens the terminal — the one action worth a first-class target — and **⋯** (or right-click anywhere on the row) opens everything else. Deleted: `ViewButtons`, the five-button `.card-actions` row, the inline `<Previews>` block under every session, the per-row `×`, and the card's duplicated mounts readout. **The workspace shell moved to the top of its card.** That fixes the naming complaint at its root: `start agent` was ambiguous because it sat on the workspace header next to `Start`/`Stop` (the container). It's now `Start/Stop shell agent` on the row it controls, and container power is `Start/Stop workspace` in the workspace menu. **Ports and Settings became dock panels.** `DockView` gains both. Settings is a panel and not a modal deliberately — a modal blocks the terminal, and editing an env var while watching the agent restart is a normal thing to want. **Identity is a dim wash; the left border means status alone.** Three of the eight `SESSION_PALETTE` hues are byte-identical to `--running` / `--warn` / `--danger`, so the two channels could read as each other. `sessionColourRgb()` is *derived* from the hex palette, with a test pinning them together. Two alphas (`--wash-row` 0.10, `--wash-tile` 0.22) because a wash that reads on a 330px row disappears on a 40px rail tile. **The rail is segmented capsules with a hover card.** One bordered column per workspace; the shared border is what makes a session read as belonging to it. **Measured 37 × 24 = 888px² per segment, against 81px² for the dot it replaces**, and clear of WCAG 2.2 SC 2.5.8's 24×24 on both axes — which the old dot failed outright. The hover card opens on `:focus-visible` too; the segments are buttons and a keyboard user got nothing at all before. **Right-click a dock tab** gets the same menu, so collapsing the sidebar is lossless. **Mobile gets a panels pill.** Reaching the dock used to *require* opening a panel — `openPanel()` was `showDock()`'s only caller, so forward always mutated the layout while coming back was free. ## Issue #95, absorbed No confirm on revoke · operator-created ports auto-approve (approval gates the *agent* callback; a port typed into the operator's own UI has already expressed that intent) · the remapped host port is shown when it differs from the requested one. ## Verification `pnpm test` 110 files / **1049 tests** · `pnpm run typecheck` 4864 files, 0 errors · `pnpm run lint` clean. Browser-driven against a seeded instance, since the suite is node-only and proves nothing about rendering: | checked | result | |---|---| | sidebar audit | 0 view icons, 0 inline preview blocks, 1 ports chip (only the session that has one) | | session row | 2 buttons (3 with a ports chip) | | menu | portalled to `<body>`, clamped in viewport, live port count in the hint | | Ports panel | renders, 1 preview row, real host URL | | Settings panel | renders; env/mounts labelled `— set on lz/agent-nexus` | | tab right-click | menu opens with ✓ on the docked view | | rail | 3 capsules, segment 37×24 = 888px², wash on docked segments, progress segment, warn pip | | hover card | portalled, in viewport, **opens on keyboard focus** | | mobile 390px | pill visible with identity dots, switches to the dock **without opening a panel**, list scrolls | | long-press | full-width bottom sheet with dim scrim | ## Deliberately not included - **"Restart agent"** in the session menu. There is no restart-session endpoint, and a menu row that does nothing is worse than an absent one. - **A workspace submenu on session tabs.** The tab variant carries views + Close + Close others only: removing a session from under one of its own open panels isn't something to offer at the pointer, and a tab has no sensible place for container controls. - **Editable env/mounts in the Settings panel.** Both tables are keyed on `repo_full_name`, so an editable table under a "workspace" heading would silently reconfigure siblings. Two preview tests pinned the pre-#95 behaviour and were updated rather than worked around, plus a new case for a bind failure degrading to pending instead of failing the create. --- ### Added after the spec audit A five-agent pass over the shipped code against the spec and the mock found this PR carried the bulk of what was missing. All of it is now here. **The blocking criterion was false.** "Every action reachable from the sidebar is reachable from a dock tab's context menu" — the tab menu was a hand-written fourth shape with four views plus Close, so ~10 actions had no route. The cause was three near-identical `onPick` switches, each knowing a different subset of `MenuAction`. `menu-actions.ts` is now the only dispatcher, and the two `-tab` variants are **composed** from the sidebar's own item builders, so the criterion holds by construction. `target-menu.test.ts` pins the superset relation across all four toggled-row combinations — verified by rebuilding `session-tab` by hand and watching it go red. **Session-agent lifecycle did not exist** product-wide, which is why the menu had no Restart/Stop and D6 had no Agent section. `POST`/`DELETE` on `sessions/:id/agent` now restart and stop claude without touching the row or the worktree. Stop respawns the tmux window as bash rather than killing it, because `convergeSessions` restores a session whose window is *missing* — killing it would be silently undone within one 10s poll. **D6 was a stub** — two links, zero `<button>`. It now carries live agent state with Restart/Stop, the agent-teams toggle, created + usage, image + capability chips, container state with Start/Stop, the repo's env keys, and both Remove actions. **`WorkerDTO` had no `worker_image`.** One missing field blocked three surfaces; the rail's hover card row *labelled* "image" printed `container_name`. **The rail had no context menu**, against Decision 2 — leaving the collapsed sidebar able to open terminals and nothing else. Also: the hover card gains usage and docked views; the mobile pill's 4-dot cap now shows an overflow dot instead of lying about the count; the edge swipe (D11) is implemented with its thresholds in a pure, tested module; the ports panel body says Ports rather than Previews; and `/api/quota` stopped being fetched once per workspace *card*. `SessionRow` and `ProvisionProgress` come out of the two sidebar files, which is what finally makes their net line count **fall** (662 → 627) as the spec requires, rather than rise. Browser-verified at 1400px and 390px: both tab menus (12 and 15 rows, no duplicates), the rail menu, "New session…" from the collapsed rail expanding and focusing the right form, both settings scopes, the corrected image row, the overflow dot, and the edge swipe in both directions plus its scroll guard. ### Verified in a real container, and reviewed Ran the session-agent endpoints against a live worker (real image, real clone, real claude). Stop → converge → restart behave as designed: the window survives a stop as `bash`, `convergeSessions` correctly leaves it alone, and restart reuses the same window with `--resume` on the same conversation id. That run found a **pre-existing bug the suite could not see**: the per-session health probe is `/bin/sh -c "<script>"` that greps every proc cmdline for `--remote-control <workspace · session>` — and the script text *contains* that pattern, so it matched its own entry and exited 0. A session name that had never existed reported claude as running. Invisible on `main` because nothing could produce the state it hides in; stop is exactly that state. Now matched by CWD. Then `/simplify` (4 agents) and `/pr-review` (2 adversarial). What they caught, all fixed: - **`setSessionAgent` dropped `-e NEXUS_SESSION_ID`** — found independently by two agents. tmux does not remember a window's original `-e`, so a restarted session lost `notify-preview` / `notify-artifact` permanently (fact #16). - **`respawn-window -t nexus:<name>` resolves an all-digit name as an INDEX** — verified against real tmux 3.3a. Restart on a session named `1` SIGKILLs a *different* session's claude and leaves it dead where `convergeSessions` will never look. Same hole in `deleteSession`'s `kill-window`, older and worse. Both now resolve a window ID. - **Stop left `sessions.status = 'running'`**, so the rail showed green while the expanded sidebar showed a red error for the same deliberately-stopped agent. - **Restart claimed to resume a conversation it had not** — `resumeFlag` emits nothing for the empty id migration 0012 backfilled, so an upgraded install silently got a fresh conversation. - **Neither action waited for claude**; both now do, and return `{confirmed}` so the toast can say "not up yet". - The `workspace-tab` menu offered `open-shell` **twice**, and my guard test compared *labels* — so did my manual browser check, because I wrote both. - Silent failures: `goto` outside its try, "Copy branch name" returning quietly with a stale clipboard, "New session…" on a booting workspace doing nothing visible, a failed env fetch rendering as "None set", and a transient image-list failure latched for the life of the page. - A session Settings panel restored from localStorage rendered the **workspace** pane — with a live "Remove workspace…" — during the window between `listWorkers` and `listSessions`. 22 tests added for the endpoints and the dispatcher, plus 5 for the review findings. Every guard was confirmed to go red against the behaviour it describes.
lz force-pushed feat/target-menu from 9fe5354e8f
All checks were successful
ci / nexus (pull_request) Successful in 7m34s
ci / images (pull_request) Successful in 9m3s
to c07700ad40
All checks were successful
ci / nexus (pull_request) Successful in 8m40s
ci / images (pull_request) Successful in 9m18s
2026-09-03 01:01:54 +02:00
Compare
fix(sessions): the health probe was matching itself, not claude
All checks were successful
ci / nexus (pull_request) Successful in 9m31s
ci / images (pull_request) Successful in 10m45s
3e594a975b
Found by running the new stop/restart endpoints against a real container, which
is the first thing that can produce the state the bug hides in: a live worker,
the tmux window present, and no claude in it.

The probe was `/bin/sh -c "<script>"` where the script greps every
`/proc/*/cmdline` for `--remote-control <workspace · session>`. The script text
CONTAINS that pattern, so the loop reached its own `/proc` entry and exited 0.
Measured in the container: a session name that had NEVER existed reported claude
as running, and so did a session whose agent had just been stopped.

Pre-existing — but invisible until now, because nothing could previously make a
running container hold a present window with no claude. Stopping an agent is
exactly that state, so shipping stop without this means the action succeeds and
then the UI reports the agent as running, on the sidebar dot and in the new
settings panel's Agent chip.

Matched by CWD instead, the same shape `probeClaudeWorkspaceProcess` already
used and immune for the same reason: the first 7 bytes of the probe's own
cmdline are `/bin/sh`, and its cwd is not a worktree. Still per-session — two
sessions in one worker have different worktree names — which is the property
fact #5 wanted from the argv match.

Verified against a real container before and after: `claudeRunning` now goes
true → false → true across stop and restart, and the reason names the worktree.

Tests for both new endpoints come with it, plus the dispatcher's. The
`setSessionAgent` set pins the three decisions that are easy to undo: `-k` (or
respawn refuses), reuse of the window rather than `new-window`, and `--resume`
rather than the bare id — that last assertion was too weak until a negative
control showed `resume: false` emits `--session-id <same id>`, which carries the
id while telling claude to start a fresh conversation under it.

`menu-actions.test.ts` derives its action list from `buildMenu` across every
variant rather than hand-listing it, so an action a menu can offer but the
dispatcher ignores fails the suite. A hand-listed set is exactly what let the
dock tab ignore twelve of fifteen actions while everything stayed green.
refactor: apply /simplify — including a regression two reviewers caught
All checks were successful
ci / nexus (pull_request) Successful in 8m54s
ci / images (pull_request) Successful in 10m9s
45f2b31106
Four cleanup agents over the audit-fix commits. Two of them independently found
the same functional regression, which is the one worth reading:

**`setSessionAgent` dropped `-e NEXUS_SESSION_ID`.** tmux builds a spawned
pane's environment from the server environment plus the `-e` arguments and does
NOT remember a window's original ones, so a respawn has to re-pass it —
`openWorkspaceSession` already does, on its own respawn, which was the
codebase's own evidence. Without it, `notify-preview` and `notify-artifact`
stop working in that session after a Restart (fact #16), silently and until the
session is recreated. The stop path had the same hole for the bash it leaves
behind. Fixed by pulling the launch out into a shared `spawnSessionPane` rather
than by adding the flag in a fourth place; the test now pins the env block, and
removing it goes red.

**`workspace-tab` offered `open-shell` twice** — as "Start shell agent" and as
"Open workspace shell", two rows firing one action under different names. The
guard test compared LABELS, so it passed; my own browser check compared labels
too, so I confirmed the wrong thing and reported no duplicates. The variants now
compose through `dedupeByAction`, the `withSettings` flag that patched the one
earlier collision is gone, and the test compares actions across all four toggle
states.

Also:

- "Session log" is deleted, not fixed. It opened the same terminal panel as the
  row four above it, minus the ✓ that says the panel is already docked. There is
  no separate transcript: the agent's log IS its tmux window.
- The repo-env effect in `SettingsPanel` was a poller. `workspaces.workers` is
  reassigned to a fresh array every tick, so an effect reading
  `worker?.repo_full_name` re-ran forever; it now derives the string first and
  only runs for the scope that renders it.
- The panel's health probe gets the same 8s TTL `<Sessions>` uses (both poll the
  same session when the sidebar is open), stops re-probing straight after a
  restart (the respawn does not wait for claude, so it painted "stopped"), and
  its Restart/Stop go through the dispatcher — which is also how Stop acquired
  the confirm it was missing while the identical menu action had one.
- Toggling agent-teams no longer refetches the whole fleet to reflect a boolean.
- `MenuActionHost`'s sidebar members are required; the two toast fallbacks no
  caller could reach are gone. `closePanel`/`closeOthers` stay optional and the
  header now says plainly that they are silent, instead of claiming everything
  degrades to a toast.
- One `probeClaudeCwd` for both probes, run concurrently — neither gates the
  other and both are docker execs. `reload()` likewise stops serialising two
  independent refreshes.
- Smaller: `readJsonBody`, `isRunning` and `WORKTREES_ROOT` instead of fourth
  copies; a dead `sessionStats.get()`; a separator that rendered above the first
  row of the workspace menu; Dock's sham `menuHost` seed replaced by a getter;
  and the restart/stop JSDoc moved onto the function it describes.
fix(sessions): apply /pr-review — a tmux target that hits the wrong window
All checks were successful
ci / nexus (pull_request) Successful in 8m40s
ci / images (pull_request) Successful in 9m9s
pr-image-cleanup / delete-pr-images (pull_request) Successful in 9s
3c05a7c6d3
Two adversarial reviewers over the audit-fix commits. The critical one is
verified against real tmux, not reasoned:

**`respawn-window -t nexus:<name>` resolves an all-digit name as an INDEX.**
tmux tries the window half of a target as an index before it tries it as a
name, and `1` / `42` are legal git refs the create form accepts. Measured on
3.3a with windows `0:workspace 1:alpha 2:beta 3:"1"`, `-t nexus:1` resolves to
**alpha** — and the `=` exact-match prefix does not change it. So Restart on a
session named `1` SIGKILLs alpha's claude, relaunches session 1's agent inside
alpha's window (where notify-preview then attributes to the wrong session), and
leaves alpha dead permanently: convergeSessions only restores a session whose
window is MISSING, and alpha's window is right there.

Now resolved to a window ID first. The same hole existed in `deleteSession`'s
`kill-window`, older than this PR and worse — it would destroy a bystander's
window outright — so that site moves too. Resolving also means a Restart on a
session whose window went missing now CREATES it instead of failing, which is
the state the panel reports while leaving the button enabled.

**Stop left `sessions.status = 'running'`.** That column is what the rail and
its hover card read, so a stopped agent showed green and "agent: running" —
while the expanded sidebar, which reads the probe, painted the row RED with a
"no claude running in <worktree>" line. The operator stops an agent on purpose
and one surface says it is fine, another says it crashed. `'stopped'` was
already in the union, so this is a write and a guard, no migration.

**Restart claimed to resume a conversation it had not resumed.** `resumeFlag`
emits nothing for the empty `claude_session_id` that migration 0012 backfilled,
so on an upgraded install Restart silently started a fresh conversation under
the old toast, and left the row permanently unresumable. It now mints and pins
an id the way `openWorkspaceSession` does, and reports `resumed: false` so the
toast says which of the two things happened.

**Neither action waited for claude.** tmux exiting 0 only means the pane was
respawned; the launch line falls through to `exec bash` if claude dies on
startup. Both paths now wait — the shape `openWorkspaceSession` already used —
and return `{confirmed}`, so "Agent relaunched, but claude has not come up yet"
is sayable instead of an unconditional success.

The silent-failure pass found four more places the operator is told nothing:
`goto` was the one awaited call outside a try (a rejected navigation became an
unhandled rejection); "Copy branch name" returned silently when the roster had
no branch, leaving the previous clipboard contents to be pasted into a checkout;
"New session…" on a booting workspace expanded and scrolled and then found no
form; and a failed repo-env fetch rendered as "None set for this repository" —
an affirmative claim produced by not knowing, on the pane whose whole job is
stating a blast radius. `worker-images` also latched a transient failure for the
life of the page, so one bad response hid every capability chip.

Two more the reviewers caught in the merged workspace tab: it offered "Stop
shell agent" beside "Open workspace shell" (distinct actions, so the new
dedupe did not collapse them) — fixed in the builder, since offering to open a
running shell was equally wrong on the card; and a session Settings panel
restored from localStorage rendered the WORKSPACE pane, complete with a live
"Remove workspace…", during the window between listWorkers and listSessions.

Verified: the getter on `deps.menuHost` does survive the `$state` proxy (an
accessor has no `writable`, so the trap falls through to `Reflect.get` and the
getter runs on every read), `lastProbedAt` is per-instance, and `dedupeByAction`
keeps its separator. Five new tests cover the numeric name, exact-name matching,
the missing-window fallback, the unresumable row and the status write; each was
confirmed to go red against the behaviour it describes.
lz referenced this pull request from a commit 2026-09-04 00:15:25 +02:00
lz changed target branch from feat/startup-visibility to main 2026-09-04 17:24:26 +02:00
lz merged commit 855baa6841 into main 2026-09-04 17:24:35 +02:00
Sign in to join this conversation.
No reviewers
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
lz/agent-nexus!100
No description provided.