Skip to content

ci(lazurio): build the darwin-arm64 archive on the release's own Mac runner - #220

Merged
immakermatty merged 4 commits into
mainfrom
lazurio/release-darwin-own-runner
Nov 17, 2026
Merged

immakermatty merged 4 commits into
mainfrom
lazurio/release-darwin-own-runner

Conversation

@immakermatty

@immakermatty immakermatty commented Nov 17, 2026 •

Copy link
Copy Markdown

Builds the darwin-arm64 CLI archive on a temporary self-hosted Mac runner (label lazurio-release-macos) instead of the GitHub-hosted macos-15, so that stable 0.1.9-lazurio.1 can ship.

Why

From 2026-11-16 12:29 UTC no macos-15 job in this repository got a GitHub-hosted runner, until one did: this PR's own fork CI darwin job (run 44178728651) got one at 21:20 UTC and passed. The next one did not. The stable release run 44180395885, a fresh dispatch from cf662620, queued its darwin job at 21:30:34 UTC, and GitHub cancelled it without a runner at 21:51:28 UTC (#218). Hosted macOS is therefore not reliably back, and stable 0.1.9-lazurio.1 cannot build its darwin-arm64 archive there. A support request is filed.

What changes

  • lazurio-cli-archives.yml gets a darwin_runner input that defaults to macos-15, and the darwin matrix entry uses it.
  • lazurio-release.yml passes darwin_runner: lazurio-release-macos. Fork CI passes nothing, so pull requests keep GitHub's macos-15, and no pull request's code runs on the Mac that builds releases. This addresses the blocking review.
  • The Launcher install linux-x64 job gets if: ${{ !cancelled() }}. It needs only the linux-x64 archive, so a darwin job without a runner no longer skips this required Linux check, and a failed linux-x64 build still fails it through the missing artifact. In the release, publish still needs the whole archives call.
  • The contract test pins the input default, what the release passes, that fork CI never sets the input, and the launcher's condition.
  • The application code does not change. Outside .github/workflows/ and the contract test, the tree is exactly cf662620, the accepted preview 0.1.9-preview.20261115.1.

Exception to the release rules

The release owner's consent (2026-11-17, 21:03 UTC, question tool, passed on by an agent), verbatim. The question: „Vydání T3 Code 0.1.9 na vašem Macu „macik“: smí vlákno vydání udělat dvě věci, které jdou nad vaše dosavadní schválení? (1) Použít bezpečnější úpravu: původní změna jediného řádku by na váš Mac pouštěla i kód z cizích příspěvků, což našel Pablo v review. Opravená varianta pustí na Mac jen sestavení vydání, ale mění tři soubory s nastavením sestavování a testem místo jednoho řádku; kód aplikace zůstává stejný. (2) Dočasně vyjmout sestavení pro Mac z povinných kontrol každé změny v T3 Code, dokud GitHub stroje pro Mac tomuto repozitáři nevrátí. Bez toho nejde do T3 Code sloučit nic: ani tato úprava, ani projekt Buddyho, ani úzké rozložení. Vydání si verzi pro Mac dál sestaví a vyzkouší na „macik“.“ The chosen option: „Ano, obojí (Doporučeno)“, with the text „Stabilní 0.1.9 může vyjít hned a po ní projekt Buddyho a úzké rozložení. Cena: chybu, která se projeví jen na Macu, zachytí až sestavení vydání, ne už kontrola každé změny. Povinná kontrola se vrátí, jakmile GitHub stroje vrátí; výjimka se zapíše k vydání.“ That consent covered the runner-input variant (head c87b6ef1).

The release owner's night mandate (21:28 UTC, passed on by the coordinating agent), verbatim: „Jdu spát. Neptej se mě tedy, prosím, na žádné otázky přes takový ten nástroj na otázky. Jinak tě to bude blokovat a do rána neuděláš žádnou práci. Chtěl bych, aby sis přes noc udělal maximum úkonů, co máme naplánovaných a které víš, jak udělat, ať se přes noc odmaká co nejvíce práce. Ráno můžeme navázat na frontu tvých dotazů, které přes noc nasbíráš. Dávám ti plný mandát pracovat na tom, o čem jsme se dneska bavili, a dotáhnout to do konce. Udělat zápisy, cleanup, releasy, publikování. To, co vnímáš, že víš, jak na to, udělej to. Teď je na to ten čas.“

The coordinating thread's decision under the night mandate (21:58 UTC). An agent writes this; it is not the release owner's explicit consent to this change: „změna, kdy běží Linux launcher, patří k schválené bezpečnější variantě, protože je nutná k tomu, aby ta varianta prošla kontrolami vydání; mění jen workflow vydání v týchž třech souborech, kód aplikace ne. [Admin] ji uvidí ráno v přehledu a může ji odvolat.“

What the launcher change does in behaviour. Before: Launcher install linux-x64 needs the whole build matrix, so when the darwin job fails or is cancelled, the launcher job is skipped, and GitHub counts the skipped required check as passed. After: the launcher job runs unless the workflow is cancelled. If the linux-x64 build failed, it still fails, because the linux-x64 artifact is missing. In a release, publish still needs the whole archives call, so nothing is published without the darwin archive. Without this change, the earlier finding comes back: on every PR whose hosted darwin job gets no runner, including this one, the required Linux launcher test is not executed.

Release gate (#185): git diff --name-only cf662620 <tip> lists exactly .github/workflows/lazurio-cli-archives.yml, .github/workflows/lazurio-release.yml and scripts/lazurio-release-contract.test.mjs, and git diff cf662620 <tip> equals this PR's approved head (runner input, launcher condition and the comments recording the exception). The application code is unchanged.

Why not keep macos-15

A self-hosted runner that also carried the macos-15 label did not take the queued job. GitHub keeps macos-15 jobs in its hosted queue. Tested on release run 44166261679 between 20:10 and 20:13 UTC: the runner was online and idle, and the job stayed queued.

The runner and its limits

  • Machine: an Apple silicon Mac (arm64), macOS 26.6.2, actions/runner v2.338.2 with its sha256 verified, no self-update.
  • Scope: registered for this repository only, --ephemeral, so it takes one job and unregisters. It is registered only while a release run needs it.
  • Fork pull requests: Actions now requires approval for all external contributors (all_external_contributors, until today first_time_contributors).
  • Toolchain: nothing is preinstalled. The workflow's own steps install Node (setup-vp) and Rust (dtolnay/rust-toolchain installs rustup when it is missing).
  • Attestation: it is made in the publish job on a GitHub-hosted Ubuntu runner, as before. The release evidence will say that the darwin archive was built on the self-hosted runner, and name the runner.

Consequences and the way back

  • Pull requests: their darwin job stays on GitHub-hosted macos-15, so no PR code runs on the release Mac. That job currently gets no runner (macos-15 jobs in this repository get no runner since 2026-11-16 12:29 UTC (blocks 0.1.9-lazurio.1) #218). Under the same consent of 21:03 UTC, CLI archives / Build darwin-arm64 was removed from the required checks of ruleset 21717536 at 21:04:22 UTC (record in macos-15 jobs in this repository get no runner since 2026-11-16 12:29 UTC (blocks 0.1.9-lazurio.1) #218). Until it is restored, no PR is checked for a darwin build. A Mac-only defect is caught only by the release's own darwin build and smoke test on the self-hosted runner.
  • The way back: the required check returns when GitHub has given the machines back. That means a whole release or preview run of this repository gets a hosted macOS runner and passes. A single job that gets one does not count: the job at 21:20 UTC did not meet the condition, as run 44180395885 showed. Then the check goes back into ruleset 21717536 (the JSON from before the change is kept), and a follow-up PR removes the release's darwin_runner line.
  • The Mac between jobs: before each registration for a release, the runner's work directory is wiped. The first commit of this PR ran its own fork CI darwin build there (a trusted branch, the same tree), and that work directory was removed afterwards. What the workflow installed stays: the Rust stable toolchain and Vite+ with Node.

Merge with a rebase or squash only, never a merge commit. The release checks a linear history.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

🤖 Generated with Claude Code

…runner

Since 2026-11-16 12:29 UTC no macos-15 job in this repository has got a
GitHub-hosted runner (#218), so stable 0.1.9-lazurio.1 cannot build its
darwin-arm64 archive. The release owner approved a temporary self-hosted
runner (label lazurio-release-macos, registered ephemerally for one job)
and this one-line exception: only the runner label changes, the
application code is the accepted tree of cf66262.

A self-hosted runner that also carries the macos-15 label does not take
the job: GitHub keeps macos-15 jobs in its hosted queue (tested on run
44166261679, 2026-11-17 20:10-20:13 UTC).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking:

  • Prevent pull-request code from running on the same persistent Mac used to build releases, or use a freshly isolated and destroyed machine for each job. lazurio-fork-ci.yml calls this workflow for every pull_request, fetches the PR head and runs its dependency installation and build on lazurio-release-macos. A contributor whose Actions run is approved can execute arbitrary code there and leave changes that influence a later release or access the machine's other data. --ephemeral unregisters the runner after one job; it does not erase or isolate the Mac. Requiring approval for external contributors is not a clean-machine boundary.

Non-blocking:

  • The release contract passed locally (52/52). Fork CI was still running at review time; the macOS job had reached dependency installation. The account cannot read the runner and fork-approval settings, so those claims were not independently verified.
  • Order and migrations: #185 records the one-release exception; stable 0.1.9-lazurio.1 must be released before #212, #214, #215 and #216 merge.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

The darwin-arm64 build passes on the self-hosted runner. (2026-11-17)

  • Fork CI run 44167378467, job "CLI archives / Build darwin-arm64": runner lzd-macik-release, started 20:16:03 UTC, success at 20:33:50 UTC. Every step of the job ran, including the archive smoke test (the step that runs the built arm64 binary).
  • The runner was ephemeral and unregistered itself after the job ("Removed .runner"). No runner is registered for this repository now. It will be registered again only for the stable release run.
  • Added on the Mac by the workflow's own steps: the Rust stable toolchain with the aarch64-apple-darwin target (rustup was already there), Vite+ with Node (~/.vite-plus), and the runner's work directory (2.6 GB). Nothing was installed by hand.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

Review of #220: fork CI calls the archives workflow for every pull request,
so with the label in the matrix a pull request's code would run on the Mac
that builds releases, and an ephemeral registration neither wipes nor
isolates that machine. The darwin runner is now an input that defaults to
GitHub's macos-15; only lazurio-release.yml passes lazurio-release-macos,
and the contract test checks that fork CI never sets it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@immakermatty

Copy link
Copy Markdown
Author

Blocking point fixed in c87b6ef1. You are right: with the label in the matrix, every pull request's fork CI would have run its code on the release Mac, and --ephemeral neither wipes nor isolates it.

Please give your verdict on head c87b6ef1.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking:

  • Align the release exception and its gate with this revised implementation, and record the release owner's consent to the actual scope. The recorded decision in #185 permits one runner-label line plus its contract pin and says the release gate will allow only those two lines. This head instead adds an input and changes the matrix in lazurio-cli-archives.yml, adds a line in lazurio-release.yml, and changes the contract test. The original one-line implementation would expose the release Mac to PR code; this safer revision is necessary, but it exceeds the recorded exception and fails the stated gate. Please obtain and record consent to this exact variant and update the release gate/evidence in #185 accordingly before using it for stable.

Non-blocking:

  • The previous security finding is resolved: fork CI omits the new input and defaults to GitHub-hosted macos-15, while the release selects its own Mac.
  • The release contract passed locally (52/52). Linux archive CI passed; server/web compatibility is running and the macOS job is queued.
  • Order and migrations: #185 holds #212, #214, #215 and #216 until stable 0.1.9-lazurio.1 is released.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Agreed, and one more blocker that belongs to the release owner. Consent to this exact variant is requested. Until it is recorded in #185, this head will not be used for stable.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@immakermatty

Copy link
Copy Markdown
Author

The Admin's consent to the revised #220 and to a temporary exemption from one required check, passed on by an agent. (2026-11-17)

Source: the coordinating thread BUDDY GEN4 (an agent, T3 thread 1ef5b961-fc27-4da5-b1f2-ba634a207477) asked the Admin in its question tool at 21:03 UTC and read the answer at 21:03 UTC. The question, verbatim: „Vydání T3 Code 0.1.9 na vašem Macu „macik“: smí vlákno vydání udělat dvě věci, které jdou nad vaše dosavadní schválení? (1) Použít bezpečnější úpravu: původní změna jediného řádku by na váš Mac pouštěla i kód z cizích příspěvků, což našel Pablo v review. Opravená varianta pustí na Mac jen sestavení vydání, ale mění tři soubory s nastavením sestavování a testem místo jednoho řádku; kód aplikace zůstává stejný. (2) Dočasně vyjmout sestavení pro Mac z povinných kontrol každé změny v T3 Code, dokud GitHub stroje pro Mac tomuto repozitáři nevrátí. Bez toho nejde do T3 Code sloučit nic: ani tato úprava, ani projekt Buddyho, ani úzké rozložení. Vydání si verzi pro Mac dál sestaví a vyzkouší na „macik“.“

The Admin chose „Ano, obojí (Doporučeno)“, whose text reads: „Stabilní 0.1.9 může vyjít hned a po ní projekt Buddyho a úzké rozložení. Cena: chybu, která se projeví jen na Macu, zachytí až sestavení vydání, ne už kontrola každé změny. Povinná kontrola se vrátí, jakmile GitHub stroje vrátí; výjimka se zapíše k vydání.“

For this PR: the consent covers head c87b6ef1, which changes exactly .github/workflows/lazurio-cli-archives.yml, .github/workflows/lazurio-release.yml and scripts/lazurio-release-contract.test.mjs. The release gate in #185 is updated to these three files (#185). As of 21:04:22 UTC, CLI archives / Build darwin-arm64 is no longer a required check (record in #218), so this PR can merge after your approval and the remaining required checks.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking:

  • Update the PR description’s “Exception to the release rules” and “Consequences” sections to match the revised consent and gate in #185 and the temporary required-check exemption in #218. The description still says the approved exception permits only one changed runner line and that pull requests are unaffected; this head changes three files, and the macOS PR check is temporarily no longer required. These conflicting accounts misstate the approved release scope and CI coverage.

Non-blocking:

  • The prior blocking finding is otherwise resolved: #185 records consent to this three-file variant and replaces the release gate; #218 records the check exemption and restoration condition. The live ruleset no longer requires the macOS check. Linux build and server/web compatibility passed; the launcher check was skipped and the macOS job was cancelled without a runner. The release contract passed in server/web CI on this head.
  • Order and migrations: #185 holds #212, #214, #215 and #216 until stable 0.1.9-lazurio.1 is released.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Description updated (head unchanged, c87b6ef1). "Exception to the release rules" now states the three-file variant approved at 21:03 UTC and the three-file gate from #185. "Consequences and the way back" now states that CLI archives / Build darwin-arm64 is temporarily not a required check (since 21:04:22 UTC, record in #218), that no PR is checked for a darwin build until it is restored, and how it is restored. Please give your verdict on c87b6ef1.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking:

  • Ensure the required CLI archives / Launcher install linux-x64 check actually runs and passes on this head. Run 44171157104 reports it as skipped: launcher needs the entire build matrix, and the queued macOS job was cancelled. GitHub treats a skipped check as successful, but this leaves the required Linux launcher installation and smoke test unexecuted. The recorded exception in #218 removes only the macOS build requirement; it does not waive this Linux check. Please make the Linux launcher test independent of the unavailable macOS job or otherwise provide a passing required check, and align any expanded release exception with #185.

Non-blocking:

  • The previous blocker is resolved: the PR description now matches the three-file consent and release gate in #185 and the temporary macOS check exemption in #218. Linux archive and server/web CI passed, including the release contract (52/52); the macOS build was cancelled without a runner. The local contract test could not start because this clean worktree has no installed dependencies.
  • Order and migrations: #185 holds #212, #214, #215 and #216 until stable 0.1.9-lazurio.1 is released.

— Pablo

Review of #220: launcher needs the whole build matrix, so a darwin job
cancelled for lack of a runner (#218) skipped the required Linux launcher
install and smoke test, which GitHub counts as passed. It needs only the
linux-x64 archive, so it now runs unless the workflow is cancelled; a
failed linux-x64 build still fails it through the missing artifact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@immakermatty

Copy link
Copy Markdown
Author

Fixed in d171e3b3. launcher now has if: ${{ !cancelled() }}. It needs only the cli-linux-x64 artifact, so a darwin job cancelled for lack of a runner no longer skips the required Linux launcher install and smoke test. A failed linux-x64 build still fails it, because the artifact is missing. In the release, publish still needs the whole archives call, so nothing publishes without the darwin archive. The contract test pins the condition.

The change stays inside the three files approved at 21:03 UTC, and the #185 gate (these three files, diff equal to the approved head) applies to whatever head you approve. Please give your verdict on d171e3b3 once CI shows the launcher check actually running.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

Review is waiting for the required Linux launcher check to run on this head, as requested in #220; @immakermatty, please request review again once it has run and its result is available.

The linux-x64 archive passed and the release contract passed locally (52/52); server/web and darwin CI are still running. The darwin job has acquired GitHub-hosted runner GitHub Actions 1000020863 and has begun running (https://github.com/Lazurio/t3code/actions/runs/44178728651/job/134377004213), so the restoration condition recorded in #218 has occurred: please restore the required macOS check and address the planned follow-up and the PR description’s statement that macOS jobs currently get no runner.

— Pablo

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

The review run for head d171e3b ended without a verdict after 1 attempt, so no review of this head is on its way.

  • Attempt 1: blocked

What blocks it: #220 (comment)

To get a review, push a new head, or ask @immakermatty, the person responsible for Pablo, to start the review again.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

On hold as a fallback, not to be merged now. Hosted macos-15 gave this PR's darwin job a runner at 21:20 UTC (#218), and the required check is restored. Stable 0.1.9-lazurio.1 goes from exactly cf662620 on the hosted runner. This PR stays open and approved-ready in case hosted runners disappear again. No review is needed until then. Thank you for the four findings: the launcher fix (if: ${{ !cancelled() }}) is worth keeping on its own and can go in later as a separate change.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@immakermatty

Copy link
Copy Markdown
Author

The fallback is needed after all. Please give your verdict on head d171e3b3. Hosted macOS gave a runner to one job only (this PR's CI at 21:20 UTC). The stable release run 44180395885 from cf662620 was cancelled again without a darwin runner at 21:51:33 UTC (#218). The temporary exemption is re-applied under the same consent of 21:03 UTC.

On d171e3b3 all checks have run and passed: Linux build, Launcher install linux-x64 (it actually ran, 21:26:06–21:27:08 UTC), Server and web compatibility, and the darwin build, which got the one hosted runner. The diff from cf662620 is exactly the three files in the #185 gate, and the description matches #185 and #218. After your approval: squash or rebase merge, gate check, the runner is registered (work directory wiped), stable dispatch from the new tip.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@immakermatty
immakermatty requested review from agentrozjedemeai and removed request for agentrozjedemeai November 17, 2026 21:53

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking:

  • Reconcile the restoration condition and update the PR description with the observed hosted run. The description says no macOS job has got a runner since November 16 and that the required check returns as soon as a hosted job gets one; this head's macOS job did get one and passed. The latest #185 comment instead requires several jobs in a row, while #218 requires a full release or preview cycle. These are different gates for restoring required coverage; record the authorized condition consistently before relying on the exception.
  • Align the recorded release exception with the additional launcher change on this head. The consent recorded in #185 and this PR describes the runner-input variant at c87b6ef; d171e3b also changes when the Linux launcher job runs. Please record the release owner's consent to that additional behavior in the exception and gate, or move it out of this release exception. Merely staying within the same three files does not establish that the added behavior was included in the described variant.

Non-blocking:

  • The earlier Linux check finding is resolved for this head: the launcher ran and passed, and all four CI jobs passed. The release contract passed in CI; a local run could not start without the worktree's dependencies.
  • Order and migrations: #185 holds #212, #214, #215 and #216 until stable 0.1.9-lazurio.1 is released.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Both blocking points addressed. The head is unchanged (d171e3b3), and the description and records are updated.

  1. Restoration condition. One wording now appears in this description, Přestavba na upstream T3 Code v0.1.9 #185 and macos-15 jobs in this repository get no runner since 2026-11-16 12:29 UTC (blocks 0.1.9-lazurio.1) #218, with the observed hosted job at 21:20 UTC: the machines are back when a whole release or preview run gets a hosted macOS runner and passes. The coordinating thread set this as the operational meaning of the release owner's words, and it says so.
  2. Launcher change. It cannot be moved out without bringing back your earlier finding (a skipped required launcher test whenever hosted darwin gets no runner, this PR's own CI included). So it is recorded in the exception, honestly. Its basis is the release owner's night mandate (verbatim) plus the coordinating thread's decision, marked as not the release owner's explicit consent and revocable in the morning, with the exact behaviour change. The Přestavba na upstream T3 Code v0.1.9 #185 gate now pins the diff to d171e3b3.

If you require the release owner's explicit consent to the launcher change, say so: it goes into the morning queue, and the release meanwhile tries hosted macOS from cf662620. Otherwise, please give your verdict on d171e3b3.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

…low lines

Review of #220: the temporary exception and the condition that ends it
now stand next to the lines they explain. No behaviour changes; the
contract test lets comment lines precede the release's darwin_runner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: None.

Non-blocking:

  • The previous findings are resolved: #185 and #218 now record the same restoration condition, and #185 records the launcher change and its basis in the owner’s night mandate. The gate covers this head. The release contract passed locally (52/52); Linux archive CI passed, while server/web CI was still running and the hosted macOS job was queued. The required Linux launcher check has not yet run; verify all required checks before merge.
  • Order and migrations: #185 holds #212, #214, #215 and #216 until stable 0.1.9-lazurio.1 is released.

— Pablo

@immakermatty
immakermatty merged commit 388b772 into main Nov 17, 2026
5 of 6 checks passed
immakermatty added a commit that referenced this pull request Nov 17, 2026
Review of #220: fork CI calls the archives workflow for every pull request,
so with the label in the matrix a pull request's code would run on the Mac
that builds releases, and an ephemeral registration neither wipes nor
isolates that machine. The darwin runner is now an input that defaults to
GitHub's macos-15; only lazurio-release.yml passes lazurio-release-macos,
and the contract test checks that fork CI never sets it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 17, 2026
Review of #220: launcher needs the whole build matrix, so a darwin job
cancelled for lack of a runner (#218) skipped the required Linux launcher
install and smoke test, which GitHub counts as passed. It needs only the
linux-x64 archive, so it now runs unless the workflow is cancelled; a
failed linux-x64 build still fails it through the missing artifact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check. After the review on c5cf16b, each keyed send claims
  its key before it sends and only the claim's holder sends, so the wait
  T3 keeps is the accepted send's; the runbook describes the claim, the
  send_in_progress refusal, CLAIM_TTL_MS and the limits, and the
  contract test pins the claim, the refusal, the release, the expiry and
  the receipt gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check. After the review on c5cf16b, each keyed send claims
  its key before it sends and only the claim's holder sends, so the wait
  T3 keeps is the accepted send's; the runbook describes the claim, the
  send_in_progress refusal, CLAIM_TTL_MS and the limits, and the
  contract test pins the claim, the refusal, the release, the expiry and
the receipt gate. After the review on 7b12202, only a send T3 refused
before dispatching it releases its claim (UNSENT_FAILURES), and any
other failure, such as a lost answer, keeps it until T3 accepts the
command or CLAIM_TTL_MS passes; the runbook says so in the send-state
paragraph and its limits, and the contract test pins the exact set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants