fix: the density's ceiling comes from the fade, so the ramp is visible

The library's `full_scale` now defaults to the default fade's steady state and `gamma` to 1.0 (its
own commit); this side states the ceiling for the fade *it* configured, because that is what the
ceiling means: the ink the display settles at, so the newest acquisition is a fraction of full ink
and white is reached only where acquisitions agree.

- **acquisitions**: `1/(1 - factor)` -- the geometric sum, 2.0 at the panel's 0.5, and 1.0 at 0
  (only the newest sweep, at full ink).
- **time**: the library's default of two sweeps. A time fade has no fixed steady state -- it
  settles where the trigger's rate and the constant meet, which is the *point* of it -- so a fast
  trigger reads brighter than a slow one the way a phosphor's does.
- `gamma` is left at the library's 1.0: a cell is a count of sweeps, so half as many must read as
  half the ink. With the ceiling at one sweep and gamma at 0.45 (the library's first defaults) one
  sweep was already full white and every display looked the same -- which is exactly what the user
  reported seeing, and why the assertion for it is a framebuffer one in the library's case
  (`empty=21 full=83 quarter=54`) rather than anything `ink`/`peak` can say.

The probe's own figures are unchanged in kind (they are the grid's): `on` `peak=1.0000`,
`step-acquisitions` `peak=1.5000`, `step-time` `ratio=0.367879`, `off` all zeros -- re-read on this
build, with the frame cost `tick 0.53 -> 7.49 ms`, `draw 1.89 -> 16.78 ms` and `gtk warnings: 0` in
the same run. The trigger/pinning invariants carry the ceiling rule and why the eye found it.

docs/claude/invariants-trigger-and-pinning.md

@@ -403,6 +403,17 @@ Part of [CLAUDE.md](../../CLAUDE.md). These are rules that cost a defect to lear
   * **The switch deposits what is already on screen.** `on && !density_was_on` sets the same pending
     flag, so a user who turns persistence on while an event is held sees it instead of waiting for a
     latch that `single` mode may never send.
+  * **The brightness ceiling is the fade's steady state, and the ramp is linear in sweeps.** The app
+    states `DensityConfig::full_scale` from the fade it configured -- `1/(1 - factor)` for the
+    acquisition fade, the library's default two sweeps for the time one, which has no fixed steady
+    state (it settles where the rate and the constant meet) -- and leaves `gamma` at 1.0. A ceiling
+    at *one* sweep is the defect a user reported as "the colour fading is not applied, it looks
+    white": a single sweep was already full ink, everything above it clamped to the same pixel, and
+    a display of one sweep and a display of five were the same white. It is also the one half that
+    the *grid's* own numbers cannot see -- `ink`/`peak` were right while the picture was flat -- so
+    the assertion is a **framebuffer** one: `a_phosphor_density_is_drawn_under_the_traces` measures a
+    cell at a quarter of the scale against one at the ceiling and against the background
+    (`empty=21 full=83 quarter=54`), which is the reading the eye asked for.
   * **It is the plot's, so a figure rebuild resets it** -- the grid lives on each `Plot`, and
     `rebuild_all()` builds new ones. That is the one state a structural change (a row added, a signal
     switched off, a trace recoloured) does not carry: it costs the accumulated image and nothing else,