Opus finding
Spotlight history sort key mismatch with persisted field name (`featured_at` vs `fork`)
mediumbugmedium
- skills/fleet-state/SKILL.md:118-122
The skill assumes `contributor-spotlight-history.json` entries carry `featured_at` and `fork` fields, but this is never cross-referenced with the producing skill's schema in this PR. If the constituent contributor-spotlight skill writes a different key (e.g., `featured_date`, `fork_full_name`, `picked_at`), `sort_by` will silently sort by nulls and `SPOTLIGHT_FORK`/`SPOTLIGHT_DATE` will be empty, causing the spotlight section to render as missing without any error. The bullet `pick whichever is newest` would then be wrong without any FLEET_STATE_PARTIAL signal.
Recommendation
Either (a) cite the exact schema produced by `contributor-spotlight/SKILL.md` and assert it here, or (b) tolerate alternative key names with `.fork // .fork_full_name`, `.featured_at // .picked_at // .ts`, and log `FLEET_STATE_SPOTLIGHT_SCHEMA_UNKNOWN` if neither resolves.