v0.5.0 — the deck chrome

Three fences for the four presentation decks, and the repair of the one marker in this system that
never closed.

The marker that never ended

deck footer · v1 opened a region and never closed it. That is why four copies of it have never
been comparable, and why the spec called closing it "the first fix, and it is worth doing whether
or not the rest of this spec is adopted." Closing it showed that it held two components wearing
one name.

deck transport — one form, and it never drifted

The spec put the transport at "162 / 150 / 154 / 160 lines, four forms, all different." Those
are the whole region counted by line, its prose comment and the lockup included. Compared as CSS
rules, all four decks are byte-identical. It needed no reconciliation — only an end marker and a
source.

One .name rule lives in this block rather than the lockup fence: .name{display:none}, inside the
860px query. It is not lockup identity, it is the bar saying it drops the lockup on narrow screens,
and it is identical everywhere.

deck lockup — two forms, which is why the split was worth making

blust.ch's two decks	one tier — the mark plus Robert Blust
companygraph + guestgraph	two tiers — the product lockup, then · ROBERT BLUST

There the product and the presenter are different names; here they are the same name, and a second
tier would read "Robert Blust · ROBERT BLUST". Eight rules are genuinely shared; each family's own
five and eight are spliced in by variant, verbatim from what those decks carry.

deck fit — the canvas scaler, and a comment describing a bug

Identical on all four decks but for one word: two said it scales "the 1600×900 canvas". That is
the fixed 16:9 shape that put 96px of black top and bottom on a 4:3 screen, and it was removed. Only
the height is pinned, at 900, and the width follows the screen — which is what the code does:
CH = 900, width derived as innerWidth / s.

One correction to what this project has been telling itself

Every one of these blocks used to carry, or sit beside, the claim that the copies exist because a
deck opens from file://, so there is nothing to import. That is false. A relative <link> and a
relative @font-face both work from file:// — measured, fonts genuinely loading. Copies are a
deliberate choice: one rule for everything, and every page self-contained. The blocks say that
now, so nobody overturns the architecture on discovering the stated reason was wrong.

112 tests.