Opus finding
LRU cap on targets uses wrong recency field
lowbughigh
- skills/price-threshold-alert/SKILL.md:233-234
`first_seen_below_at` is set once on first observation and never updated. Using it as the LRU key means recency is actually 'order of first appearance', not 'order of most-recent activity' — a target hit yesterday could be evicted before a never-touched target observed two weeks ago. Also, an operator who re-passes the same target via `${var}` does not refresh the timestamp (no spec for that), so re-passed targets get evicted as if abandoned.
Recommendation
Either (a) refresh `first_seen_at` each run the target appears in `${var}`, or (b) use `max(first_seen_at, hit_at, last_observed_at)` as the LRU key. Document the choice explicitly.