The five data visualisations, and a host that can actually mount an L0 card

[ymote]

Pairs with splash-lang/Splash#4. This side holds the kinds, the shaders, the kit
changes and — the piece that was missing — somewhere to put a card on screen.

Five kinds, not an anonymous Shader

§1.1 said Shader with a variant "was dismissed too quickly". It is settled the
other way, and the reason is typing: with an anonymous shader a temperature bar
and a moon phase ride the same nameless fields, and nothing catches a card that
passes a latitude where a phase belongs.

min/max and lat/lon already meant the right thing and are reused; lo,
hi, rise, set, now, phase, illum, span, symbol, range are new.

Three shaders are real; two say they have nothing

L0TempBar draws a day's range as a segment of the week's, cold-to-warm across
its own span. L0SunArc is a half-ellipse with the sun placed by time, clamped
so a pre-dawn hour sits at the horizon. L0MoonPhase is a disc whose terminator
tracks the phase.

L0AqiContour and L0StockPlot draw an explicit hatched empty state. An
air-quality field and a price series are data, and this backend has no fetch.
Drawing a plausible curve would make a card look complete and be fiction — worse
than the marker it replaced, and the same instinct as §4's no-facts rule one
layer down.

I shipped five dangling names. widget_name mapped the kinds to L0TempBar
and friends in the commit that added them, and none of the widgets existed.
Nothing failed, because the mapping and the definitions are in different crates
and nothing here renders to pixels. The new test walks all three cards, collects
every widget name this backend emits, and asserts each one the kit owns is
defined — renaming a definition fails it by name.

The kit, corrected by putting it on a phone

Switching octos-one's device path to this kit found four things, in descending
order of damage:

• l0_surface filled the height. A card is as tall as its content and the
  host surface shows below; filling painted the whole screen and covered the
  app's own background. 94% of the lower half differed on a card whose content
  was correct. 43.8% drift → 5.0%.
• Containers had no height at all. The kit leaves height to the backend
  because a row is as tall as its contents; the stock list rendered as a panel
  containing four hairlines.
• Padding and margin had to become asymmetric — a page's top clears the
  status bar, its bottom the gesture bar.
• The type scale is now TAKEN from the widgets it replaces, not chosen, so a
  golden failure means "the layer moved" and not "the theme changed".

kit-host mounts an L0 card

The pieces were all here and the composition was unrenderable: the kit existed,
kit::lower emitted calls to it, splash_render evaluated them, to_makepad_ui
mapped them — and nothing ever put the result on a screen.

Three routes now. splash-ui-l0 is a real dependency rather than a dev one, so
the host realizes and lowers at runtime and the card stays a ledger. The data
is baked and static, which is a real difference from octos-one and is stated in
the code: where a source is answered live on a backend that fetches, this one
shows the seeded value.

Verification

45 workspace tests, 0 failures. splash-node, splash-render, splash-widgets
and kit-host are clippy-clean under -D warnings; the two remaining warnings
are in in-flight material.rs work that is not part of this branch.

🤖 Generated with Claude Code

[r9s-codereview]

🤖 AI Code Review

Claude CLI exited with code 1:

✅ No significant issues found.

---

Tokens used: 0 | Powered by r9s.ai

[r9s-codereview]

🔐 Secrets Detected

This PR contains 5 potential secret(s) that must be removed before merging.

[r9s-codereview]

🟠 Secret Detected (credit_card_visa)

Visa Credit Card Number detected: LLM validation unavailable - flagging conservatively

Match preview: 4520****0000

Remediation: Please review manually and remove if this is a real secret

[r9s-codereview]

🟠 Secret Detected (aws_secret_key)

Potential AWS Secret Key detected: LLM validation unavailable - flagging conservatively

Match preview: /com****heet

Remediation: Please review manually and remove if this is a real secret

[r9s-codereview]

🟠 Secret Detected (aws_secret_key)

Potential AWS Secret Key detected: LLM validation unavailable - flagging conservatively

Match preview: /com****ayer

Remediation: Please review manually and remove if this is a real secret

[r9s-codereview]

🟠 Secret Detected (aws_secret_key)

Potential AWS Secret Key detected: LLM validation unavailable - flagging conservatively

Match preview: /com****nces

Remediation: Please review manually and remove if this is a real secret

[r9s-codereview]

🟠 Secret Detected (aws_secret_key)

Potential AWS Secret Key detected: LLM validation unavailable - flagging conservatively

Match preview: /com****tton

Remediation: Please review manually and remove if this is a real secret

[ymote]

Superseded by a branch with the history split properly.

This one folded in-flight kit-host and Material work into commits about L0 — main.rs showed +730 lines where my change was 12, and splash-makepad/src/lib.rs +598 where mine was 39. Its Secrets Scan failure came from that swept-in content, not from the L0 work.

The replacement separates them: the catalog host, its screens and the Material renderer as one commit, then the visualisation kinds and shaders, then the L0 wiring.