Skip to content

docs: LAZURIO.md keeps upstream branding and records the shell loader - #17

Merged
immakermatty merged 1 commit into
mainfrom
agent/DEV-6639-direction-docs
Oct 3, 2026
Merged

immakermatty merged 1 commit into
mainfrom
agent/DEV-6639-direction-docs

Conversation

@immakermatty

@immakermatty immakermatty commented Oct 3, 2026 •

Copy link
Copy Markdown

Why

On 2026-10-03, Matěj made the Lazurio shell decisions for this fork. MausBot keeps upstream's look and branding until upstream's stable releases. In the Environment's app switch (Chat · Apps · Automate) it is Automate, and we call it MausBot. The fork adds only the loader for the Lazurio shell.

LAZURIO.md still said "the UI is at most lightly adjusted" and "Lazurio calls this product Lazurio MausBot". Neither matches that direction.

What changes

LAZURIO.md:

  • The Same product bullet now reads Same product and look as upstream. Upstream's look and branding stay, and the shell loader is the only decided UI change.
  • In a Lazurio Environment: in the switch it is Automate, and we call it MausBot. A note explains that earlier texts and the code say "Lazurio MausBot".
  • A new The Lazurio shell section, marked decided 2026-10-03, implementation pending. It covers:
    • /.lazurio/shell.js with <lazurio-rail>, <lazurio-column-head> and <lazurio-buddy>, and /.lazurio/shell.json. The Environment's Launchpad serves both on the same origin.
    • About 20 lines in about three files, listed in allowed_upstream_changes as one entry.
    • Plain links between origins, so MausBot's router does not change.
    • Nothing renders outside Lazurio, and nothing is recoloured or renamed.

What deliberately does not change

  • No code, workflow or allowlist change. The loader is not in the overlay yet.
  • Identifiers and messages that say "Lazurio MausBot" (for example the GitHub intake's user agent) and docs/operations/lazurio-fork-release.md stay as they are. The runbook's line that the overlay has "no UI change beyond the live browser fixes" is still true today. It needs an update in the PR that adds the loader.

Verification

  • node --test scripts/lazurio-release-contract.node-test.mjs: 6/6 pass. It reads LAZURIO.md and checks that it still links the release runbook.
  • The local pre-push hook (pnpm lint, typecheck, i18n:check) was skipped with OMB_SKIP_HOOKS=1, as the hook allows, because pnpm is not installed on this computer. None of those checks reads Markdown, and CI runs lint and typecheck.

Evening answers applied (2026-10-03)

Checked against Matěj's evening answers: this PR mentions Buddy only as the floating Buddy bubble 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 036137e unchanged; pr-preflight ready_to_push.

Status: ready for review

🤖 Generated with Claude Code

The Lazurio shell decisions of 2026-10-03: MausBot keeps upstream's look
and branding until upstream's stable releases; in the app switch it is
"Automate" and we call it MausBot. The overlay will add only a loader for
/.lazurio/shell.js (rail, app switch, Buddy bubble; data from
/.lazurio/shell.json), about 20 lines listed in allowed_upstream_changes,
and nothing renders outside Lazurio. Recorded as decided, implementation
pending.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@immakermatty
immakermatty merged commit f10c9c7 into main Oct 3, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant