Change the stale-data behavior

A Status Display goes feed-stale when Print Hive's evidence stops being trustworthy: source expiry, transport expiry, or untrusted timestamps. The profile's stale mode selects what every mapped pixel renders while the feed is stale. This is different from a single Printer's UNKNOWN status, which renders normally on a fresh feed.

The three modes

per_pixel (wire value 0) — each pixel renders its UNKNOWN binding. The display looks like a feed where every Printer is unverifiable.
all_pixels (wire value 1) — every mapped pixel renders the profile's stale program, for example a constant dim purple.
first_pixel (wire value 2) — logical pixel 1 renders the stale program and every other pixel turns off. This is the controller-wide diagnostic used by the default profile. Physical pixels with no logical assignment stay off.

In the pattern editor the STALE tab previews the three modes in parallel so you can compare them before you commit.

Change the mode

Open the profile in the Patterns tab and select the STALE target in the status rail.
Select the row for the mode you want.
Choose the stale pattern that modes all_pixels and first_pixel render. The binding must name a pattern in this profile in every mode, including per_pixel.
Select Save draft. The mode is part of the compiled header, so the byte meter and SHA-256 update immediately.
Select Publish and assign the new revision to the displays that receive it.

Limits

The stale program cannot be byte-identical to a program bound to FILAMENT_RUNOUT through WAITING. A dead feed can never look exactly like a status that asserts attention or activity.
The profile brightness cap applies to the stale program.
The stale override runs only while feed-level evidence fails. A fresh snapshot that legitimately reports UNKNOWN renders the UNKNOWN binding, not the stale output.
Installing a profile or receiving a receipt never refreshes Printer evidence, so a new profile cannot clear the stale state by itself.