docs: record the decided Lazurio shell loader in the fork runbook

[immakermatty]

Why

On 2026-10-03, Matěj made the Lazurio shell decisions for this fork. Chat (T3 Code) keeps upstream's look and branding until upstream's stable releases, and the overlay adds only what Lazurio needs around it: the rail of Environments, the app switch in T3's sidebar and the Buddy bubble. The release runbook said only that the fork ships the vanilla upstream client. It did not record this planned UI change, which future overlay rebuilds have to account for.

What changes

docs/operations/lazurio-fork-release.md:

• The introduction says the web client's look and branding stay upstream, and that loading the Lazurio shell is the only decided UI change.
• A new Lazurio shell subsection under Overlay, marked decided 2026-10-03, implementation pending. It covers:
  • Web Components with Shadow DOM from /.lazurio/shell.js (<lazurio-rail>, <lazurio-column-head>, <lazurio-buddy>), with data from /.lazurio/shell.json. The Environment's Launchpad serves both on the same origin.
  • About 20 lines in about three apps/web files, added to allowed_upstream_changes as one reviewed entry, plus a slot check so rebases conflict only there.
  • Plain links between origins, so T3's router does not change.
  • Nothing renders outside Lazurio. The official desktop and mobile apps stay upstream.

What deliberately does not change

• No code, workflow or allowlist change. The overlay table and allowed_upstream_changes stay as they are until the loader is implemented.
• No recolouring or renaming of T3 Code.

Verification

• node --test scripts/lazurio-release-contract.test.mjs: 11/11 pass. It reads this runbook and still finds "v kořeni vlastního hostname".
• vp fmt --check was not run locally because the workspace dependencies are not installed. prettier@3 --check on the changed file passed. CI runs the formatter.

Evening answers applied (2026-10-03)

Checked against Matěj's evening answers: this PR mentions Buddy only as the floating bubble ("plovoucí bublina Buddyho") of the shell, never as an agent, an operator or an app, so A1 ("Buddy is Buddy") needs no change. The Apps home sections (A6) are not described here. Head 0b82a8c unchanged; pr-preflight ready_to_push.

Status: ready for review

🤖 Generated with Claude Code

Confidence Score: 4/5

The documentation-only PR appears safe to merge, though its implementation instructions should be corrected before the shell is built.

Findings

1.  Rail margin clips content ▶
2.  Allowlist needs separate paths ▶

Summary

The PR records the planned Lazurio shell loader and its intended boundaries in the fork release runbook.

• It keeps upstream branding and describes a pending web-only overlay.
• The proposed layout and allowlist instructions need correction before they are used for implementation.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Browser["T3 web client"] --> Gateway["Environment gateway"]
  Gateway --> T3["T3 app"]
  Gateway -->|"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/.lazurio/shell.js and shell.json"| Launchpad["Environment Launchpad"]
  Launchpad --> Shell["Rail, column head, Buddy"]

Loading

_{Reviews (1) · Last reviewed commit: "docs: record the decided Lazurio shell l..."}

[agentrozjedemeai]

Reviewed exact head 0b82a8c. Two unresolved, reproducible release-runbook defects block approval: (1) the proposed #root { margin-left: var(--lazurio-rail-width, 0); } keeps the existing width:100% while body overflow is hidden (apps/web/src/index.css:1596–1608), so a nonzero rail clips the right side; specify a width/box-sizing-safe layout instead. (2) allowed_upstream_changes is a list of exact individual paths checked by the release contract (scripts/lazurio-release-contract.test.mjs:207–210), not a single entry for three files; specify one entry per changed file. The focused release contract passes 11/11 today but does not validate this future loader. Please correct both instructions, then request exact-head rereview. No merge.

[agentrozjedemeai]

@immakermatty — APPROVED on exact head cf16fa0. Fixed rail and #root border-box padding-left resolve overflow clipping; allowed_upstream_changes now requires one exact path per file under a shared reason. Release contract tests 11/11 pass in isolated checkout, latest diff --check clean, all live checks green and both addressed Greptile threads resolved with readback. No runtime shell is implemented by this docs PR.