feat(regulatory): Railway cron — schedule seed-regulatory-actions.mjs every 2h

[koala73]

Context

Part of the Regulatory RSS pipeline. Final wiring step — depends on #2492, #2493, #2494 being merged and deployed.

This is task 4/4.

What to do

Add a 2-hour cron entry for seed-regulatory-actions.mjs to the Railway cron service configuration.

• Script: node scripts/seed-regulatory-actions.mjs
• Schedule: every 2 hours (0 */2 * * *)
• Rationale: Redis TTL is 7200s (2h). Cron at 2h = 1× cadence with no gap window. Regulatory actions don't change by the minute — 2h is appropriate.

Acceptance criteria

• Cron job runs every 2 hours in Railway
• regulatory:actions:v1 key is populated in Redis after first successful run
• seed-cross-source-signals.mjs picks up the key on next run (30min cadence) and emits REGULATORY_ACTION signals when HIGH/MEDIUM-tier actions are present

[lspassos1]

Work is in #2569.

This adds the repository-side automation for the Railway cron configuration:

• scripts/railway-set-watch-paths.mjs now syncs cronSchedule as well as watchPatterns and startCommand
• seed-regulatory-actions is marked as a required seed service
• the expected cron is codified as 0 */2 * * *
• tests/railway-set-watch-paths.test.mjs covers the new path

This branch is currently stacked on #2568, which depends on #2567 and #2564.

The live Railway cron was not applied from this environment because no RAILWAY_TOKEN / Railway login is available locally. After auth is available, running node scripts/railway-set-watch-paths.mjs --dry-run and then node scripts/railway-set-watch-paths.mjs should apply it.

[lspassos1]

Applied this in Railway for magnificent-recreation.

seed-regulatory-actions is now configured against koala73/worldmonitor on main, with /scripts as the root directory, node seed-regulatory-actions.mjs as the start command, the watch paths from #2569, and cron 0 */2 * * *.

Refs #2569.