Disable mt-check-data-outdated.yml schedule; flag data expiring within 3 days as outdated

[Copilot]

The scheduled workflow for checking outdated data is being disabled, and the staleness check is being made more proactive — triggering a sync before data actually expires rather than only after.

Changes

• mt-check-data-outdated.yml: Comment out the schedule trigger; workflow_dispatch remains available for manual runs.

• check_data_outdated.sh: Expand the "outdated" condition from last_departure ≤ now to last_departure ≤ now + 3 days, so a sync is triggered before expiry rather than after.

# Before: only outdated if already expired
if [[ "$DEPLOYED_LAST_DEPARTURE_SEC" -gt "$NOW_TIMESTAMP_SEC" ]]; then
  exit 0  # not outdated

# After: outdated if expiring within the next 3 days
THREE_DAYS_SEC=$((3 * 86400))
if [[ "$DEPLOYED_LAST_DEPARTURE_SEC" -gt "$((NOW_TIMESTAMP_SEC + THREE_DAYS_SEC))" ]]; then
  exit 0  # not outdated

Original prompt

---

This section details on the original issue you should resolve

<issue_title>mt-check-data-outdated.yml > check_data_outdated.sh</issue_title>
<issue_description>shared-overwrite/.github/workflows/mt-check-data-outdated.yml
shared-opt-dir/agency-parser/check_data_outdated.sh

Let's try to:

• disable mt-check-data-outdated.yml workflow
• check_data_outdated.sh should return true if outdated in the next 3 days as well</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes mt-check-data-outdated.yml > check_data_outdated.sh #629

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mmathieum]

#628 should be good for now