Stale-container recorder: engine checks, always-on sampling, findings that survive the log - #279

…t and end

Krathe, 2026-09-24, after an Aura Designer aura went stale briefly and the
recorder had nothing: "the log should find the problem -- it's pointless if it
keeps missing it."

It missed for three reasons, all fixed here:

1. It sampled only in combat. It now samples all the time -- every second in
   combat, every two seconds out of it.

2. Saved rows were merged by key with no date, and the detail was written once
   and never refreshed. A repeat in a later session looked like the old row
   with a bigger count, and new diagnostic fields never appeared on a key that
   already existed. Rows now carry their session, and the detail is always the
   latest.

3. Every check trusted DF's own bookkeeping. Two new checks ask the engine:
   ENGINE-UNIT (the container's own GetUnit differs from the frame's unit, so
   it is parsing someone else's auras) and SHOWN-DISABLED (the window is shown
   but the container is disabled, so it is not listening for UNIT_AURA). They
   cover every lane: aura rows, dispel, the dispel icon row, every Aura Designer
   container store, and the AD slot owner.

Every finding now goes into the debug log as well, under a new UNITSCAN
category: one START line when a problem appears and one CLEAR line with its
duration when it goes away. That is the timeline, next to the roster, latch
and retarget lines, so a reload is the whole report.

Hidden frames are skipped (a frame nobody can see cannot show a stale aura;
the old version filled the log with frames whose unit had left). Test mode is
skipped. Whether a container is still registered for UNIT_AURA cannot be
checked: IsEventRegistered is refused on containers by the EventRegistrations
forbidden aspect, as proven in game; SHOWN-DISABLED is the readable half.

A mock harness caught one bug before this shipped: `okE and en or nil` turns
a disabled container's false into nil, so SHOWN-DISABLED could never fire.
Explicit ifs now.

The panic snapshot (MarkAuraFault) records the engine binding and enabled
state per lane too.

…icted

The range-crossing aura snapshot moves to the RANGE channel (noisy, off by
default). It fired on every crossing of every unit and filled ~78% of a
raid evening's log, and the log evicts oldest INFO first.

The recorder's start, clear and snapshot lines are now WARN so they outlive
the INFO chatter, and each session leaves a heartbeat row in
DandersFramesDebugDB.unitscanRuns (armed, samples, last sample, findings),
so an empty findings list can be told apart from a recorder that never ran.

Also records why a shown-but-stale aura icon cannot be detected: the engine
secret-wraps button visibility and icon, out of combat too.