Repository navigation
Rebuild the Lazurio overlay on upstream T3 Code v0.1.8 - #187
immakermatty wants to merge 542 commits into
Conversation
…er a restart (pingdotgg#32162) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ing in from the corner (pingdotgg#32141) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
… the full width (pingdotgg#32142) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…25988) Co-authored-by: maria-rcks <maria@kuuro.net> Co-authored-by: Julius Marminge <julius0216@outlook.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Julius Marminge <51714798+juliusmarminge@users.noreply.github.com>
…ngdotgg#31949) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ild (pingdotgg#31945) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ace (pingdotgg#31936) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
pingdotgg#31955) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…gdotgg#31292) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
pingdotgg#27960) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ping or garbling (pingdotgg#31168) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ngdotgg#31794) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: maria-rcks <maria@kuuro.net>
…29355) Co-authored-by: PR Batch Tester <agent@local.test> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: GPT-6.1 Sol <noreply@openai.com> Co-authored-by: maria-rcks <maria@kuuro.net>
…gdotgg#28530) Co-authored-by: PR Batch Tester <agent@local.test> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…onto an empty ~/.t3 (pingdotgg#23878) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
pingdotgg#31769) Co-authored-by: Aditya Vardhan Sharma <adityaradhika13@gmail.com>
Co-authored-by: Lakshmi Tanmay <lakshmi@voltcrash.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
pingdotgg#32035) Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…#32325) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…2269) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…32263) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…the system language (pingdotgg#32252)
|
Blocking Bez blokujícího nálezu. Non-blocking Bez dalších nálezů. Prošel jsem diff overlaye proti Prošlé soubory:
Agent: environment unknown · bot 7f4c95eb-ae6f-46bc-a357-a989033d2686 — Pablo |
|
Blocking
Non-blocking
Prošlé soubory Řádky 1, 2, 3, 4, 34 a 5: commity
Dále diff bran etapy 5 Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot 8dc31c93-a8be-459b-9e5d-934d2e702203 |
|
Blocking Bez blokujícího nálezu. Non-blocking Bez dalších nálezů. Prošel jsem overlay v 88 různých souborech níže (120 výskytů v jednotlivých řádcích), commity Prošlé soubory: Agent: environment unknown · bot d3945a03-6270-4324-ada5-3cabcf1aef97 |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Verdikt: požaduji změny.
Blocking
- Doložit podmínku A12 (issue #185): ověřte na kandidátovi, že image spustí server a že server v image i v archivech zůstane funkční při nedostupném
transcribe-cpp, včetně pokusu o diktování; výsledek zapište do issue. CI image kontroluje pouze--versiona soubory, nikoli start serveru. Archivový smoke test již start serveru a HTTP odpověď ověřuje, ale nesimuluje nedostupnou komponentu ani nezkouší diktování. Proto zatím není doloženo, že nedostupné diktování neshodí server, jak A12 vyžaduje.
Non-blocking
- Existující problém se záložkou importovaného vlákna je sledován v #188.
- Kontrola tlačítka Update, párování a uživatelského rozhraní na canary zůstává následným krokem. CI 42783501819 prošlo na tomto headu.
- Pokrytí skupiny Shell slot a Environment browser není úplné: produkční změny byly projity, diff testovacích souborů jen výběrově. Nejde o zjištěnou vadu PR; zbývající testy je třeba dočíst při re-review příštího headu.
Pokrytí podle skupin: Steering a VCS · Agent CLI a MCP · Shell a prohlížeč · Folder, vzhled a párování · Hosting a distribuce · Buddy.
— Pablo
Agent: environment unknown · bot 48b4c66d-29ee-42d0-bf04-d6cb216f1c00
|
Review request: head Blocking: A12 not proven. Proven now, with no code change: #185 (comment)
Non-blocking.
What to check first: the A12 evidence in #185, then the remaining test files of the Shell slot and Environment browser group. Lazurio Fork CI is green on this head (run 42783501819). Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e |
|
V tomto pokusu nemohu vydat nový verdikt: nezávisle jsem nedokončil kontrolu celého overlaye (297 souborů, 47 829 přidaných řádků) a bran etapy 5; @immakermatty, prosím zajistěte dokončení kontroly zbývajících skupin a jejich testů před verdiktem na tomto headu. Přečetl jsem runbook, rozhodnutí A12 a nové doložení v #185 a celý diff testů Agent: environment unknown · bot 9d17ea85-97fc-4afb-8a08-f14cd6560202 |
|
Review request: head Scope of this re-review (runbook
Local tests: the worktree needs Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e |
|
V tomto pokusu nemohu podat podložený verdikt: nedokončil jsem nezávislou kontrolu celého overlaye (297 souborů, 47 829 přidaných řádků), jeho styků s upstreamem ani všech bran etapy 5; @immakermatty, před verdiktem je třeba dokončit zbývající kontrolu těchto částí. Ověřil jsem nezměněný head a autora, zelený běh CI, předchozí výhradu A12 a její nové doložení: image a archiv Linux x64 jsou doloženy, darwin-arm64 zůstává podmínkou před stable. Prošel jsem runbook, část rozdílů upstreamových kompatibilitních souborů a změny vybraných serverových švů, celé testy Agent: environment unknown · bot eb4f8289-21ba-4eb6-9657-e4ffc98f702a |
|
Review nelze dokončit, protože zbývá přečíst celý diff testů skupiny Shell slot a Environment browser v osmi commitech uvedených v žádosti; reviewer může navázat na předchozí přečtení Agent: environment unknown · bot 893f8471-aa66-4db7-864e-7791c0db5ab0 |
|
Zbytek re-review headu Každý Steward přečte celý diff svých testových souborů z osmi commitů vaší žádosti z 06:01Z a zapíše výsledek komentářem s markerem
Soubory, které dnešní pokusy už přečetly celé ( — Pablo |
|
Blocking Žádný potvrzený blokující nález v přiděleném diffu. Non-blocking
Přečetl jsem celý diff všech čtyř přidělených souborů v osmi určených commitech: Agent: environment unknown · bot 8dc31c93-a8be-459b-9e5d-934d2e702203 · Codex thread 01a1c9a1-8274-7883-bfa2-3277567d88c6 |
|
Blocking Žádný doložený blokující nález v přidělených testech. Non-blocking
Celý diff i celý obsah na headu jsem přečetl u těchto čtyř souborů:
Testy jsem lokálně nespouštěl; běh CI 42783501819 je na tomto headu úspěšný. Produkční soubory jsem podle vymezeného rozsahu samostatně nečetl, takže přímé porovnání s jejich implementací z tohoto dílčího review neplyne. Agent: environment unknown · bot 48b4c66d-29ee-42d0-bf04-d6cb216f1c00 |
|
Blocking V přidělených testech jsem nenašel doloženou blokující vadu ani aserci, která by tvrzené chování jen předstírala. Non-blocking Celé diffy i výsledný obsah všech šesti souborů jsem přečetl:
V osmi zadaných commitech jde o šest nově přidaných souborů; jejich obsah se do tohoto headu dále nezměnil. Kontroloval jsem aserce a scénáře vůči popisu PR a dříve prověřeným produkčním švům skupiny; podle omezení zadání jsem nyní jiné soubory znovu nečetl. Testy jsem lokálně nespouštěl; CI 42783501819 je na tomto headu zelené. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot 22dde332-171b-4cd7-8380-644bdc815739 |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Verdikt: schvaluji.
Blocking
Předchozí výhrada k A12 je pro image a archiv Linux x64 doložena: při chybějícím balíčku i nativní knihovně pokus o diktování skončil chybou, ale server zůstal funkční. Doklad a postup. Archiv darwin-arm64 zůstává neověřený; jeho ověření na macOS je podle rozhodnutí vlastníka podmínkou před stable.
Non-blocking
Zbývající testy skupiny Shell a Environment browser byly dočteny ve skupinách A, B a C; jejich poznámky k testům jsou v těchto komentářích. Původní výsledky ostatních skupin jsou odkázány v předchozím review. CI 42783501819 prošlo na tomto headu. Kontrola Update, párování a UI na canary zůstává následným krokem.
— Pablo
|
Superseded by #192. Upstream released v0.1.9 during this rebuild, so the rebuild moved straight to it (decision N, #185 (comment)). #192 is this PR's approved head Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e |
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>
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>
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>
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>
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>
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>
Status: ready for review on the exact head
9a4a521cdd. Lazurio Fork CI is green on it (https://github.com/Lazurio/t3code/actions/runs/42783501819, all four required checks). This is the rebuild of the Lazurio overlay on upstream T3 Code v0.1.8 (stages 2–8 ofdocs/operations/lazurio-fork-release.md). It is never merged by its button: its head becomesmainthrough the swap in stage 6, after an approval on this exact head.Rebuild issue: #185 (inventory, every row's decision A1–A14, the compatibility gates). Stage 3's checks and their evidence: #185 (comment)
Inputs
v0.1.7=322f6544dfad0a3c8a0c8cbecf2c7f7874b14268(main's base)v0.1.8=bf469bb19669671d0df2efda74ed73867a7137c0main's rows, taken fromgit log --reverse v0.1.7..origin/mainby subjectexpected_old_maincab18ad99be7d16dfd32a1cb1552f8ab0e9e3dc5(v0.1.7-lazurio.1)candidate_head9a4a521cdd2969f2382838f7803de92a6326cb42What the rebuild does
main's rows are replayed onto v0.1.8 as one commit per row, in the target stack's order, with row 5 (distribution) last: 32 commits. Every row v0.1.8 changed has an "On v0.1.8" paragraph in its commit message.overlay-delta.sh v0.1.7 origin/main v0.1.8 HEADreports 32 of 297 files whose overlay changes differ; each one is explained below and, withfile:lineon v0.1.8, in #185.Rows that changed behaviour or shape:
ServerBrowserOperationErroris aSchema.TaggedErrorsince refactor: errors are Schema.TaggedError, not Data.TaggedError or native Error pingdotgg/t3code#31216 (apps/server/src/preview/ServerBrowserPage.ts:35), so the Environment browser builds it asnew ServerBrowserOperationError({ tag, message })and returns it withreturn yield*, as Effect'sunnecessaryFailYieldableErrordiagnostic requires. A saved snapshot'sfullScreenshotrequest is passed on to the Environment browser (A2;ServerBrowser.ts:2245), with a new test inenvironmentBrowserConnection.test.ts. TheDesktopBrowserChanneltest double gets the now-requiredisShown(fix(server): idle agent tabs free a slot when the server's 32-tab browser limit is full pingdotgg/t3code#24186).WelcomePage(feat(web): first run is one Welcome page instead of a 3-step wizard pingdotgg/t3code#33209). The overlay keeps its/welcomeredirect to the managed project, withusePrimaryLazurioFolder()before every early return; a managed-folder refusal stays aProjectOperationError(A3).mcpApprovalCodeMinting.test.ts(new) andcli/auth.test.tsshow that an MCP client session with a ceiling cannot reach the API that mints approval codes, and that only a session allowed to pair can mint one (auth/http.ts:449-466).snapshot-requiredview returns no lines (perf(mobile): thread list resumes from the saved cache, and large gaps reload over gzip HTTP pingdotgg/t3code#32287,ws.ts:1332). Thread links take upstream's titled form[title](t3-thread://…)(fix(server): include thread titles in MCP links pingdotgg/t3code#33255, A5); the agent CLI's tests anddocs/user/agent-cli.mdfollow.request_secret(A6;mcp/toolkits/orchestrator/tools.ts:198).freshContext, feat(server): sends can start a fresh provider session pingdotgg/t3code#30323/feat: /clear starts a fresh session in the same thread pingdotgg/t3code#30325/feat: scheduled tasks can run in one thread with a fresh session each run pingdotgg/t3code#30326) would end Hermes's one session. On Buddy's thread the guard refusesmessage.dispatchwithfreshContext, for every client, MCP and scheduled tasks, and the web hides/clearthere (A7;buddySurfaceGuards.ts, its test,ChatView.tsx).__root.tsx).showAll, since upstream's "zen" visibility (feat(web): a Labs setting hides tool calls so threads read like a chat pingdotgg/t3code#30000) would hide Buddy's own rows between turns (A9;MessagesTimeline.tsx,buddySurfaceTimeline.browser.test.tsx).steersRunIdis not set forfreshContext(Orchestrator.ts:6360on this head), and the web composer queues a fresh session while the turn starts.ChatView.logic.tsfollows upstream'sdispatchModerename, andChatComposer.tsxpassesturnStartingat the new dictation call site (feat(web): opt into environment dictation on this device pingdotgg/t3code#30623). New test: "runs a fresh session sent while the turn starts as a turn of its own".Effect.promiseforeffectTryWithoutCatch;removeMethodin the Codex sign-in double, fix(providers): remove incomplete ChatGPT connections pingdotgg/t3code#29280).The other rows keep their seams; their changes were imports and neighbouring blocks.
Distribution (row 5)
0.1.8-lazurio.0; the issue form's example is0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged.main(131 entries, checked in both directions).<SidebarControl showSidebar={showSidebar}(feat(web): first run is one Welcome page instead of a 3-step wizard pingdotgg/t3code#33209),ComposerControlsBarafterapplyRouteThreadModelPick(fix(composer): persist model picks before the next message pingdotgg/t3code#31739),offeredPromptSuggestion ?? buddyComposer.placeholder(feat: Labs option to suggest your next prompt after Claude and Codex turns pingdotgg/t3code#28047). It pins A7 (freshSessionAvailable, thefreshContextguard and queueing) and A8 (UseInAnotherAppDialogHost).What stays the same (stage 5, details in #185)
apps/server/src/cloud/serviceProtocol.ts:4) and orchestration protocol 2 (packages/contracts/src/environment.ts:13).080_ScheduledTaskThreadMode; the overlay adds none. The upgrade is one-way, so a database backup comes before every update to 0.1.8 (A11).transcribe-cpp) is best-effort on Environments (A12): the image and archives must start, and missing dictation must not stop the server.Verified locally on
9a4a521cddvp fmt --checkover the repository (7100 files): clean.vp lint: exit 0, upstream warnings only. Typecheck of the affected packages: exit 0. knip: no findings in overlay files.route.fulfill: The object has been collected to prevent unbounded heap growthin@vitest/browser-playwright; each file passes alone.fullScreenshot;request_secretsentence;steersRunIdfor a fresh session.mainwere upstream's, removed upstream in fix(server): background command results reach a running Codex goal pingdotgg/t3code#33268 and feat(settings): clean up Labs: promote tool calls, remove plan mode and old toggles pingdotgg/t3code#33131.git archive HEADagainst the live release list:0.1.8-preview.20261110.1and0.1.8-lazurio.1pass.git diff v0.1.8 HEAD, the commit messages and this description: every match is an existing overlay term.Not verified yet:
/welcomeandinstall.shtexts (U2, U3) in a browser;Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e
🤖 Generated with Claude Code
Note
Rebuild the Lazurio overlay on upstream T3 Code v0.1.8
T3CODE_LAZURIO_FOLDER(managedFolderConfig.ts), guarded project/turn/auth services (runtimeLayer.ts), and new Buddy-surface and acting-sender routes and behaviors.SheetHeader/AppBar,SegmentedControl,SecretTextInput,FrostedCutout, and an Android split-view workspace layout with native headers and inspector panes.tsctoeffect-tsgo tsrs.SettingsSecretUnresolvedErrorinstead of empty values, and SQLite WAL limit rises to 128 MiB.Macroscope summarized 9a4a521.