Skip to content

feat: run tau on pi - #8

Merged
andrebrait merged 129 commits into
mainfrom
pi-port-tests
Nov 20, 2026
Merged

andrebrait merged 129 commits into
mainfrom
pi-port-tests

Conversation

@andrebrait

@andrebrait andrebrait commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

tau now runs its agents with pi --mode rpc (pi 1.5.2) and the companion extension lib/pi/tau-extension.ts, instead of the omp runner. tau is a new product: it shares no state or harness with ompweb, never upgrades from ompweb, and nothing has been released, so this PR drops every compatibility path rather than keeping it.

Runtime

  • Sessions start pi --mode rpc with the tau extension. The extension adds /tau_host_tools, /tau_meta, /tau_btw, /tau_edit and /tau_auth, reached through callExtension and tau_reply frames.
  • Live streaming: pi's delta-only message_update frames get an id and block shells on the daemon (piStreamFrame), so replies show while they stream.
  • Remaps: Stop is clear_queue + abort; branch is fork; title generation always uses the fallback; set_event_filter is gone; thinking levels follow pi's thinking_level_changed level and include max.
  • Extension UI (setStatus, setWidget, setTitle, set_editor_text) becomes ui frames.
  • Session titles are pi session_info entries, so pi can still resume the file.
  • --approve is passed only when the session cwd is inside a workspace added to tau (or one of its worktrees).
  • Subagents: pi-subagents' subagent tool (per-call model with an :effort suffix). Child transcripts are read from the file AgentProgress.sessionFile names, confined to the parent's artifacts directory.

Removed

  • The auth broker and shared credentials: each host keeps its own pi credentials, managed per host in Settings → Models. Cluster placement skips members without a login for the provider (409 pool_provider_unavailable / host_provider_unavailable).
  • Agents tab, provider usage, advisor mode, model roles, word prediction, live MCP status, the browser WebSocket link (SSE only), local://, profiles, and the omp-era legacy upgrade and recovery paths (tau recover-host, the v10/v11 shim).

Protocols and updates

  • Host link restarts at application protocol v1; host maintenance has its own separately versioned API (v1).
  • Updates go over the maintenance channel only (503 maintenance_unavailable when it is down). A missing preflight fails the update. ompVersion is now piVersion.

Configuration

  • Settings write pi's settings.json; plugins are pi packages (pi install/remove/update); skills are scanned in pi's precedence order plus packages.
  • Cluster members mirror pi's configuration files and directories; LOCAL_SETTINGS lists pi's machine-local keys.
  • Persisted browser keys are tau-* (no migration); the default theme is "midnight".

Security

  • /api/files denies pi credentials (auth.json, mcp-auth.json, oauth.json, models.json, mcp.json), tau-settings.json and the whole <agent dir>/tau/ tree.
  • The Files panel cannot write into the agent directory or ~/.pi: uploads, clone targets and worktree add/remove answer 403 agent_dir_read_only, checked on the daemon through symlinks and device/inode identity. Composer attachments are unaffected.

Not in this PR

  • The ompweb-dev names (GitHub repo, npm scope @ompweb-dev/tau, launchd labels dev.ompweb.tau*) are renamed later. Nothing is published to npm.
  • Known gaps: the Windows attachment fallback outside the agent dir (a shortcut: comment; whether to keep omp's <tmp>/tau-local rule at all is open); the skills scan ignores filter patterns, ignore files and extension skills; subagent transcripts written to a custom pi-subagents sessionDir are not shown (fails closed); pi's subagent tool gets no task panel yet.
  • Flaky test: lib/hosts/files-owner.integration.test.mjs "native publication keeps staged bytes leased…" fails intermittently, also at this PR's first head.

Verification

npm test: 4105 pass, 35 skip, 0 fail (the flaky test above passed this run). npm run typecheck clean, npm run lint 0 errors (8 existing warnings), npm run build OK. Not exercised in a browser end to end.

The fake child now answers the daemon's startup get_state instead of a
runner hello, and commands, replies and events use pi's flat frames.
Runner-only checks (channel protocol version, delta/full event filter
switching) are removed. Update fixtures also name the tau repository.
Fake children and link fixtures answer the startup get_state, take
flat {type, id, ...args} commands and reply with response frames;
events travel unwrapped. Runner-only checks (channel protocol version,
subagent subscription, --advisor/--profile argv, use-omp-build) are
removed, word-prediction commands are swapped for surviving ones, and
update pins name the tau repository and npm package.
Only the fork's omp runner dialed the daemon's host socket; pi never
does, so the listener, ChannelTable.adopt and the adopted-channel
branches are dead. The startup get_state now waits channelReadyMs, as
the hub does for an open, instead of the 15 s command timeout. The
v10/v11 upgrade test exercised published ompweb updaters that install
@kahme247/ompweb, a path tau hosts never take.
Update and recovery checks still required @kahme247/ompweb, so a tau
install was refused as not an installed package and a staged tau
release failed the name check. Package names, install directories,
npm metadata checks and update commands now use @ompweb-dev/tau.
…them

pi emits agent_settled and reports only pendingMessageCount in
get_state, while the session wrapper, notifications and Edit read
session_settled, queuedMessages, queuedMessageCount and isSettled.
RpcProcess now forwards agent_settled as session_settled and fills
those get_state fields from the last queue_update and the settlement it
observed since the last agent_start; an adopted child reports no
settlement until it has seen one.
pi has no per-message queue commands: clear_queue returns every queued
text and nothing else. Queue Edit now moves all queued messages back
into the composer and Delete discards them all after a confirmation;
the per-message Steer action is gone. Stop sends abort_and_restore_queue,
which the session wrapper runs as clear_queue then abort, returning the
withdrawn texts even when the abort fails. The composer recovers Edit
text into the identity it captured at the click, so an Edit identity
move meanwhile cannot misroute it, and abort_and_restore_queue stays
fenced during a history edit.
The companion extension registered a fixed tool list, so browser tools
other than open_file and the agent tools (new_session, send_to_session,
list_sessions) never reached pi, and the Agent tools setting could not
hide anything. The daemon now sends its set_host_tools union as
/tau_host_tools, which the extension registers and activates, turning
off tools no longer listed. The daemon also routes the extension's
__tau_host_tool__ dialog as a host_tool_call, so one member executes
each call instead of every linked server, and returns the result as the
dialog's answer. Companion-extension commands are kept out of run
tracking: pi's reply never says that no run started.
pi list prints a package's path only when it is installed; the parser
dropped every package without one and kept a filter mark in the source.
The runner and its fork pin are gone: workflows install the pinned pi
(@earendil-works/pi-coding-agent 0.85.1) instead, smoke tests and
preflight use the pi on PATH, release binaries ship no runner and the
release attaches only the binaries.
readline also ends a line at U+2028 and U+2029, which are valid inside
JSON strings, so model text containing one broke its frame in two and
forced a resync. pi's framing is strict JSONL: split at LF, strip a
trailing CR, and decode UTF-8 across chunk boundaries.
pi 0.99+ answers a prompt that an extension command or input handler
consumed with disposition "handled" and starts no run; the daemon kept
waiting for that run's agent_start, which held off the idle stop.
pi has no /btw, and the extension's stand-in recorded the question
without answering it. The extension now answers from the active
branch's conversation with the session's model (streamSimple), streams
btw_delta and btw_record frames, cancels, takes follow-ups, and keeps
each record as a custom session entry, which pi leaves out of the model
context; a record saved while running is interrupted on reload.

The server reaches it through RpcProcess.callExtension: a /tau_btw
prompt that the extension answers with a tau_reply frame naming the
call's id. The daemon treats such /tau_* commands as no user message:
no peer marker, no history-edit fence, and their reply ends them.
pi has no edit_message command and moves the leaf only from an
extension command, so the wrapper calls /tau_edit: the companion
extension checks the target is a user message, runs
navigateTree(entryId, { summarize: false }), which keeps the old
branch and moves the leaf to the message's parent, and answers
{ sessionId, cancelled, leafId }. Its reply frames now use the widget
key tau, as they carry more than /btw.
The extension listened for guessed pi-subagents event names, so no
subagent ever reached tau. pi-subagents already reports to RPC hosts:
foreground children as AgentProgress rows on its subagent tool call,
background runs as PI_SUBAGENT_ASYNC_JSON snapshots on its
subagent-async widget. RpcProcess now runs both through SubagentBridge,
which emits the subagent_lifecycle and subagent_progress frames tau's
roster reads (lifecycle before a new child's progress, progress before
its end; a child still running when its call ends ends with it), and
the wrapper answers get_subagents with the children still running.
pi rejects --no-lsp (Unknown option), so the utility process behind
logins and model lists exited on start. It skips MCP instead, pi's
startup work the utility never needs.
pi keeps no client message ids, so delivery fell back to matching text
and origin cards (session and GitHub sources) disappeared. The session
wrapper now names each message before sending it (/tau_meta). The
companion extension binds the name in its input handler to the message
pi admits, follows pi's steering and follow-up queues in delivery
order, announces the id just before pi's own message_start, and
journals it as tau's client-message-entry (with its origin) once pi
has stored the message, which the session reader joins for origin
cards. A withdrawn queue is journaled as client-message-resolution,
and get_client_message_status reads the journal through the extension.

RpcProcess puts the announced id and origin on the user message's
events, the extension's names on queue snapshots, and reports
supportsClientMessageIds once the extension has spoken (tau_hello at
start, or any reply from an adopted process).
A test body still running after its environment was restored (a timeout under
--parallel, a late timer) wrote the self-update state into the machine's real
<tmp>/ompweb-self-update-<uid>, which blocked a real server's host daemon start;
update-policy.test.mjs wrote mutation.sqlite there on every run.
Rename the remaining omp-web/ompweb product names in code, tests, scripts
and CI: bin files and the tau CLI, TAU_* environment variables, the tau
state directory and file names, browser storage keys, cookies and headers,
service labels (dev.ompweb.tau, dev.ompweb.tau-host, tau.service,
tau-host.service), and the default ports 30187 (production) and 30188 (dev).
…the binary

- TAU_PI_BIN is the only pi override (TAU_OMP_BIN is gone); resolvePiBin,
  getPiVersion, spawnPiTransport and PI_NOT_FOUND replace their omp names.
- Release pins and the host updater no longer know tau-omp runner assets;
  the updater fixtures lose their fetch-omp kinds.
- The compiled binary now ships lib/pi/tau-extension.ts, and pi never loads
  an extension from the session's cwd: binary installs ran pi without tau's
  extension unless started from a tau checkout.
- smoke takes --pi; messages, comments and the not-found error name pi.
…keeps its own pi logins

Cluster members no longer run on the master's provider logins. The broker
route, the daemon's loopback forwarder, the host record's shareCredentials
flag and its Settings toggle are gone. A cluster start still names the
opening link as the server it takes its configuration from (configServer).
…on extension

/tau_auth lists pi's providers (with the stored credential's type only),
runs an account login whose steps and prompts stream back to tau, saves
an API key and logs a provider out, all through pi's own ModelRuntime.
A new host op, auth, reads and writes that host's own pi logins through a
utility pi on the daemon's machine; this machine goes the same way. The
login SSE route long-polls the daemon for its steps and feeds pasted
codes and chosen options back. API keys can now be saved and removed.
Settings -> Models lists hosts whose link is up; providers, account logins,
stored credentials and API keys are read and written on the chosen host.
API-key providers get a key field and a remove button.
Pool placement asks each member's daemon which providers it can
authenticate (cached a minute, forgotten after a login through tau) and
skips the ones without the start's provider, saying so when none is left.
A start on one chosen host fails naming the host and the provider.
A failed or slow provider query counted as logged out and refused the
start with pool_provider_unavailable.
Without it pi reads tau's /tau_* calls as prompts, so the utility's
/tau_auth api_key call sent the key to the model provider.
A prompt, steer or follow-up starting with /tau_ reached the extension:
a browser or another agent could forge a message origin, rewind history
or change the host's logins.
Reordering, renaming or configuring a session-discovered project
registered it, and pi then got --approve there. Such entries are now
marked discovered and stay untrusted until the user adds them.
pi-subagents pauses a detached child and keeps it in its foreground runs;
tau marked it completed.
…holds it

A clone could create a missing ~/.pi, and removing a worktree that
contained the agent directory deleted it. A path that cannot be checked
(a symlink loop, no access) now says so instead of blaming the agent
directory.
A name pi never admitted stayed forever and could bind to a later
message with the same text.
- link-protocol: queuedLine (only the removed browser link used it)
- draft-store: unused toDraftImages
- pi/plugins-cli: parseJsonLoose and its test
- upgrade-process: findUpgradeServerProcesses and its tests
- i18n: unused pluginsConfig package enable/disable keys
- outbox: the never-read advisor column
- hosts route: pool launchConfig accepts only extraArgs
- README (all languages): browsers no longer use /api/events/link
- AGENTS.md: main relays upload bytes through putUploadChunk
- comments that still named the browser link, and DESIGN.md's
  "legacy name" wording for TAU_TRUSTED_HEADER_SECRET
@andrebrait

Copy link
Copy Markdown
Contributor Author

Review round 1 closed at head 236bec2. It found correctness and security defects (fixed in 1c70297..2026ed2), so the stop rule does not hold yet: round 2 (adversarial review and code review) runs on 4d537da17..236bec2be.

@andrebrait

andrebrait commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor Author

Review round 2: code review

Scope: 4d537da17..236bec2be (push, whole PR as context; read locally). Tool: /code-review (high).

# Severity Location Finding Verdict
1 Medium lib/message-outbox.ts:42 Dropping the advisor column breaks inserts into an outbox.db created by an earlier build of this branch (NOT NULL constraint failed: entries.advisor). Rejected: only an install of an earlier build of this unreleased branch can hold that data; tau keeps no compatibility with its own unreleased builds (as for the tau-* browser keys). A dev machine that ran one deletes <agent dir>/tau/outbox.db.
2 Medium lib/hosts/workspace-clone.ts:77 Clone checks only the parent; a .pi repository cloned into ~ creates pi's config root. Fixed in 4af3e40: the clone target itself goes through assertOutsideAgentDir (test: a clone never creates pi's agent directory, even while it does not exist).
3 Medium lib/pi/subagent-bridge.ts:104 A detached foreground child now stays running forever; no later frame of its call can end it. Fixed in be54a3d: at its call's end a detached child gets a lifecycle frame with detached: true and leaves running(), so a snapshot cannot keep it running (test updated).
4 Medium lib/message-outbox.ts:1059 An idle follow-up/steer sent as a bare prompt is refused if a run starts between the idle read and the write; streamingBehavior would queue it. Rejected after checking: a prompt with streamingBehavior skips the wrapper's run bookkeeping (promptRunning, awaitingAgentStart in rpc-manager.ts), so it would start an untracked run. Idle entries stay bare prompts; a run started in that window makes pi refuse it, which leaves the entry Not sent with Retry, as for prompt entries before. Documented in 9094214.
5 Medium lib/pi/tau-extension.ts:325 The new text check drops the id of a prompt another extension's input hook rewrites. Fixed in a533076: the text check is gone; the input-time clear covers a refused prompt (tests: a named prompt keeps its id when another extension rewrites its text; a refused slash prompt's name is cleared by the next prompt).
6 Medium lib/hosts/workspace-roots.ts:116 A missing agent dir is compared case-sensitively; ~/.PI on macOS/Windows is not matched. Fixed in 4af3e40: path comparison folds case on macOS and Windows.
7 Medium lib/worktree.ts:225 Entries registered by earlier builds have no discovered flag and stay trusted. Rejected: only an install of an earlier build of this unreleased branch can hold that data; tau keeps no compatibility with its own unreleased builds (as for the tau-* browser keys). Such a dev machine removes and re-adds those workspaces, or edits projects.json.
8 Low lib/pi/tau-extension.ts:311 findIndex binds the oldest of equal-text names; the newest is the admitted one. Fixed in a533076 (findLastIndex; test: of two names with the same text, the newest is the prompt pi admits).
9 Nit lib/rpc-manager.ts:2448 Session callExtension calls are not refused under TAU_NO_EXTENSION=1. Fixed in a533076: RpcProcess.callExtension refuses every call under TAU_NO_EXTENSION=1 (test: every extension call is refused).
10 Nit app/api/hosts/route.ts:85 A pools.json with stored profile/advisor keys can no longer be saved back. Rejected: only an install of an earlier build of this unreleased branch can hold that data; tau keeps no compatibility with its own unreleased builds (as for the tau-* browser keys).

Not checked: the full test suite.

@andrebrait

andrebrait commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor Author

Review round 2: adversarial review

Scope: 4d537da17..236bec2be (push, whole PR as context). Tool: adversarial-review (private copy; pi 1.5.2 and pi-subagents 0.89.0 sources read; 15 affected test files 442 pass).

# Severity Location Finding Verdict
1 Medium lib/pi/tau-extension.ts:325 Same as code review #5: an input-transforming extension makes every delivered message show "Not sent". Fixed in a533076 (same as code review #5).
2 Medium lib/pi/subagent-bridge.ts:104 Same as code review #3. Fixed in be54a3d (same as code review #3).
3 Low lib/message-outbox.ts:953,1059 Same race as code review #4; check the wrapper's run bookkeeping for a prompt with streamingBehavior. Rejected (same as code review #4): the wrapper skips run bookkeeping for a prompt with streamingBehavior.
4 Low lib/hosts/pool-starts.ts:345 Unknown-login members rank equal to known-good ones. Deferred: preferring known-good members is a placement-policy change; the round-1 fix only stops refusing members that cannot answer.
5 Low lib/message-outbox-schema.ts Same as code review #1. Rejected (same as code review #1): unreleased-build data only.
6 Low lib/pi/tau-extension.ts:310 The input-time clear is untested (mutation survives): a refused slash prompt followed by another prompt. Fixed in a533076 (test: a refused slash prompt's name is cleared by the next prompt, which never takes it).
7 Low lib/pi/rpc-utility.ts:125 The TAU_NO_EXTENSION utility guard is untested (mutation survives). Fixed in a533076: the guard moved into RpcProcess.callExtension, with a test.
8 Low lib/hosts/workspace-roots.ts:157-171 A dangling symlink into a missing part of the agent dir is walked past; missing-dir compare is case-sensitive. Case folding fixed in 4af3e40. The dangling-symlink case is rejected: it needs a link the same user planted, and that user can already write into the agent directory directly.

Found fine: every prompt path goes through AgentSessionWrapper.send; the extension ships with npm, nix and the binary; the discovered flag paths; the cleanup commit.
Not checked: a live pi RPC run, EACCES ancestors (ran as root), Windows/macOS paths, inherited TAU_PACKAGE_DIR in an update preflight.

A clone checked only its parent, so a .pi repository cloned into ~
created pi's config root. On macOS and Windows a missing agent dir is
now compared case-insensitively.
…thout the extension

The text check dropped the id of a prompt another extension's input hook
rewrote; the input-time clear already covers a refused prompt. Of equal
names the newest is the admitted one. callExtension itself refuses under
TAU_NO_EXTENSION=1, so session calls cannot reach pi as prompts.
…nning

No later frame of its call can end it, so it stayed running for good.
@andrebrait

Copy link
Copy Markdown
Contributor Author

Review round 2 closed at head 9094214. It found correctness and security defects (fixed in 4af3e40..be54a3d), so round 3, the last one, runs on 236bec2be..909421461.

@andrebrait

andrebrait commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor Author

Review round 3: code review

Scope: 236bec2be..909421461 (push, whole PR as context; read locally). Tool: /code-review (high).

# Severity Location Finding Verdict
1 Medium lib/pi/tau-extension.ts:327 A bare prompt pi refuses during a run (input handlers ran, then "already processing") leaves starting set; the run's next queued steer/follow-up takes that id, now that the text check is gone. Fixed in db634f5: a bare prompt during a run (!ctx.isIdle()) never becomes pending (test: a bare prompt pi refuses during a run never gives its id to the run's next queued message).
2 Medium lib/pi/tau-extension.ts:312 findLastIndex swaps ids when two senders interleave names and prompts with equal text (name A, name B, prompt A, prompt B). Fixed in db634f5: back to first-in-first-out matching; names go out in their prompts' order (test: names with the same text go to their prompts in order). This reverses round 2's #8 fix; the 32-name cap still bounds a never-admitted name.
3 Medium lib/pi/rpc-process.ts:502 The TAU_NO_EXTENSION guard reads the calling process's environment, not the daemon's that spawned pi. Documented, not changed, in db634f5: TAU_NO_EXTENSION is a single-process test switch that no production path sets, and production cannot start pi without the extension (c26feca). Refusing until tau_hello would break adopted sessions, which never see it.
4 Medium lib/pi/subagent-bridge.ts:92 running() hides a child as soon as a row reads detached, even while its call still runs. Fixed in db634f5: only a child still detached when its call ended leaves running() (test: a child detached while its call still runs stays in the running snapshot).
5 Low lib/rpc-manager.ts:2147 A prompt refused because a run is active resets the wrapper's run state (existing behaviour, now on a path the outbox comment names). Deferred: existing wrapper behaviour, not changed by this PR; reconciling run state on an "already processing" refusal is a separate change.
6 Nit lib/pi/tau-extension.ts:312 A rewrite by an extension whose input handler runs before tau's is not matched. Rejected: tau's --extension is merged ahead of installed extensions (mergePaths(cli, enabled) in pi 1.5.2, confirmed by the round-2 adversarial pass), so tau's input handler runs first.
7 Nit lib/hosts/workspace-roots.ts:92 Case folding over-refuses on case-sensitive APFS and ignores Unicode normalization. Accepted as a limit: fail-closed; recorded in a shortcut: comment in db634f5.

Not checked: the test suite; pi-subagents emitting detached before a call ends.

…all detached child

A bare prompt pi refused during a run left its name for the run's next
queued message, and newest-first matching swapped equal-text names of
interleaved senders. A child detached while its call still ran left the
running snapshot.
A follow-up whose input fired while a prompt still prepared replaced that
prompt's pending name, so the prompt took the follow-up's id. Pending
prompts are now a list matched by text, with the latest input as the
fallback for a rewritten text.
@andrebrait

Copy link
Copy Markdown
Contributor Author

Review round 3: adversarial review

Scope: 236bec2be..909421461 (push, whole PR as context). Tool: adversarial-review (private copies; extension harness probes ordered by pi 1.5.2 source; 7 affected test files 109 pass; 8 mutations, 1 survived).

# Severity Location Finding Verdict
1 Medium lib/pi/tau-extension.ts:324-328 A follow-up whose input fires while a prompt is still in pi's preflight (pi strips its behaviour while not streaming) replaced the prompt's pending name, so the prompt took the follow-up's id and its origin card. Fixed in d76c89e: pending prompts are a list matched by text; the latest input is the fallback only for a rewritten text (tests: a follow-up whose input fires while a prompt still prepares never swaps ids; an unnamed prompt after a refused named one gets no id).
2 Medium lib/pi/tau-extension.ts:315,328 A bare prompt refused with "already processing" left its name for the run's next queued message. Fixed in db634f5 (same as code review #1).
3 Low lib/hosts/workspace-roots.ts:91-96 Case folding has no test (mutation survives on Linux). Rejected: the fold applies only on darwin/win32 and CI's macOS and Windows runners exercise that platform's path; a faked process.platform test would test the fake. The probe in this pass confirmed the behaviour.
4 Low workspace-roots.ts:92 Fold edge cases (case-sensitive APFS, Unicode, 8.3 names). Accepted as a limit: fail-closed or hostile-only; recorded in a shortcut: comment in db634f5.
5 Low lib/pi/rpc-process.ts:501-502 The TAU_NO_EXTENSION guard reads main's environment, not the daemon's. Documented in db634f5: the flag is for single-process tests only; no production path sets it, and production cannot start pi without the extension (c26feca).
6 Low lib/pi/subagent-bridge.ts:90 A child detached mid-call left get_subagents early. Fixed in db634f5 (callEnded; test: a child detached while its call still runs stays in the running snapshot).
7 Low subagent-bridge + useAgentSession.ts:944-947 A detached chip pulses until the next roster refresh, then vanishes; no history entry. Deferred with simplification #12 (pi's subagent tool gets no history parser or task panel yet).
8 Low lib/pooled-projects.ts:162, lib/project-clone.ts:68 Pool clones into a server-configured root skip assertOutsideAgentDir. Deferred: the root is server configuration, not user input; covered by the pool-placement follow-up.

Not checked: a live pi RPC run, real macOS/Windows filesystems, browser rendering of the roster.

@andrebrait

Copy link
Copy Markdown
Contributor Author

Review round 3 closed at head d76c89e. Its correctness findings are fixed in db634f5 and d76c89e. This was the third and last round: only a High finding reopens one. Remaining deferred items are listed in each round's comments.

@andrebrait
andrebrait merged commit 6b80081 into main Nov 20, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant