@bongos/core 1.17.1 → 1.17.2

package/tests/workflow_exec_paths.mjs

@@ -0,0 +1,98 @@
+// tests/workflow_exec_paths.mjs — task 2136 (ADR 0108 configurable-root).
+//
+// Proves every .github/workflows/*.yml invocation of a CORE script resolves in a consumer layout
+// after the R89 split: each is routed through the both-layouts resolver (infra/core-node.sh for
+// node targets, infra/core-path.sh for bash targets) AND names a PUBLISHABLE core file that ships
+// in @bongos/core (→ present at node_modules/@bongos/core post-install) and exists at the core root
+// today. No workflow still invokes a core script the bare repo-relative way. Also proves
+// core-path.sh resolves both layouts (the bash-target sibling of core-node.sh).
+//
+// DB-free, no network. Run: node tests/workflow_exec_paths.mjs
+
+import { strict as assert } from 'node:assert';
+import { execFileSync } from 'node:child_process';
+import { createRequire } from 'node:module';
+import fs from 'node:fs';
+import os from 'node:os';
+import path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const require = createRequire(import.meta.url);
+const { lintWorkflowExec } = require('../scripts/gds/lint-workflow-exec.js');
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const REPO = path.resolve(__dirname, '..');
+const CORE_PATH_SH = path.join(REPO, 'infra', 'core-path.sh');
+
+let passed = 0, failed = 0;
+function test(name, fn) {
+  try { fn(); console.log(`  ok  ${name}`); passed++; }
+  catch (err) { console.error(`  FAIL ${name}`); console.error('    ', err.message); failed++; }
+}
+
+// ---- A. the workflow lint is green on the real tree ---------------------------------------------
+test('lint-workflow-exec: every core invocation is routed + publishable (no bare repo-relative form)', () => {
+  const r = lintWorkflowExec({ instanceRoot: REPO, coreRoot: REPO });
+  assert.deepEqual(r.violations, [], `expected no violations, got: ${JSON.stringify(r.violations, null, 2)}`);
+  assert.ok(r.ok, 'lint should pass');
+  // The security-critical merge gates + the functional gates must all be covered.
+  const rels = r.checked.map((c) => `${c.file}:${c.rel}`);
+  assert.ok(rels.some((s) => s.startsWith('gate-review.yml:') && s.endsWith('scripts/gds/gate-review.js')), 'gate-review routed');
+  assert.ok(rels.some((s) => s.startsWith('grade-gate.yml:') && s.endsWith('scripts/gds/ci-grade.js')), 'grade-gate routed');
+  assert.ok(rels.some((s) => s.endsWith('scripts/migrate.sh')), 'selfhost migrate routed via core-path.sh');
+});
+
+test('lint-workflow-exec: a bare core invocation in a workflow is flagged (counterfactual)', () => {
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'wf-lint-'));
+  try {
+    fs.mkdirSync(path.join(tmp, '.github', 'workflows'), { recursive: true });
+    fs.mkdirSync(path.join(tmp, 'scripts', 'gds'), { recursive: true });
+    fs.writeFileSync(path.join(tmp, 'scripts', 'gds', 'gate-review.js'), '// probe\n');
+    fs.writeFileSync(path.join(tmp, '.github', 'workflows', 'legacy.yml'),
+      'jobs:\n  x:\n    steps:\n      - run: node scripts/gds/gate-review.js\n');
+    const r = lintWorkflowExec({ instanceRoot: tmp, coreRoot: tmp });
+    assert.ok(!r.ok, 'a bare core invocation must fail the lint');
+    assert.equal(r.violations.length, 1);
+    assert.match(r.violations[0].why, /bare core invocation/);
+  } finally { fs.rmSync(tmp, { recursive: true, force: true }); }
+});
+
+// ---- B. core-path.sh resolves BOTH layouts ------------------------------------------------------
+function runCorePath(rel, instanceRoot) {
+  return execFileSync('bash', [CORE_PATH_SH, rel], {
+    encoding: 'utf8', env: { ...process.env, BONGOS_INSTANCE_ROOT: instanceRoot },
+  }).trim();
+}
+
+test('core-path.sh prints the monolith path (script at the instance root)', () => {
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'cp-mono-'));
+  try {
+    fs.mkdirSync(path.join(tmp, 'scripts'), { recursive: true });
+    fs.writeFileSync(path.join(tmp, 'scripts', 'migrate.sh'), '# probe\n');
+    assert.equal(runCorePath('scripts/migrate.sh', tmp), path.join(tmp, 'scripts', 'migrate.sh'));
+  } finally { fs.rmSync(tmp, { recursive: true, force: true }); }
+});
+
+test('core-path.sh falls back to the consumer path (script only under node_modules/@bongos/core)', () => {
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'cp-cons-'));
+  try {
+    const pkg = path.join(tmp, 'node_modules', '@bongos', 'core', 'scripts');
+    fs.mkdirSync(pkg, { recursive: true });
+    fs.writeFileSync(path.join(pkg, 'migrate.sh'), '# probe\n');
+    assert.equal(runCorePath('scripts/migrate.sh', tmp), path.join(pkg, 'migrate.sh'));
+  } finally { fs.rmSync(tmp, { recursive: true, force: true }); }
+});
+
+test('core-path.sh exits non-zero (no stdout) when the script is in NO layout', () => {
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'cp-none-'));
+  let threw = false;
+  try {
+    execFileSync('bash', [CORE_PATH_SH, 'scripts/nope.sh'], {
+      encoding: 'utf8', stdio: 'pipe', env: { ...process.env, BONGOS_INSTANCE_ROOT: tmp },
+    });
+  } catch (_) { threw = true; }
+  finally { fs.rmSync(tmp, { recursive: true, force: true }); }
+  assert.ok(threw, 'expected a non-zero exit when the script resolves in no layout');
+});
+
+console.log(`\nworkflow_exec_paths: ${passed} passed, ${failed} failed`);
+process.exit(failed ? 1 : 0);

package/docs/design/container-exterior-tiles.md

@@ -1,49 +0,0 @@
-# Container building — exterior tile spec (pixel-precise, V2)
-
-- **Task:** [#643](https://example.com/builders#/task/643) (V2 · product). Promoted from idea_inbox [#162](https://example.com/builders#/idea/162) (builder 25 art/design brief, 2026-06-04).
-- **Date:** 2026-06-18
-- **Builds on:** [`container-exterior.md`](container-exterior.md) (the structure-level design, task [#641](https://example.com/builders#/task/641)) — this is the **tile-level** layer it calls out. Colour is governed by the locked decisions below.
-- **Status:** Spec ready. **Generation waits for [#640](https://example.com/builders#/task/640) / [ADR 0044](../adr/0044-mediterranean-palette-replacement.md)** (every tile here re-quantizes against the replacement palette — per `container-exterior.md` §Pipeline). Spec work proceeds now.
-
-## ⚠️ Colour: the original brief is superseded — weathered charcoal, not clean red
-
-idea [#162](https://example.com/builders#/idea/162)'s brief (this task's source) asked for **"saturated industrial red (or black) — clean, no weathering, no rust."** That was written **before** Lars resolved the question. The authoritative decision (later wins):
-
-- **Blocker [#7](https://example.com/builders#/blocker/7) (Lars, 2026-06-10, now a locked `style_guide.md` rule):** the container body is **weathered BLACK/CHARCOAL corrugated metal with rust streaks** — *not* red, *not* teal. Faded **Hermes-teal is an ACCENT only** (the door panel + a faint caduceus etch). It must read as an *ancient, heavy, discovered relic*, not factory-new cargo.
-- **`style_guide.md` (Lars, 2026-06-14):** **no white / light edge rim** on container (or other large-object) tiles — strip near-white edge pixels in post ("the white on the container actually sucks").
-- **`style_guide.md`:** non-ground objects carry a **1-px darker outline** against their interior (FireRed rock/tree convention); ground tiles do not.
-
-So every tile below is **weathered charcoal corrugated metal with rust streaks**; the brief's "clean red, no weathering, single-pixel white highlight" wording does **not** apply. The brief's *geometry* (corrugation, glass panels, deck, roof, staircase) is still the source — only the colour/finish is corrected.
-
-## Per-tile pixel specs (32×32 base)
-
-### Container wall tile
-- **Base:** weathered charcoal/gunmetal (a matte near-black with a faint blue-grey undertone), drawn from the replacement palette's charcoal/grey value steps (ADR 0044 guarantees enough steps).
-- **Corrugation:** 4–5 vertical ridges per tile. Each ridge: 1px lighter charcoal on the left (highlight), 1px darker on the right (shadow); flat panels between are the base.
-- **Weathering:** sparse vertical **rust streaks** (a desaturated orange-brown from the palette) bleeding downward from ridge tops + seams — irregular, 1–2px wide, not on every ridge. Reads as age, not damage.
-- **Edges:** 1px darker-charcoal **outline** on the object silhouette (per the style rule). Top edge 2px darker (top face in oblique light); bottom edge 1px near-black ground shadow. **No white/light rim** anywhere on the silhouette.
-- **Stacked-unit seam:** a 2px dark recessed line with a 1px shadow below, where the ground-floor container meets the second storey.
-
-### Glass storefront / window panel (32×32, or 64×32 wide)
-- **Fill:** semi-transparent blue-grey (≈40–50% over what's behind). Through dark glass, a faint **warm amber interior glow** (the "dark exterior, warm interior" mood from `container-exterior.md`).
-- **Frame:** 3px matte-charcoal border (the frames dissolve into the dark facade rather than reading as separate elements).
-- **Interior hint:** extremely faint 1–2-shade-darker silhouettes (a plant, shelving) — not detailed.
-- **Reflection highlight — FLAG for Lars:** the brief wanted a white upper-left reflection strip; the no-white-rim rule targets the *object silhouette*, not interior glass. Proposed: a restrained **pale-blue** (not white) 1px upper-left reflection inside the frame. If Lars wants zero light pixels here, drop it. *(Open pixel-detail decision.)*
-
-### Door tile (the one Hermes-teal accent)
-- Charcoal frame; the door panel is **faded Hermes-teal** (the single body-color exception), with a **faint caduceus etch** (1–2px lighter teal lines) where space allows, and a warm interior glow at the threshold. This is the only teal on the building.
-
-### Deck tile (wood apron, walkable)
-- Horizontal planks: light warm tan base, 4–5 planks/tile, 1px dark gap between; very subtle 1–2px grain lines; 2px darker far-edge shadow. Drawn as an alpha-margined object overlay over sand (the `marble_path` technique, [ADR 0013](../adr/<redacted>.md)) so it works on any ground.
-
-### Roof tile (top-down)
-- Flat charcoal surface, 1 shade darker than the wall face (less direct light); small 3×3 dark **container corner castings** at each corner; a faint 2px panel seam every 8px; 1px railing line on edge tiles (per `container-exterior.md` rooftop band).
-
-### Exterior staircase (object overlay)
-- Dark charcoal steel: two parallel rails with treads between (top-down ladder look); 1px railing line each outer edge, 1px lighter than the tread. Arrives at the rooftop stair-landing tile.
-
-## Mood target
-A **designed object, not a found one** — presence from its *shape and glass*, not from bright paint. The charcoal recedes into the coastal scene; at dusk the warm interior light through dark glass is the most dramatic visual in the game. The contradiction (an *ancient* shipping container) lives in the weathering + the teal-and-caduceus door.
-
-## Pipeline mapping (generate after [#640](https://example.com/builders#/task/640))
-Per [ADR 0008](../adr/<redacted>.md) (families, not per-tile): `container_building_facade` (wall · glass · door · light-fixture · staircase), `container_building_roof` (field · railing · landing), `deck_wood` (16-autotile alpha-tile line family). Furniture singletons (table, chairs) per-tile. **Nothing generates until the palette swap ([#640](https://example.com/builders#/task/640)/ADR 0044) lands** — else every tile re-quantizes against the old palette and is redone.

package/docs/design/container-exterior.md

@@ -1,81 +0,0 @@
-# Container building — exterior structure design (V2)
-
-- **Task:** [#641](https://example.com/builders#/task/641) (V2 · product · creative). Promoted from idea_inbox [#160](https://example.com/builders#/idea/160) (builder 25 art/design brief, 2026-06-04).
-- **Date:** 2026-06-11
-- **Status:** Design locked at the structure level. Pixel-precise tile specs are [#643](https://example.com/builders#/task/643) (facade); interior is [#642](https://example.com/builders#/task/642)/[#644](https://example.com/builders#/task/644)/[#645](https://example.com/builders#/task/645); palette implementation is [#640](https://example.com/builders#/task/640) / [ADR 0044](../adr/0044-mediterranean-palette-replacement.md).
-
-## What changes
-
-The container is no longer a single beached 4×2 object (the current `CONTAINER_LAYOUT` in
-`src/world/terrain.js`). It becomes a **two-storey trading house built from stacked
-shipping containers** — a designed building with a glass storefront, a wooden deck,
-an exterior staircase, and a flat rooftop. It reads as a *destination*, not salvage.
-
-The narrative survives intact: Hermes placed the containers; the Examplens stacked
-them into a trading house. The mythic contradiction (an *ancient* shipping container)
-stays — see the colour note below.
-
-## Colour: weathered black/charcoal (decided)
-
-The original brief asked for "bold, uniform red or black — not rusted or weathered."
-That option was resolved **after** the brief was written: blocker [#7](https://example.com/builders#/blocker/7) (Lars, 2026-06-10,
-recorded as a style-guide rule) fixed the container as **weathered black/charcoal
-corrugated metal with rust streaks**, with faded Hermes-teal as an *accent only* (the
-door + the caduceus etch). The later decision wins. So the building is charcoal and
-weathered — it is "designed architecture" by its *shape and glass*, not by looking
-factory-new. ADR 0044 already constrains the replacement palette to carry enough
-charcoal/grey value steps for this.
-
-## Top-down structure (32×32 tiles, FireRed building anatomy)
-
-FireRed conveys buildings top-down as **facade rows (what you'd see standing in front)
-topped by roof rows**. A second storey = a taller facade. The reference is the Celadon
-department store: tall glass-fronted facade, flat roof.
-
-The building is an **8-wide × 6-tall** visual block (up from 4×2):
-
-| Rows (top→bottom) | Band | Content |
-|---|---|---|
-| 1–2 | **Rooftop** | Flat container roof; 1-px railing along the edge tiles; a stair landing tile at the right edge where the exterior staircase arrives. Future rooftop deck props (parasol, crates) are object overlays, not part of this family. |
-| 3–4 | **Upper-storey facade** | Charcoal corrugated container walls with a continuous band of **large glass panels** (semi-transparent blue-grey, single white highlight stripe). Container seams visible at the stacked-unit joints. |
-| 5–6 | **Ground-storey facade** | Glass storefront panels flanking a centred **door** (the one Hermes-teal accent, faint caduceus etch, warm interior glow). Wall-mounted light fixtures as small details on the wall tiles either side — lit at dusk/night. |
-
-Attached, outside the 8×6 block:
-
-- **Exterior staircase** — a 1-tile-wide steel stair strip climbing the building's right
-  side from ground to the rooftop landing. Purely visual in V2 (blocking); the rooftop
-  becomes walkable in a later version, the art shouldn't need to change for that.
-- **Wooden deck** — a 2-row walkable apron in front of the ground facade, drawn as an
-  alpha-margined object overlay over sand (the marble-path technique, [ADR 0013](../adr/<redacted>.md)),
-  so it works on any ground. Outdoor furniture (table, two chairs) are blocking
-  object singletons placed on the deck, off the door's walking line.
-
-### Placement and collision
-
-Anchor at **(11, 4)** in the current 30×18 world: the building spans cols 11–18,
-rows 4–9 (grass behind, sand in front), the deck spans rows 10–11, and the existing
-marble path (col 13, rows 10–13) shifts to meet the door at col 14–15. All building
-tiles **block**, including the door — interaction stays "stand adjacent and face it,"
-exactly like the current container door. Deck tiles are walkable; furniture blocks.
-
-## Pipeline mapping (what gets generated, later)
-
-Per [ADR 0008](../adr/<redacted>.md), coherent groups are families, not per-tile calls:
-
-1. **`container_building_facade`** family — wall, glass-panel, door, light-fixture, and
-   staircase tiles (replaces the 2×4 `container` family in `art/template/families.json`).
-2. **`container_building_roof`** family — roof field, railing edges/corners, stair landing.
-3. **`deck_wood`** — 16-autotile alpha-tile line family (same recipe as `marble_path`).
-4. **Furniture singletons** (table, chair) — per-tile pipeline.
-
-**Sequencing rule: generate nothing until [#640](https://example.com/builders#/task/640) / ADR 0044 lands.** Every one of these
-tiles would be quantized against the old palette and re-done after the Mediterranean
-swap. Spec work ([#643](https://example.com/builders#/task/643)) can proceed now; generation waits.
-
-## Engineering follow-up (not this task)
-
-The world model needs a matching change in **both** `map.js`/`terrain.js` twins
-(server + client): new OBJECT ids, an 8×6 building layout replacing
-`CONTAINER_PANELS_ROWMAJOR`/`CONTAINER_LAYOUT`, deck overlay placement, and blocking
-rules as above. That is an engineering task to be filed when the facade family's tile
-ids are final (after [#643](https://example.com/builders#/task/643)).

package/docs/design/container-interior.md

@@ -1,77 +0,0 @@
-# Container building — interior atmosphere design (V2)
-
-- **Task:** [#645](https://example.com/builders#/task/645) (V2 · product · creative). Promoted from idea_inbox [#164](https://example.com/builders#/idea/164) (builder 25 art/design brief, 2026-06-04).
-- **Date:** 2026-06-21
-- **Builds on:** [`container-exterior.md`](container-exterior.md) — this is the **interior** counterpart of that structure-level brief. The granular interior layers it calls out are the **layout** ([#642](https://example.com/builders#/task/642)) and the **floor-tile pixel spec** ([#644](https://example.com/builders#/task/644)); palette is governed by [ADR 0044](../adr/0044-mediterranean-palette-replacement.md).
-- **Status:** Atmosphere direction locked. Colour reconciled to ADR 0044 (below). Tile generation waits for [#640](https://example.com/builders#/task/640) / ADR 0044, same sequencing rule as the exterior.
-
-## ⚠️ Colour: the source brief is superseded — Mediterranean palette, not Poke-Mart blue
-
-idea_inbox [#164](https://example.com/builders#/idea/164)'s brief (this task's source, 2026-06-04) built the interior on a **saturated Pokémon "Poke Mart" blue wave-scale floor** and **orange-red container walls** as the nostalgia anchor. That was written **before** the palette was locked. The authoritative decisions win (exactly as the exterior briefs defer):
-
-- **[ADR 0044](../adr/0044-mediterranean-palette-replacement.md)** (2026-06-10): the world has **one Mediterranean palette**, and it states explicitly — *"there is no 'Poke Mart interior' context that needs the temperate palette."* So the interior is **not** a palette exception; it shares the world's hues.
-- **Blocker [#7](https://example.com/builders#/blocker/7)** (2026-06-10, locked `style_guide.md` rule): the container body is **weathered black/charcoal corrugated metal**, not red/orange. The interior-facing walls are the same shell.
-- **Lars (2026-06-21, this session):** Mediterranean governs the interior. The layered *geometry* survives untouched — only the hues are corrected.
-
-Concretely (geometry preserved, hue corrected — the exact move [`container-exterior-tiles.md`](container-exterior-tiles.md) made for the facade):
-
-| Source brief's colour | Corrected (Mediterranean) |
-|---|---|
-| Saturated Poke-Mart **blue** wave floor | **Aqua / turquoise** wave-scale, from the palette's turquoise-sea steps — the *pattern* is the nostalgia anchor; the *hue* matches the sea just outside the glass |
-| **Orange-red** container walls | **Weathered charcoal** corrugated (blocker [#7](https://example.com/builders#/blocker/7)) — warmth comes from the *lighting*, not the paint |
-| Lush **forest-green** featured rug | Deep **olive / sage** rug (the palette's darkest greens) — still "rich and set apart," in-palette |
-| Pure-**white** shelving | **Cream / pale-stone** (warm-neutral steps); no white edge rim, 1-px darker object outline (style rules) |
-
-> **[#642](https://example.com/builders#/task/642) / [#644](https://example.com/builders#/task/644) note:** both still say "blue" floor; [#644](https://example.com/builders#/task/644)'s title already hedges to "aqua-tinted." Read their "blue" as this brief's Mediterranean turquoise/aqua — this doc is the colour authority for the interior, the way `container-exterior.md` is for the facade.
-
-## The unified interior — a layered space
-
-Three layers on three surfaces, none fighting because each owns a different plane:
-
-1. **Shell (walls):** raw weathered-charcoal corrugated container — the industrial bones are never hidden. Double-height: tall wall columns, a second-floor balcony railing along the top of the map, pendant lamps on cables from a high ceiling.
-2. **Floor (the centerpiece):** aqua/turquoise wave-scale tile — the nostalgia geometry underfoot, in Mediterranean hue.
-3. **Retail layer (objects + light):** boutique principles — items displayed like sculpture with as much negative space as product; warm directional track lighting makes the illuminated patches the brightest things in the room.
-
-You walk into a space that *feels* like a game (the floor pattern), *looks* like a container (the charcoal shell), and *shops* like a boutique (the sculptural, warm-lit display). That triple recognition in the first two seconds is the emotional design goal — unchanged by the palette correction, because it lives in **pattern, material, and light**, not in saturation.
-
-## Architecture extracted from the references (geometry — all survives)
-
-The source brief studied four interior reference images (idea_inbox [#164](https://example.com/builders#/idea/164)); the *geometry* below is the durable takeaway, independent of hue.
-
-- **Double-height shell** (Interior1/2): two storeys of open vertical space → taller wall columns, a balcony-railing band at the top of the map, pendant lamps on cables from a high ceiling.
-- **Symmetrical industrial staircases** (Interior1): black-metal flights on the left/right walls — key navigation + vertical drama. Visual/blocking in V2; walkable upper floor is a later version.
-- **Warm pooled light** (Interior2): tall warm lamps and track lights pool on the floor — 2–3 shade steps radiating from each source. This is where *all* the warmth now comes from, since the walls are charcoal.
-- **Sculptural display** (interior3): freestanding display tables (gallery plinths, not Poke-Mart shelves), few items, generous spacing. Negative space ≈ product — the single biggest luxury signal.
-- **Featured "room within a room"** (interiorShelving1): an architecturally framed VIP zone with a deep olive/sage rug and warm ochre/gold fixtures — the inner sanctum / featured-product zone.
-- **Rear glass panel** (Interior1): full-width north-wall glass showing the coast beyond — ties the interior back to the Mediterranean exterior (and reuses the facade's glass language).
-
-## Key tile assets (priority order)
-
-1. **Aqua wave-scale floor tile** — the foundational tile; pixel spec is [#644](https://example.com/builders#/task/644).
-2. **Interior container wall tile** — weathered charcoal corrugated (interior-facing variant of the exterior wall family).
-3. **Cream shelving unit** — wall-mounted, pale-stone, items displayed; no white rim, 1-px outline.
-4. **Track-light tile** — small dark ceiling/beam fixture + a warm cone splashing onto the surface below.
-5. **Display-table object overlay** — freestanding wood top, few items, spaced.
-6. **Deep olive/sage featured rug** — the premium-zone floor (alpha-tile overlay over the wave floor).
-7. **Industrial pendant lamp** — hung from above, warm light source.
-8. **Balcony railing** — dark metal, top of the map (second-storey read).
-9. **Polished-concrete floor** — grey, smooth, for back-of-house / secondary areas.
-10. **Rear glass panel** — full-width north wall, coast visible through it.
-
-## Pipeline mapping (generate after [#640](https://example.com/builders#/task/640) / ADR 0044)
-
-Per [ADR 0008](../adr/<redacted>.md) (families, not per-tile calls):
-
-1. **`interior_container_shell`** family — wall · balcony railing · staircase · pendant lamp.
-2. **`interior_floor`** family — aqua wave-scale + polished-concrete, with the olive/sage rug as an alpha-tile overlay (the `marble_path` technique, [ADR 0013](../adr/<redacted>.md)).
-3. **Display singletons** — table, shelving, track light, glass panel — per-tile.
-
-**Nothing generates until the palette swap ([#640](https://example.com/builders#/task/640) / ADR 0044) lands** — every tile would re-quantize against the old palette and be redone, the same sequencing rule the exterior brief states.
-
-## Mood target
-
-Walk in and feel like you discovered something — not a supermarket, not an unaffordable boutique, not a video-game shop, but all three at once. The charcoal shell says *industrial secret*; the aqua wave floor says *I know this place*; the spaced, warm-lit display says *this is worth something*. The floor now reads as a **sun-bleached aqua wave** rather than an arcade-saturated blue, which is the point: it belongs to the same coast you can see through the rear glass.
-
-## Engineering follow-up (not this task)
-
-A walkable interior needs a second world map / room and a door transition (the `container-exterior.md` entrance door leads here), plus interior OBJECT ids in **both** `map.js`/`terrain.js` twins (server + client). File as an engineering task once the interior layout ([#642](https://example.com/builders#/task/642)) and floor tile ([#644](https://example.com/builders#/task/644)) are final.

package/docs/design/world-map-scroll.md

@@ -1,41 +0,0 @@
-# World map — the "Sealed Ruins Chart" (diegetic artifact, V2)
-
-- **Task:** [#648](https://example.com/builders#/task/648) (V2 · product). Promoted from idea_inbox [#169](https://example.com/builders#/idea/169) (builder 25 art/design brief, 2026-06-04).
-- **Date:** 2026-06-18
-- **Status:** Art + design spec ready. Two follow-ups it implies are separate tasks: the **diegetic-item mechanic** (engineering) and **tile generation** (waits on the palette swap, [#640](https://example.com/builders#/task/640)/[ADR 0044](../adr/0044-mediterranean-palette-replacement.md)). See *Follow-ups* below.
-
-## Concept
-
-The world map is **not a UI overlay or menu** — it is a **diegetic in-game artifact**: an ancient sealed chart the player *discovers*. This reframes navigation from a game mechanic into a story beat. The in-world item name is the **"Sealed Ruins Chart"** — "sealed" is load-bearing: the map is a mystery; not everything is visible from the start.
-
-> Reference concept art (builder-25 planning input): `art/references/concept-art-original/world-map/Map Item Pop Up Concept.webp` + `Shipping container Concept.png`. **NB:** these planning images are not committed to the repo (the `art/references/concept-art-original/` tree is empty here); this written spec is the durable, self-contained source.
-
-## Behaviour (the "diegetic" part — engineering follow-up, not this art task)
-
-- The player does **not** open a menu. They find / are given the scroll — an inventory item, like the FireRed Town Map received from a character.
-- Examining it plays an **unroll animation**.
-- It is **progressive / fog-of-war**: sealed areas begin as blank parchment and fill in as the player explores. (This is the "sealed" mystery made mechanical.)
-
-## Scroll art spec (pixel art)
-
-- **Rollers (top + bottom):** dark mahogany brown, visible wood grain (2–3 horizontal pixel lines per plank); cylindrical implied by a lighter highlight strip along the top edge.
-- **Corner accents:** round emerald-green gemstone insets, 8×8px each, single light highlight pixel upper-left.
-- **Parchment:** aged warm tan, **not uniform** — subtle darker age/wear patches; slight edge vignette.
-- **Title banner:** a rectangular banner at the top, slightly darker parchment, **"SEALED RUINS CHART"** in a serif pixel font (dark brown, not black).
-- **Footer:** bottom roller repeats the title left + right with a centred **emblem** between — a 32×32 pixel creature (dragon / sea-monster), dark-outline style.
-
-### Map surface — the swirling currents (what makes it feel ancient)
-The parchment is densely covered in hand-drawn-style arrows + curved flowing lines — **ocean-current / wind notations**, the language of old nautical charts (NOT paths):
-- thin 1px dark-brown curved, directional lines; arrow tips = simple 2–3px chevrons;
-- density ≈ one arrow/curve segment per 16×16 area over **sea**; **land** areas sparser;
-- this texture — organic, dense, directional — is what reads as *ancient + discovered*, not *designed*.
-
-## Colour note (palette)
-The hexes in the source brief (mahogany, emerald, #D4A96A parchment) are **targets, not literals**: when generated, every pixel quantizes to the locked 64-colour palette — and that palette is being **replaced** ([#640](https://example.com/builders#/task/640) / [ADR 0044](../adr/0044-mediterranean-palette-replacement.md)). The replacement must carry warm-tan / mahogany / emerald steps for this artifact; flag if it doesn't. This is a UI/item artifact (not a world ground tile), so it is less palette-constrained than terrain, but it should still read in-world.
-
-## Mood target
-The player should feel they found something they were **not supposed to find** — a real object from another time, not a game menu. First unroll = one of the most memorable moments in the game.
-
-## Follow-ups (separate tasks, not this art spec)
-1. **Diegetic-item mechanic** (engineering): inventory item + examine→unroll animation + progressive fog-of-war reveal keyed to discovered areas. File when the inventory/item system exists (relates to the V3 purchase-loop / bag work, e.g. [#635](https://example.com/builders#/task/635)).
-2. **Scroll tile/sprite generation** (art pipeline): produce the scroll frame + parchment + emblem assets — **after** the palette swap ([#640](https://example.com/builders#/task/640)) so it isn't re-quantized + redone.

package/docs/recipes/claude-gemini-bongos-doors.md

@@ -1,155 +0,0 @@
-# Recipe — stand up claudebongos.com + geminibongos.com (vanity doors → cloudbongos.com)
-
-> Brings **claudebongos.com** and **geminibongos.com** live as public "vanity
-> doors": each shows the exact Cloud Bongos landing **gate** (`brand/cloud-bongos/gate`),
-> rebranded to **"Claude Bongos" / `> claude`** (resp. **"Gemini Bongos" / `> gemini`**)
-> at runtime — the visitor still types `bongos`, and on enter the gate redirects
-> to **cloudbongos.com**, landing straight on the orbs. Same task also **promotes
-> the gate onto the cloudbongos.com apex** (it replaces the buddha placeholder,
-> which is what makes the redirect land "on the orbs"). Task
-> [#1746](https://example.com/builders#/task/1746).
-
-## Architecture (what we're building)
-
-One gate bundle, three domains, a runtime switch — **no forked copies**. `space.js`
-reads `location.hostname`; a door rebrands the entry + redirects on enter, and the
-default (cloudbongos.com) reveals the orbs in place. Any future change to the gate
-shows up on all three automatically.
-
-| Domain | Serves | On typing `bongos` + enter |
-|---|---|---|
-| **claudebongos.com** | the gate, rebranded "Claude Bongos" / `> claude` | `→ https://cloudbongos.com/?entered=1` (orbs) |
-| **geminibongos.com** | the gate, rebranded "Gemini Bongos" / `> gemini` | `→ https://cloudbongos.com/?entered=1` (orbs) |
-| **cloudbongos.com** | the gate, "Cloud Bongos" (**was** the buddha page) | reveals the orbs in place |
-
-Hosting is the **cheapest possible**, same as the staging gate:
-
-| Thing | Value |
-|---|---|
-| Served by | Caddy `file_server`, web root `/home/lars/example/brand/cloud-bongos` |
-| The two doors | **pure static** — no app process, no port, no password |
-| cloudbongos.com apex | static gate for `/` + gate assets; **still proxies** `/api`, `/healthz`, etc. to the platform app (`:3002`) so sign-in keeps working |
-| TLS | **one new Cloudflare Origin Cert per new domain** — the cloudbongos cert's SANs do NOT cover claudebongos.com / geminibongos.com |
-| Cost | **$0/mo** — same droplet, no new process/port |
-
-Why static (not a reverse-proxy block): the gate is plain HTML/CSS/JS + PNGs.
-There is nothing to run. The `?entered=1` query flag is how a door hands off — the
-gate honors it (only on non-door hosts) to skip its own entry and open the orbs.
-
-Everything in the repo (`space.js`, the `infra/Caddyfile` blocks, the gate art)
-auto-deploys to the droplet checkout on merge. What is **NOT** automatic — and is
-this recipe — is the per-domain **DNS + Origin Cert** and the **live Caddyfile
-merge + reload**. Until those are done, the two domains show a TLS error (expected).
-
-## Phase ① — DNS (Cloudflare, ~1 min per domain)
-
-Both domains are already on Cloudflare. For **each** zone (claudebongos.com,
-geminibongos.com):
-
-1. Cloudflare → pick the zone → **DNS** → **Add record**.
-2. Type **A**, Name **`@`**, IPv4 **`REDACTED_IP`**, Proxy status **Proxied**
-   (orange cloud ON), TTL Auto. Save.
-3. Cloudflare → **SSL/TLS** → **Overview** → set encryption mode to **Full (strict)**.
-
-(Optional: add a **`www`** A record → same IP, proxied, if you want `www.` to work.
-The Caddyfile blocks are apex-only today; add `www.claudebongos.com` to the site
-line if you add the record.)
-
-## Phase ② — Origin Certificate (own domain → own cert)
-
-Each new domain needs its **own** Origin Cert. For **each** zone:
-
-Cloudflare → **SSL/TLS → Origin Server → Create Certificate**:
-- Hostnames: `claudebongos.com` **and** `*.claudebongos.com` (resp. the gemini pair)
-- Let Cloudflare generate the key; **copy both** the certificate and the private key.
-
-Install on the droplet (operator). Caddy runs as user `caddy` and **must be able to
-READ the key** — match the existing `origin.key` ownership (`640 root:caddy`). A
-root-only `600` key makes Caddy's reload fail (learned during the cloudbongos
-bring-up). The `.crt` can be world-readable.
-
-```bash
-# claudebongos
-sudo install -m 644 -g caddy /dev/stdin /etc/caddy/claudebongos-origin.crt   # paste cert, Ctrl-D
-sudo install -m 640 -g caddy /dev/stdin /etc/caddy/claudebongos-origin.key   # paste key,  Ctrl-D
-# geminibongos
-sudo install -m 644 -g caddy /dev/stdin /etc/caddy/geminibongos-origin.crt   # paste cert, Ctrl-D
-sudo install -m 640 -g caddy /dev/stdin /etc/caddy/geminibongos-origin.key   # paste key,  Ctrl-D
-```
-
-## Phase ③ — apply the Caddy blocks + reload
-
-Three blocks ship in `infra/Caddyfile`: the two new **door** blocks
-(`claudebongos.com`, `geminibongos.com`) and the **modified `cloudbongos.com`
-apex** block (now serves the gate + proxies functional paths). The live
-`/etc/caddy/Caddyfile` has drifted slightly from the repo copy, so **do not blindly
-`cp` the whole file** — apply the two pieces by hand:
-
-```bash
-cd /home/lars/example
-git pull   # or wait for the auto-deploy; the brand/ bundle + infra/Caddyfile land here
-
-# 1. Append the two door blocks (idempotent: skip if already present).
-grep -q '^claudebongos.com {' /etc/caddy/Caddyfile || \
-  awk '/^# ── Claude Bongos \+ Gemini Bongos — vanity DOORS/{p=1} p' infra/Caddyfile \
-    | sed '/^# ── Cloud Bongos — STAGING/,$d' >> /etc/caddy/Caddyfile
-#   (or just open the file and paste the two blocks from infra/Caddyfile — the
-#    awk above copies from the DOORS comment to end-of-file.)
-
-# 2. Modify the LIVE cloudbongos.com apex block. Open the file, find the
-#    `cloudbongos.com {` block, and replace its body — the single
-#    `reverse_proxy 127.0.0.1:3002 { … }` — with the gate-serving body from
-#    infra/Caddyfile (root + @hidden + @gate handle + the catch-all reverse_proxy).
-#    Leave builders.cloudbongos.com and status.cloudbongos.com UNTOUCHED.
-sudo nano /etc/caddy/Caddyfile
-
-# 3. Validate (as root — it must read the 640 origin keys), then reload.
-sudo caddy validate --config /etc/caddy/Caddyfile --adapter caddyfile
-sudo systemctl reload caddy   # fails closed on a bad config
-```
-
-> A bad config makes `reload` error out and **keep serving the old config** — the
-> live sites never go down. If a cert path is wrong, that one site fails to come
-> up while the others keep serving.
-
-## Phase ④ — verify
-
-```bash
-# from anywhere — the two doors:
-curl -sSL https://claudebongos.com/  | grep -o 'space.css\|gate'      # gate HTML served ✓
-curl -sSL https://geminibongos.com/  | grep -o 'space.css\|gate'      # gate HTML served ✓
-curl -sS -o /dev/null -w '%{http_code}\n' https://claudebongos.com/   # 200 (via the /gate/ redirect) ✓
-
-# cloudbongos.com apex now serves the gate, and the app still answers:
-curl -sSL https://cloudbongos.com/   | grep -o 'space.css\|gate'      # gate served at apex ✓
-curl -sS  https://cloudbongos.com/healthz                            # "ok" — app still reachable ✓
-```
-
-Then open each in **Chrome or Edge** (the live-glass refraction needs Chromium
-`backdrop-filter` + SVG displacement; Safari falls back to a plain frost, still
-fine):
-
-- `https://claudebongos.com` → gate reads **"Claude Bongos" / `> claude`**. Type
-  `bongos`, press enter → you land on **cloudbongos.com showing the orbs**.
-- `https://geminibongos.com` → same, **"Gemini Bongos" / `> gemini`**.
-- `https://cloudbongos.com` → gate reads "Cloud Bongos"; type `bongos` → orbs in place.
-- **Sign-in still works:** `https://builders.cloudbongos.com` → sign in with GitHub
-  (the OAuth callback is on the apex, `/api/gds/auth/web/callback`, which the
-  catch-all still proxies to `:3002`). If sign-in breaks, the apex `@gate`/`handle`
-  split is wrong — recheck step ③.2.
-
-## Rollback
-
-- **Take a door down:** delete its block from `/etc/caddy/Caddyfile`,
-  `sudo systemctl reload caddy`, remove the Cloudflare `@` A record.
-- **Revert cloudbongos.com to the buddha page:** restore the apex block to the
-  single `reverse_proxy 127.0.0.1:3002 { … }` body, reload. The buddha landing
-  (`public-landing/index.html`) is untouched in the repo and served again
-  immediately.
-
-## Files this recipe uses
-
-- `infra/Caddyfile` — the two door blocks + the modified `cloudbongos.com` apex block.
-- `brand/cloud-bongos/gate/space.js` — the runtime hostname switch (branding +
-  redirect + `?entered` auto-open).
-- `brand/cloud-bongos/` — the gate bundle + the world art it refracts (shared by all three).