nfty 1.3.2 — a missing asset image looks like damage

One fix. 2,170 tests, 0 failures.

A missing asset image now looks like damage

SetItemRow.Decode falls back to a 1×1 transparent bitmap rather than throwing — a browser
over a damaged Set should show the damage, not refuse to open. But the moment that
placeholder was published IsLoading went false, the breathing diamond that covers a pending
decode went with it, and the tile settled into a flat empty square: indistinguishable from
a decode still in flight, and from a fully transparent asset, which is a legal thing to mint.

Found by opening a Set whose folder had been half cleaned up — 24 images for a 60-asset Set,
and 36 tiles that looked like they were still thinking.

The decode returns the flag beside the bitmap now, and the tile draws a mark: the same
diamond, so an unfilled tile still looks like part of the product rather than a hole in it,
but static and in the warning ink. Static is the whole point — a pulse means "coming", and
nothing is coming. The detail rail's preview carries the same mark, because a blank square
there is the identical defect one level over, and both carry a tooltip naming what happened.

Two tests either side of it: one asserts the mark is drawn only on the row that lost its file
and that the loading pulse is absent; the other that an intact Set draws no marks at all.
Neither can pass on a constant.

Downloads

	Size	.NET 10 needed
Portable	84 MB	no — unzip anywhere and run. Start here if you are unsure.
Single file	76 MB	no — one .exe. Unpacks itself on first run, so that launch is slower.
Single file, .NET	14 MB	yes — one .exe, runtime left out.
Framework-dependent	14 MB	yes — the same, as a folder.

The two .NET builds need the .NET 10 desktop
runtime; the other two carry everything.