koala73 / koala73/worldmonitor
ops(safety): tpsCallsAttended EMPTY until first on-demand TPS Calls Attended fetch
- Dominant language
- TypeScript
- Stars
- 86.6k
- Forks
- 13.1k
- Avg merge
- 8h 4m
- Merged PRs (30d)
- 825
Description
Tracking issue for the expiring EMPTY cutover acknowledgement on the new `tpsCallsAttended` health probe (`seed-meta:safety:tps-calls-attended`).
`seed-tps-open-data.mjs` is on-demand only: not a Railway cron, not FAST/SLOW bootstrap, not a `seed-bundle-canada` member. The seed-meta key cannot exist until the first explicit fetch after deploy. EMPTY through that first-run window is the deploy gap, not a producer failure.
Separate from #7035 (`tpsMci`). Each acknowledged degradation needs its own owner. After the first successful on-demand publish, prune the acknowledgement.
Does not cover GTA Update (terms-review, writer disabled, not a health probe).
Contributor guide
Research direction
Start with seed-tps-open-data.mjs and trace the seed-meta key seed-meta:safety:tps-calls-attended. Confirm the first successful on-demand publish after deploy, then prune the acknowledged EMPTY state; the issue names no test or acknowledgement file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100