[immakermatty]

Status: ready for review. Phase A, part 2 of plan DEV-6646, on main after #64 (rebase-merged as 35a31c0). Lazurio Fork CI is green on the exact head ffde629 (see Verification). Nothing here is released.

Why

On 2026-10-13 the Admin approved a cleanup of the fork before its next stable releases and the move to upstream v0.0.46. Part 1 (#64) made CI test what the overlay changes and said what the overlay is. This part does what the plan calls A3, A4 and A6, under the approved decisions:

• D9, the managed Folder (LazurioPlatform F51) now, with its behaviour fix. Without T3CODE_LAZURIO_FOLDER the fork must behave as upstream, and it did not: "Add project" disappeared from the command palette and the sidebar whenever no Environment could take a project, which also removed upstream's way to Settings → Connections. The managed Folder was also the overlay's largest upstream footprint (about 30 upstream files, its web seams mostly re-indentation), the least guarded part (no seam guard, an untested reactor guard), and the reason full vp lint failed on main (Lint fails on main: the managed Folder's engine tests exceed upstream's ManagedRuntime ceiling #63).
• A4: dead code, duplicated helpers, small faults and stale comments of the Environment browser overlay.
• D5, the welcome's language: the managed welcome was English only, while the rest of the overlay follows prefersCzech (Czech with formal address, root decision 0199).

Commits

Each commit stands alone and is one release-note line; each was checked on its own (Verification).

1. fix(web): "Add project" stays unless every Environment is managed — the palette and the sidebar ask one overlay helper, everyEnvironmentManaged: "Add project" leaves only when the web knows at least one Environment and every one is managed (an Environment whose config has not arrived counts as not managed). Without the variable, including with no Environment at all, both behave as upstream, and the palette's "Add project" leads to Settings → Connections again. The runbook no longer lists this as a known deviation.
2. fix(web): the managed welcome shows only on the welcome route, like the wizard — upstream renders its wizard only while the location is still /welcome, because the root shell can remount the route's pending outlet after the location changes. The managed welcome returned before that guard, so after "Start in Lazurio" it could show again, with an enabled button, while the new chat's route loaded. It now sits behind the same guard; welcome.tsx's seam is one import and two lines.
3. fix(web): a prepared prompt opens in a managed Environment's Lazurio project — the Launchpad's "+ Nový modul" prompt names <Folder>/organizations/<directory> as its cwd; the prompt overlay added a project there, which a managed Environment refuses, so the prompt failed ("Could not open the prepared prompt") wherever the Folder was managed. In a managed Environment it now opens in the Folder's own project, where every new thread starts anyway, and adds nothing; the prompt text names the Organization. Unchanged without the variable.
4. refactor(web): the managed Folder's web seams shrink to their real lines — upstream code stays in place and the overlay decides beside it: DraftHeroHeadline.tsx 182 → 7 changed lines, CommandPalette.tsx 81 → 12, FirstRunGate.tsx 63 → 6, useHandleNewThread.ts 16 → 5 (one managedNewThread call; its branch inside resolveDefaultEnvMode was unreachable). managedFirstRunDecision returns only the decision (its persistCompletion was always false).
5. refactor(server): the managed Folder's server code moves into the overlay folder — t3 lazurio moves verbatim to apps/server/src/lazurio/cli.ts; the Folder's config (T3CODE_LAZURIO_FOLDER, T3CODE_LAZURIO_TOOLS_URL) to managedFolderConfig.ts, which cli/config.ts spreads over its result and which also turns the cwd bootstrap off, so the three autoBootstrapProjectFromCwd && lazurioFolder === undefined checks in startup are upstream's again; one guard in managedFolder.ts for the provider reactor and the VCS service, and one for the engine (3 lines in OrchestrationEngine.ts); ws.ts gives clients the Folder through one helper; reconcileRecommendedModel is optional on the settings service, whose writer takes the function to apply inside its lock, and its pure part moves out of packages/shared into modelRecommendation.ts, so the five upstream test fixtures, the test layer, serverSettings.test.ts and packages/shared/src/serverSettings.ts are upstream's again; one routeAuth.ts for both overlay routes, so http.ts is upstream's again; the wrong "Compare-and-set" comment in packages/contracts/src/settings.ts is gone. New tests: cli.test.ts pins t3 lazurio's output, the Folder config, the guards on a real filesystem with symlinks, the VCS refusal, and the reactor guard (a turn whose workspace no longer resolves to the Folder starts no session). The allowlist drops the files that are upstream's again and adds the reactor's test.
6. fix(server): the model recommendation route knows the Folder by its canonical path — the route compared the requested folder with the canonical configured Folder as raw strings. The Platform sends realpath(folder), so it matched, but a symlink or a trailing slash got 409. It now resolves the request the way the reactor and the VCS service do.
7. test(server): the managed Folder's engine tests run on test layers; fork CI lints (#63) — the two managed engine tests added two ManagedRuntime.make runners over upstream's ceiling of five for OrchestrationEngine.test.ts; they now run as @effect/vitest live tests over the engine's test layer, and full pnpm run lint passes. Fork CI now runs upstream's lint script after the formatter, as upstream's vp check does; the release contract keeps the step. Fixes Lint fails on main: the managed Folder's engine tests exceed upstream's ManagedRuntime ceiling #63 (merging closes it).
8. test: the release contract keeps the managed Folder's seams — the guard every other feature has: it pins each hook in an upstream file (bin.ts, the config spread, the engine's command guard before a command is decided, the reactor's turn guard before a session starts, the VCS guard before a driver runs, the startup adoption, the settings hook, ws.ts, the contract fields; the palette, the sidebar, the hero, the first-run gate, the new-thread hook, the scratch project, the git actions, the welcome behind upstream's route guard) and requires every file to be the overlay's or on the allowlist. Disabling the palette's condition or the reactor's guard fails it.
9. refactor(lazurio): the overlay drops dead code and keeps one copy of its helpers — server: the snapshot's per-tab view (never read: the web builds <viewOrigin>/t/<tabId> itself since the panel first showed the tabs), DaemonSeams.read, exports without importers (askDaemonSocket, daemonProcessId); letGo now drops what it lets go (three loops merged); one label rule (holderLabel). Web: info.tab and closed.tab of the view's messages; one originOf, panelOf and snapshotOf; upstream's surfaceShortcutTargetsTypingContext instead of a copy; postThreadTab, restoreTabs, runTool and chooseInNewTab are module-private.
10. fix(web): a tab that ends as the panel's last one closes the panel, like × — the overlay's removal of an ended tab lacked upstream's rule that the panel closes with its last surface. It now matches closeSurface rule for rule, and a test runs upstream's closeSurface and the overlay on the same panels and requires the same result. It stays an automatic update: closeSurface counts as the person's choice, and one during a turn holds back the panel upstream opens by itself when the turn completes.
11. fix(server): the Environment browser overlay forgets what it no longer needs — a failed lookup of a session's thread was cached for good, so tabs an agent bound after its thread came back (unarchived) never reached the strip (tested); a tab's lock now goes with its last operation, and the host remembers the latest 256 other Environments' tabs instead of all of them; the host's interface ThreadTabs, which shadowed the service module of the same name, is HostThread; foreignView's orphaned JSDoc is back on it.
12. fix(web): a hold the server keeps failing stops retrying after about a minute — a hold retried a 5xx every 30 s for as long as the tab stayed in the strip. It now tries six more times over about a minute and then ends as a refusal does: the tab stays as the device's own, with the same warning (tested).
13. chore(lazurio): overlay comments say what the overlay does today — the session name's deleted web copy (in agentBrowserSession.ts and the release contract), the panel's retired own tab, and overlay.ts and server.ts now naming the model recommendation route.
14. feat(web): the managed welcome speaks Czech where the person's browser does — the same rule as the rest of the overlay, formal address (0199), "Environment" for the place (0170), the Lazurio Folder as the Environment's own pages name it. English text and behaviour unchanged.

What deliberately does not change

• t3 lazurio capabilities and t3 lazurio model print the same bytes. The command moved without a change; cli.test.ts now pins {"version":1,"managedFolder":true,"modelRecommendation":true}, the metadata reads ({"version":1,"current":…,"lastManaged":…}, nothing created in an empty base directory), the offline refusal ("The T3 service must be running. No settings were changed.") and a live apply through the route. Before/after runs of the real CLI (node apps/server/src/bin.ts lazurio …) are byte-identical, help included.
• The refusal words merged in fix(server): the managed Folder's refusals say what happens in plain words #61 are the same, each for the same refusal; they now live in apps/server/src/lazurio/managedFolder.ts.
• What the managed Folder does on a managed Environment: startup adoption, the command and turn guards, the model reconciliation, the welcome's English text.
• Not in this PR: the C1–C7 duplicates (both browserView.ts, the 32-hex id rules, isViewOf) for task 703, the broker's dead sort terms for phase C, the v2 event branch in threadLifecycle.ts, the README and any "Lazurio T3 Code" naming (phase B), the design system's look, the panel's head row and tab menu.
• Left on purpose: VersionMismatch.clientVersion in versionSkew.ts is upstream's field, which upstream main still reads; deleting it would add upstream-line deletions to the overlay for a field the overlay only writes. SidebarThreadHeader.tsx keeps its conditional button (6/4 lines): hiding it needs the three lines of the button one level in.

Verification

Local, on the drafts worktree (Node 24.16.0, pnpm 11.10.0, pnpm install --frozen-lockfile), on the exact head ffde629, as lazurio-fork-ci.yml runs them:

• node --test scripts/lazurio-release-contract.test.mjs — 27/27 pass (26 before; the new Folder guard).
• pnpm exec vp fmt --check — pass (4226 files).
• pnpm run lint — exit 0, no errors (on main before this PR: 2 errors, Lint fails on main: the managed Folder's engine tests exceed upstream's ManagedRuntime ceiling #63).
• pnpm exec vp run --filter t3 typecheck, pnpm exec vp run --filter @t3tools/web typecheck — pass.
• The test step with its derivation and gate (a local copy of the workflow's script): apps/server 43 files, 41 passed and 2 skipped (the Chromium tests), 876 tests passed and 12 skipped; apps/web 10 files, 222 tests; packages/contracts 3 files, 166 tests; packages/shared 1 file, 10 tests; scripts 2 files, 23 tests.
• Every commit on its own (checked out in turn): formatting, the release contract, lint, the typecheck of each app it touches and the tests of the files it touches — all 14 pass. Commit 5 returns ThreadSettlementReactor.test.ts to upstream's text; that upstream test fails its 37 storage-cleanup cases on macOS exactly as at the upstream base (the file is byte-identical to v0.0.45) and passes on Linux in CI.
• The new guard tests fail when their code is undone: the reactor test with the turn guard disabled, the contract guard with the palette condition or the reactor guard removed, the panel test with the old withoutSurface, the hold test with unlimited retries, the session test with the old cache.

GitHub (Lazurio Fork CI, workflow_dispatch on this branch before the PR, then the PR's run):

• https://github.com/Lazurio/t3code/actions/runs/38377813107 — commits 1–4 (b7ad0e5): green.
• https://github.com/Lazurio/t3code/actions/runs/38379976297 — commits 1–8 (761f01e): green, the new Lint step included.
• https://github.com/Lazurio/t3code/actions/runs/38381886443 — commits 1–13 (f4eba74): green.
• https://github.com/Lazurio/t3code/actions/runs/38382518361 — the exact head ffde629: green (Server and web compatibility, CLI archives for linux-x64 and darwin-arm64, Launcher install linux-x64). Lint on 4040 files with 184 rules, no errors. Test step per package: apps/server 43 files, 41 passed and 2 skipped (the Chromium tests), 876 tests passed and 12 skipped; apps/web 10 files, 222 tests; packages/contracts 3 files, 166 tests; packages/shared 1 file, 10 tests; scripts 2 files, 23 tests. Release contract 27/27.
• https://github.com/Lazurio/t3code/actions/runs/38441656977 — this PR's own run on ffde629: green (all four jobs).

Canary checklist (root decision 0178)

On a canary Environment with the managed Folder (T3CODE_LAZURIO_FOLDER set by Machines) and this preview:

1. The welcome in Czech and English. A first run (or /welcome) with the browser in Czech shows "Váš pracovní prostor je připravený" and the Czech text; in English, the unchanged English. The link opens the Environment's tools page in a new tab. "Začít v Lazuriu" / "Start in Lazurio" opens a new chat in the Lazurio project, and the welcome does not come back while the chat loads.
2. The command palette. On the managed Environment alone: no "Add project" and no "New project"; the project search and "New thread in…" list only Lazurio. Where an unmanaged Environment is also known (or on a T3 Code without the variable): "Add project" is there, and with no connected Environment it opens Settings → Connections.
3. The sidebar's "Add project". Hidden on the managed Environment alone, shown once an unmanaged Environment is known.
4. A prepared prompt from the Launchpad. Apps → "+ Nový modul" on an Organization opens Chat with the prompt in a new thread of the Lazurio project, unsent, without the "Could not open the prepared prompt" toast.
5. A new chat in the Lazurio project. The hero reads "What should we build in Lazurio?" without a picker; the first turn runs with the Folder as its working directory; no git actions for the Folder.
6. The Environment browser (commit 10): when the panel's only tab ends in its view, the panel closes.
7. lazurio chat defaults --apply on the canary still reports the managed model.

Risks

• The managed Folder's code moved days after its first release while Machines and the Platform call t3 lazurio; the bytes are pinned and were compared, but the canary is where the Platform reads them.
• Fork CI now lints the whole repository: an upstream lint regression at the next rebuild fails CI until it is fixed or the rule is reviewed, as upstream's own vp check would.
• The prepared prompt in a managed Environment starts at the Folder root, not the Organization's root; the prompt text names the Organization and the agent works from there. That is F51's rule ("new sessions start at that root").
• The model route now accepts the Folder through a symlink or with a trailing slash (still 409 for any other folder).
• Merging closes Lint fails on main: the managed Folder's engine tests exceed upstream's ManagedRuntime ceiling #63.

🤖 Generated with Claude Code

[agentrozjedemeai]

@immakermatty Reviewed the exact ffde629 head against main 35a31c0. APPROVED for the phase-A cleanup. I traced the managed/unmanaged/loading Environment paths, the prepared prompt to the Folder project, first-run and route guards, settings reconciliation through the native writer, engine guard before decide, CLI output and session-lookup retry, bounded tab/hold behavior, and the formal Czech welcome. No blocking regression found. Local evidence on this detached checkout: 27/27 release contract, 61/61 focused overlay tests, 208/208 related engine/reactor/VCS/settings/tab tests, web and server typecheck, lint (exit 0 with existing warnings), and git diff --check. CI on this SHA has the four fork jobs successful; review threads: 0. I did not run a live canary UI preview; keep that post-merge preview as planned.