Lazurio shell slot: load /.lazurio/shell.js and place the rail, the app switch and Buddy (upstream look stays)

[immakermatty]

Goal

Chat and Automate are our forks of T3 Code and MausBot. Decided on 2026-10-03: until the upstream stable releases they keep the upstream look and branding (we keep saying it is T3 Code / MausBot), and the fork adds only the Lazurio shell: the rail on the left, the app switch at the top of the fork's own sidebar, and the floating Buddy chat bottom-right.

What to build (about 20 lines in about 3 files)

• index.html: <script type="module" src="/.lazurio/shell.js"></script> (served by the Environment's Launchpad, Lazurio shell: serve /.lazurio/shell.js and /.lazurio/shell.json on every Environment app origin LazurioPlatform#135).
• App root: <lazurio-rail> next to the app as position: fixed at the left edge, and #root { box-sizing: border-box; padding-left: var(--lazurio-rail-width, 0px) } (padding, not margin: upstream #root is width: 100% under an overflow-hidden body, so a margin would clip the right edge).
• Sidebar: <lazurio-column-head> (the switch Chat · Apps · Automate) at the top, in place of the upstream logo.
• Once anywhere in the root: <lazurio-buddy>.
• Outside Lazurio the script does not exist, the elements stay undefined and nothing renders: the fork behaves like upstream.
• Each changed file joins the fork's allowlist (allowed_upstream_changes) as its own exact path under one reason comment.
• A check that keeps this slot across every upstream rebase (the index.html script tag and the column head in the sidebar).

Done when

On an Environment, the fork shows the same rail, switch and Buddy as the Launchpad, and the slot survives one rebase onto a new upstream version.

Depends on Lazurio/LazurioPlatform#135.

🤖 Generated with Claude Code

[immakermatty]

Update: what the slot renders (second iteration of the shell, 2026-10-04)

Decided on 2026-10-04 (DEV-6639): Anička proposed it after reviewing the wireframe, and Matěj confirmed it. Wireframe: HumanAndMachine-ai/prototypes-lazurio#4 (merged); selection look: HumanAndMachine-ai/design-system-lazurio#54.

The fork patch does not change. It is still the script tag, <lazurio-rail> fixed beside the root with the padding-left rule, <lazurio-column-head> at the top of the sidebar in place of the upstream logo, and <lazurio-buddy>. Inside the sidebar, <lazurio-column-head> stays the only element the fork adds. What the elements render changes, and it ships with the Launchpad, without a fork release.

<lazurio-rail>: spaces, not Environments

• From the top:
  • the Lazurio logo (opens the Dashboard);
  • search (⌘⇧E, the global jump dialog);
  • the personal space (the Owner's initials);
  • one GitHub avatar per Organization;
  • "+" to add an Organization.
• At the bottom: only the account, as the person's GitHub photo.
• No Environment icons, no Organization folders, no "+N"/"méně", and no gear.
• The active space has an ink ring around its avatar, with no pill and no fill in the Organization's colour. The tooltip shows the name, the number of Environments and the last one used.
• A click on an Organization returns to the last Environment used in it, in the same app (Chat stays Chat). Without a remembered one it opens the first Environment; with none at all, the Organization Dashboard.

<lazurio-column-head>: picker, gear, app switch

• The Environment picker sits on top. It shows the Environment's name (by purpose, for example "Team ", "Pracovní", "Osobní", never "VM"), with "who it serves" below and the Organization avatar as its glyph. The state appears only when the Environment is not running.
• A square Settings gear sits right beside it. It opens the Settings of exactly what the picker names: Environment Settings, or Organization Settings on an Organization Dashboard. Account Settings stay in the account menu.
• The app switch Chat · Apps · Automate sits below, as before.

The picker's dropdown overlays the sidebar only while open

• It lists the Environments of the current space by name. The Organization is a head row above its Environments and opens the Organization Dashboard.
• "This computer" appears in every Organization it carries. "Všechny Organizace" widens the list. Search, ↑↓ and Enter work.
• It overlays the column only while open. Closed, the fork's sidebar keeps all its content and layout.
• Implementation note (proposal): render the dropdown in the top layer, for example a popover or fixed positioning from inside the shadow root. Then the fork's overflow on the sidebar cannot clip it and the fork needs no CSS for it.

Look

Selection is the quiet surface of design-system variant A: a surface one step darker and semibold type, with no left edge, no shadow and no capitals. It stays inside the Shadow DOM and does not touch the fork's styles. The fork keeps the upstream look and branding as decided on 2026-10-03.

Related

• Lazurio overlay: open Chat with a prompt draft from the shell (not sent) #35 (open Chat with a prompt draft by link, not sent) is the fork's only other shell requirement, beyond this slot. The "+ Nový modul" tile in Apps uses it, from the Environment's own origin only.
• The same update is on Lazurio shell slot: load /.lazurio/shell.js and place the rail, the app switch and Buddy (upstream look stays) OpenMausBot#16 (Automate).
• The data for these elements comes from /.lazurio/shell.json (Lazurio shell: serve /.lazurio/shell.js and /.lazurio/shell.json on every Environment app origin LazurioPlatform#135).

Done when (additions)

• The rail shows the personal space and Organization avatars, with no Environment icons and no gear.
• The column head shows the picker, the gear and the switch.
• Opening and closing the picker does not move or hide the fork's sidebar content.

🤖 Generated with Claude Code

[immakermatty]

Clarification on placement (decision 0185, PR HumanAndMachines/Lazurio#487; decision 0179 point 6):

• <lazurio-column-head> is the first element at the top of the fork's sidebar, above the upstream brand. It does not replace the brand or logo. The forks keep their upstream look and brand until upstream stable releases. Upstream header controls (new thread or bot, collapse, search, lists) stay below, unchanged.
• The Environment dropdown is wider than the sidebar (at least 400 px). Render it in the top layer (Popover API or a portal to body) so the sidebar cannot clip it. It is shown only while open; Esc or an outside click closes it.
• The Settings gear beside the picker links, in the same window, to the Environment's Settings in the Platform Launchpad on the Environment's launchpad. origin.