fix: multiplex cron delivery routes through correct profile bot

[xbrxr03]

Bug

When multiplex_profiles is enabled, all cron job deliveries route through the default profile's Telegram adapter regardless of which profile owns the cron job. This causes cross-profile message leakage — e.g., SCOUT's hourly reports appearing in JARVIS's chat, CHASE's EOD briefs leaking into the wrong DM, etc.

Root Cause

resolve_delivery_transport() in _deliver_result() receives only the default profile's adapters dict. The per-profile adapters (_profile_adapters on GatewayRunner) are never passed through the cron delivery chain, so every delivery resolves to the main profile's bot.

Fix

Three-file change threading profile_adapters through the cron delivery chain:

1. gateway/run.py: Pass runner._profile_adapters to the cron scheduler at startup.

2. cron/scheduler_provider.py: Thread profile_adapters through start(), _start_multiplex(), and the per-profile cron_tick() calls.

3. cron/scheduler.py:

   • Add profile_adapters param to tick(), run_one_job(), and _deliver_result().
   • Stamp each job with _profile_home (the profile's HERMES_HOME) in tick() before dispatching to ThreadPoolExecutor. This is critical because Python 3.11's ThreadPoolExecutor does not propagate ContextVar overrides to worker threads — so _get_hermes_home() inside _deliver_result() would return the default home, not the profile's.
   • In _deliver_result(), when profile_adapters is provided, match the job's _profile_home to the correct profile's adapter and construct a DeliveryTransport that routes through that profile's bot.

Verification

2026-08-05 07:21:58 INFO cron.scheduler: Job c6c2af16728f: using profile outreach adapter for telegram delivery
2026-08-05 12:00:30 INFO cron.scheduler: Job 0a6b7a0c6c34: using profile outreach adapter for telegram delivery
2026-08-05 22:02:01 INFO cron.scheduler: Job e8c05d2b5e45: using profile chase adapter for telegram delivery

Messages now appear in the correct profile's Telegram chat.

Why _profile_home instead of ContextVar?

The multiplex cron tick sets HERMES_HOME_OVERRIDE via set_hermes_home_override() before calling cron_tick(), and resets it in a finally block. But cron_tick() dispatches jobs to a ThreadPoolExecutor. Python 3.11 does not propagate ContextVar values to ThreadPoolExecutor workers (fixed in 3.12+), so _get_hermes_home() inside _deliver_result() would always return the default home. Stamping _profile_home on the job dict in the main thread (where the override is active) before dispatch solves this reliably across Python versions.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #73363. Both patches correct multiplex cron delivery that otherwise uses the default profile bot. #73363 is the earlier focused implementation and includes regression coverage for connected, empty, and absent secondary adapter maps.