Primary finding
Step 8 state rotation will overwrite stars_7d_ago on every run, breaking 7-day deltas
highbughigh
- skills/ai-framework-watch/SKILL.md:240-246
- aeon.yml:122
The skill is scheduled weekly (Monday 08:30 UTC), so reading the prior run's `stars` value into `stars_7d_ago` only works if runs are exactly 7 days apart. The rotation rule is unconditional (every run rotates), with no timestamp guard analogous to the 30d field. Any manual workflow_dispatch, retry, or backfill run within the same week would clobber the 7-day baseline (the new `stars_7d_ago` would be ~current stars), causing the next legitimate weekly 7d delta to render near zero. Compare to the 30d rule which is explicitly gated by an `_at` timestamp; the 7d rotation lacks the same guard.
Recommendation
Mirror the 30d pattern: store `stars_7d_ago_at`, only rotate when prior `stars_7d_ago_at` is ≥6 days old; otherwise carry forward. Or only update state on the scheduled weekly cadence and treat manual dispatches as read-only.