[immakermatty]

Status: draft, for CI and review only. This PR is never merged by its button. Its head becomes main through the swap in stage 6 of docs/operations/lazurio-fork-release.md, after the current main is captured by an immutable release tag.

Rebuild issue: #112 (inventory and every row's decision).

Inputs

Old base	v0.1.1 = fe27e8e3dc12dcbb108e9a28fd9b8cb65f34ae92
New base	v0.1.2 = 044f07257c9684ae4543bd1e1ebf9c394e9e3830 (tag upstream-v0.1.2)
expected_old_main	Not final. main is 788fd715 (#106, #113 and #110 since stable 0.1.1-lazurio.1 captured 626cf804), and all three are replayed here. Preview 0.1.1-preview.20261023.1 is built from 788fd715 and goes to Ring 0. The stable 0.1.1-lazurio.2 will capture main, and this value is set to it before the swap.
candidate_head	25d9a218245e2ab338aba16c651f7860d81a8549

What the rebuild does

The overlay is replayed onto v0.1.2 as one commit per row, in the target stack's order, with row 5 (distribution) last: 28 commits. Rows 23–28 come over as one commit each, and row 29 is a backport (below). Each commit message says what changed on the new base.

Main problem solved. Upstream v0.1.2 adds its own t3 thread list|start|send|show (pingdotgg#22732). A plain replay registers two thread groups, and t3 (the server included) fails to start with "Duplicate subcommand". Row 21 now builds one group: the overlay's subcommands, plus every upstream subcommand whose name the overlay does not use (today start and show).

Other rebuilds:

• Row 4: the update offer follows its seams into chat/useSystemComposerBanners.tsx and settings/SavedEnvironmentRows.tsx. A missed site would silently offer the client's version, so a new contract pin forbids .clientVersion in web sources.
• Row 13: Nová karta declares its tool letters in data-surface-launcher-keys, as upstream's launcher does since fix(web): right panel launcher letters open their surface instead of typing into the composer pingdotgg/t3code#22898. Without it the composer's type-to-focus would take them. Covered by a browser test and a pin.
• Row 15: the prompt-link guard sits in both message rows of the new chat/TimelineUserMessageRow.tsx, including the automation row (feat: show automation messages as compact timeline rows pingdotgg/t3code#22638).
• Rows 25 and 26:
  • the Buddy surface field moves to chat/timelineRowContext.ts and the hidden fork button to chat/TimelineAssistantRows.tsx;
  • the page reference moves to chat/useComposerSend.ts, and the fallback chip to chat/UserMessageContextChips.tsx.
• Row 27 (who acted, feat(lazurio): a thread shows when Buddy sent a message or decided a request, and hides Delegace's wake #106):
  • v0.1.2 folds an agent's message into one row, labelled with its sender thread or else "Agent" (feat(web,mobile): messages from other agents fold into one-line rows pingdotgg/t3code#23135), in chat/TimelineUserMessageRow.tsx. The „Buddy za “ label now wraps that row's label, and FoldedMessageHeader takes a ReactNode.
  • The rows hook that hides Delegace's wake stays in MessagesTimeline.tsx. The mark at a decided request moves with the work row to chat/TimelineWorkEntryRow.tsx.
  • Two test adjustments: one test's expected message id follows the test world's ids, and the v0.1.2-only case of row 24's test sends as Delegace too.
• Row 28 (Buddy's chat like a chat with a friend, feat(lazurio): Buddy's chat reads like a chat with a friend #113):
  • The composer's controls live in chat/ComposerControlsBar.tsx (refactor(web): the composer's footer controls render in ComposerControlsBar pingdotgg/t3code#23058). The thread's error banner renders in chat/ChatBannerLane.tsx (refactor(web): ChatView's timeline banners render in ChatBannerLane pingdotgg/t3code#23101), and chat/useThreadLifecycle.tsx makes the work banners ChatView joins.
  • buddyBackgroundWork is whether the background-work banner exists. It exists exactly while such work runs.
  • In Buddy's surface the error banner also drops T3's error code, which would otherwise pick T3's ChatGPT usage-limit text.
• Row 29, backport of upstream fix(deps): pin all patched package versions pingdotgg/t3code#23798 (22840ab943, not in v0.1.2): every patched package is pinned in pnpm-workspace.yaml's overrides. Without it no release has passed since 2026-10-23 20:13Z: the CLI archive's install without the lockfile took node-pty 1.2.0-beta.17 once it was old enough, and the patch for 1.2.0-beta.15 went unused (ERR_PNPM_UNUSED_PATCH, release run 40017408531). The lockfile changes only in overrides, catalogs and specifiers. The row is dropped at the rebuild onto the first tag that contains fix(deps): pin all patched package versions pingdotgg/t3code#23798. main gets the same fix in fix(deps): pin all patched package versions (upstream #23798) #117.
• The brand licence (docs(lazurio): the Lazurio brand assets stand outside the MIT licence #110): apps/web/src/lazurio/brand/README.md comes with row 25. The README, the runbook and the release notes' licence lines come with row 5.
• Tests upstream deleted (test: delete 11k low-signal tests so CI runs faster and flakes less pingdotgg/t3code#22557 and others): their overlay cases move into the overlay folders, for example lazurio/environmentLabel.test.ts, lazurio/branding.test.ts, lazurio/managedFolderVcs.test.ts, lazurio/questionTool.test.ts and cli/auth.test.ts.
• v0.1.2's five test-lint rules: the overlay's tests follow them. Frame waits became retrying assertions, fakeTimers use the full set, per-test timeouts are gone, wall-clock reads became fixed times, and real-time fixtures carry reasoned exceptions.
• Toolchain: Node 26.12.1, pnpm 12.14.0, @tsc-rs/typescript 0.8.0 and Vite+ 1.3.0 in CI, the release and the image. VP_NODE_VERSION is removed. CLI archives build 0.1.2-lazurio.0.

What people and agents will notice

• t3 thread send now defaults to --mode queue: a busy thread gets the message as its next turn and nothing is interrupted. Delegace always passes --mode queue.
• New on send:
  • - reads standard input; --message-file - stays;
  • --wait prints the reply, exits 1 if the run fails and 2 if the thread waits for an answer.
• t3 thread launch starts in the project's default runtime mode (upstream's launch now applies project defaults to outside callers). That default is full access unless changed.
• Upstream's t3 thread start and t3 thread show are available beside the overlay's commands.
• Unchanged: sessions keep their t3 agent cli label, which keeps Delegace's send namespace. Buddy's chat and the „Buddy za …“ mark behave as on main.

What stays the same (stage 5)

• Database: v0.1.2 adds no migration, so it is the same statev2.sqlite and a return to v0.1.1 leaves it as it is.
• Protocols: launcher protocol 3 and orchestration protocol 2.
• Auth: scopes and the default pairing grant are unchanged (auth.ts and RpcAuthorization.ts are identical).
• Overlay commands: t3 lazurio outputs are unchanged and pinned byte for byte.

Allowlist, test gate and pins

• Allowlist: 89 → 94 entries (main → this head), exactly the upstream files this overlay changes.
  • Out: four upstream-deleted tests, packages/ssh/src/tunnel.test.ts and CodexDeveloperInstructions.test.ts.
  • In: the ten files upstream moved seams into, plus cli/thread.ts (one export for runResultText).
• Test gate: three deleted paths removed (ServerEnvironmentLabel.test.ts, VcsProvisioningService.test.ts, RightPanelTabs.keyboard.browser.test.tsx).
• Contract test: 46 tests. Pins follow the moved seams, and new pins cover the silent risks above. One of them is the agent commands' multi-line session issue with the acting sender (rows 24 and 27).

CI on this head

Lazurio Fork CI run 40019208350 (workflow_dispatch on 25d9a218, because the PR conflicts with main by design) is running. Its CLI archive builds are the proof for row 29, because the release age that broke them has passed. The previous head 6eb03a43b7 was green in run 39989366643.

Verified locally (macOS, Node 26.12.1, pnpm 12.14.0)

On 25d9a218 (row 29 added): the contract test passes 46 of 46, vp fmt --check is clean, and pnpm install --lockfile-only leaves row 29's lockfile unchanged. Its 25 pins equal the versions the lockfile already resolved. Everything below was verified on 6eb03a43b7, which differs from this head only in row 29 and five lines of the runbook.

• Every row against main: each changed line of rows 27 and 28 and of docs(lazurio): the Lazurio brand assets stand outside the MIT licence #110 compared with its source on main. The differences are only the v0.1.2 seams above, and row 24's commit subject names Delegace as main's table does.
• node --test scripts/lazurio-release-contract.test.mjs: 46 pass.
• Allowlist guard: emulated in both directions, with no unexpected file and no stale entry.
• vp fmt --check: clean over the whole repository.
• pnpm run lint: exits 0. Its warnings are all on upstream lines that warn on plain v0.1.2 as well.
• Typecheck: vp run --filter t3 typecheck and vp run --filter @t3tools/web typecheck exit 0.
• CI's "Test what the overlay changes", replayed locally:
  • apps/server: 70 files and 822 tests pass, with 1 file and 14 tests skipped.
  • packages/contracts, packages/shared and scripts pass.
  • apps/web, on the second run: 40 of 42 files and 1,720 of 1,723 tests pass. In the first run Vite's dependency optimizer reloaded mid-run, so 8 files did not import.
  • The 3 failures came with "Cannot verify that chromium request interception is active after 5s" and a 15 s pointer-reset hook timeout. Their two files (buddySurfaceControls.browser.test.tsx, buddySurfaceDayJump.browser.test.tsx) pass alone, 4 of 4, and CI ran them green.

Not verified locally

• The image build on Node 26 and pnpm 12, and the workflows themselves (pnpm/action-setup with pnpm 12). CI checks both.
• The overlay's CDP tests, which run by hand on a canary Environment (stage 7).
• The Ring 0 canary (stage 7), which additionally checks that the Lazurio Folder project in Chat defaults to full access. Before it, the Buddy rows' builder verifies the released preview artifact.

Follow-ups

• Buddy rows 23–28: reviewed by the thread that owns them. Rows 23–26 were reviewed earlier; rows 27 and 28 were reviewed on 6eb03a43b7, from the code, relying on the green CI above.
  • The „Buddy za …“ label in the folded row and the mark at a decided request were reviewed by the thread that built them, too. That thread verifies the released v0.1.2 preview artifact (the folded row's label in Czech and English, the hidden wakes, the refusal of budicek) before it goes to Ring 0.
  • The usage-limit wording in Buddy's error banner ("try again" does not help there) is a follow-up in Buddy surface follow-ups: layout echo, T3 shortcuts in the panel, live day pane, user-facing app names in the page block #109.
• expected_old_main set to what 0.1.1-lazurio.2 captures, before the swap.
• Stage 9: upstream offers (Let `t3` install and update from another repository's GitHub Releases (`T3CODE_RELEASE_REPOSITORY`) pingdotgg/t3code#21562 and others).

🤖 Generated with Claude Code