ops(safety): torontoTps EMPTY until first seed-bundle-canada TPS tick

Tracking issue for the expiring EMPTY cutover acknowledgement on the new `torontoTps` health probe (`seed-meta:safety:toronto-tps`).

`scripts/seed-toronto-tps.mjs` is a 15-minute `seed-bundle-canada` member. The seed-meta key cannot exist until the first eligible Railway tick after deploy (bundle cron is `*/5`; the 0.8-interval freshness gate admits this member on the third tick). EMPTY through that first scheduled poll is the deploy gap, not a dead producer.

Owner for the `scripts/seed-freshness-baseline.json` acknowledgement on #6682 / #7033. After the first successful TPS publish, prune the acknowledgement.

Does not cover Toronto Fire live CAD (`torontoTfs`) — that probe needs its own tracking issue.

Read scripts/seed-toronto-tps.mjs and the acknowledgement in scripts/seed-freshness-baseline.json, then review the related context in issues #6682 and #7033. Confirm the first successful Toronto TPS publish after deployment, and consider the work done when the expiring acknowledgement is pruned without changing the separate Toronto Fire probe.

Written by the indexing model from the issue text.