#176 Hermes cron delivery lost during Communications Gateway cutover

[Anonymous]

Originally created by: ilyamxx

Problem

Cron jobs previously delivered results to Slack. After the communications
refactor, jobs can still run successfully, but delivery fails with:

platform 'slack' not configured/enabled

Regression point

Commit 8756b259 removed native messaging credentials and destination settings from Hermes and introduced the Communications Gateway bridge.

The bridge forwards replies to incoming messages but does not route independently scheduled output. Cron still attempts native delivery, which no longer has the required configuration.

Expected behavior

Route scheduled output through an authorized Communication Connection using the gateway’s queue, retries, and diagnostics. Preserve [SILENT] suppression and add an end-to-end regression test.

Verification

The missing path remains in inspected main (bbf77075) and staging (a55e4eac). Slack is the observed example. Freor’s deployment transition and a full runtime reproduction remain unverified.