Primary finding
Target registration field name `first_seen_below_at` is misleading for `side=below` targets
lowdocs-gaphigh
- skills/price-threshold-alert/SKILL.md:71-78
- skills/price-threshold-alert/SKILL.md:146-148
- skills/price-threshold-alert/SKILL.md:213-215
The field is always populated regardless of side, but its name encodes only the `side=above` case (price 'below' target). For a `side=below` target (current > target), the field actually records 'first seen above'. This will confuse future maintainers and may cause bugs when someone interprets the field literally.
Recommendation
Rename to `first_observed_at` (neutral) or split into two fields. Update the LRU sort key reference in Step 8.