1
0

feat(brand): re-shoot everything at the new engine, and make it one command

**Seven new shots**, because the world grew the most photogenic things in it
after the last pass: `sfo`, `lax`, `golden-gate`, `bay-bridge`, `freeway`,
`california-relief` and `pacific-sea`. All nine existing ids are unchanged — the
manifest emits a `ShotId` union that lumbridge-v4 imports, so ids are added and
never renamed.

**A shot can now aim itself.** The chapter list has no camera for SFO, LAX, the
bridges, the freeway or the open sea, and the engine has no `?pose=` back door,
so a shot points itself by driving the app's own inputs: a click on the plan view
slides the orbit target to a lat/lng while keeping the chapter's stance, wheel
notches set the standoff, and a drag sets azimuth and elevation. The plan view's
pixel-to-coordinate map is solved at runtime from three hovers of
`#minimap-readout` rather than hard-coded, so it survives a board resize or a
restyle of the widget.

**The tera share card was a picture of the wrong thing, and had been.** Its art
came from `keyboard.press("2")`, which had landed on the California board's drive
mode once the default board changed — so the card under the headline "Cities from
above." was a chase camera on US-101, showing metre-scale cars driving between
kilometre-wide buildings, with the DRIVE readout and the mode pill baked into the
art. It renders, it looks deliberate, and it is why an unguarded key press has no
place in a capture script. `capture.mjs` now clicks an indexed chapter and
asserts its `shortLabel` the way `shots.mjs` does, waits on `#boot` and
`#chapters` instead of sleeping twenty seconds, and gives each card its own hour.

**`npm run refresh` is the durable half.** One command: build, stills, cards,
films, both manifests, and a hashed before/after diff of every deliverable. It
fails loudly and specifically on the two conditions that otherwise produce
confident wrong output — the renderer coming up as SwiftShader, and a chapter
`expect` guard firing. `--stills-only` / `--cards-only` / `--films-only` compose,
`--dry-run` lists the plan without opening a browser, and
`shots.mjs --list` prints the whole shot plan — board, chapter, expect, aim, both
hours — which is what to run first when a guard does fire.

It also re-stamps `PROVENANCE.json`, narrowly: only entries whose origin is
`repository-generated` and whose `generator` names a script the run actually
executed, by literal hash substitution rather than re-serialising the file.
Without that, every legitimate card re-shoot leaves `npm run provenance` red.

**Every film re-shot.** They were at `9c9e78f`, captured 2026-08-07, and predated
the tone mapping, the reflective sea, the sky dome, terrain shadows, the rebuilt
California board, SFO, LAX, both bridges and the moving aircraft.

Tests 1137, typecheck, build, eight budget cells and every provenance and licence
check pass.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-08-22 12:49:06 -07:00
parent f81d5218d4
commit 2aa4049258
12 changed files with 1419 additions and 115 deletions
+22 -1
View File
@@ -196,7 +196,13 @@
// rather than a screen-space gradient, so the world dissolves into the
// horizon instead of stopping at a visible edge. The framing is free to
// sit where the picture is best rather than where the defect was not.
position: "56% 62%",
//
// The state board is shot on a 2000x900 sensor, which is *wider* than
// the card, so `cover` crops horizontally and not at all vertically:
// the whole state is in frame top to bottom, and this number decides
// which two hundred pixels of ocean go. 0% keeps the western sea.
position: "0% 50%",
shift: 150,
},
office: {
eyebrow: "Lumbridge Spaces",
@@ -205,6 +211,7 @@
host: "office.",
art: "art-office.png",
position: "62% 46%",
shift: 0,
},
};
@@ -219,6 +226,20 @@
const art = document.getElementById("art");
art.style.backgroundImage = 'url("' + card.art + '")';
art.style.backgroundPosition = card.position;
/*
Slide the whole art layer right, and let the card clip it.
`cover` can crop a subject toward an edge; it cannot move a subject that
is already centred, because the offset it computes is bounded by the
overflow. The state board is centred in the app frame — the camera is —
and the left 58% of this card is scrim, so without this the headline sits
on top of California rather than beside it. Moving the layer instead of
the crop leaves the exposed strip at the far left showing the card's own
background, which is what the scrim was already painting there anyway.
*/
const shift = card.shift ?? 0;
art.style.left = shift + "px";
art.style.right = -shift + "px";
document.title = which;
</script>
</body>