Skip to content

Launchpad: module stones on a transparent background - #325

Open
annavesela wants to merge 2 commits into
mainfrom
agent/DEV-6639-transparent-stones
Open

annavesela wants to merge 2 commits into
mainfrom
agent/DEV-6639-transparent-stones

Conversation

@annavesela

@annavesela annavesela commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Why

Every module stone on the Apps page had a light square behind it: the
design system's stones carried a baked-in off-white background (#faf9f8 with
noise) instead of transparency, so on a white tile (or any other surface) the
square showed. Anička asked for the stone alone, on a transparent surround,
so it reads well on any background.

What changes

  • The 13 vendored stones in src/shell/vendor/stones/ are the design
    system's new transparent stones, byte for byte
    (HumanAndMachine-ai/design-system-lazurio#76). The antialiased rim is
    unblended against the stone colour, so dark or coloured surfaces get no
    light halo. The stone and its symbol are unchanged.
  • src/shell/vendor/README.md: new SHA-256 for each stone and the stones'
    source pin.

What deliberately does not change

The tile CSS, the stone sizes (44 px tile, 20 px menu) and the selection of a
stone by its semantic key.

Order of publication

design-system-lazurio#76 is merged (rebase) as 190e735; the README pins
that commit. The files are the same bytes as the PR head.

Verification

  • bun run check (lint, typecheck, public check, proof build and smoke, 1919
    tests) green before the rebase; after the rebase onto the current main,
    tests/apps-view.test.ts (including "every vendored file has the hash its
    README records") green.
  • Browser: bun scripts/preview-launchpad.ts local cs — Workspace tiles show
    the stones with no square; on the served images the corner pixel has
    alpha 0 and the centre alpha 255 for all six stones on the page.

Work context

  • Agent / thread: Claude Code (desktop), session 79341da9-b60b-44ef-b83f-493a50f99be5
  • Machine: MacBook-Air-2.local
  • Worktree: HumanAndMachine-ai root, .worktrees/productionspace/LazurioPlatform/DEV-6639-transparent-stones, branch agent/DEV-6639-transparent-stones
  • Mission Control: DEV-6639 (HumanAndMachine-ai mission-control/db/data/mission-control/plans/2026/10/DEV-6639-lazurio-environment-shell.yaml), the clean tile with its icon

🤖 Generated with Claude Code

Note

Replace Launchpad module stone assets with transparent-background versions

Replaces all 14 stone image assets in src/shell/vendor/stones/ with new versions that have a transparent surrounding. Updates the provenance and SHA-256 values in README.md to track HumanAndMachine-ai/design-system-lazurio commit 3219a6a7aaf27f09de084b2565100e13bd5dfe82.

Macroscope summarized 5091a39.

The vendored stones carried the design system's baked-in off-white
square, which showed as a light box behind every module icon on a tile.
They are now the design system's transparent stones
(HumanAndMachine-ai/design-system-lazurio#76) byte for byte, with the
new hashes and pin in the vendor README.

Plan: DEV-6639

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#76 was rebase-merged as 190e735; the files are the same bytes.

Plan: DEV-6639

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@annavesela

Copy link
Copy Markdown
Contributor Author

@agentrozjedemeai Anna asks to publish this one too (head f16973e): the module stones on a transparent background, already published in the shell prototype (HumanAndMachine-ai/prototypes-lazurio#35).

@immakermatty

Copy link
Copy Markdown
Contributor

Merge freeze on main for the LazurioPlatform v0.1.13 release, from 2026-10-26 ~08:40Z until the final v0.1.13 is out (expected this evening, UTC).

The candidate v0.1.13-rc.1 is main at 2bd9b438, and it runs its canary today. Anything merged into main before the final would not be in the canary, so it would have to go into v0.1.14. Please don't merge into main until the release owner (the DEV-6656 thread) says the final is out. Review, rebase and approval can go on as usual.

@immakermatty

Copy link
Copy Markdown
Contributor

The merge freeze for v0.1.13 is lifted. main already carries #661, which reached it after the candidate, so the final v0.1.13 is built on a release branch that restores the candidate's tree. Later merges into main don't change that final, so main can take merges again; they go into v0.1.14.

This branch has not been deployed

No deployments
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.

2 participants