mirror of
https://github.com/Corfirean/coa-server-manager.git
synced 2026-11-19 11:25:56 +00:00
launcher::relay does what BugReport/relay.py and manage.py relay-worker do, with the same spool: the <key>.status files the world reads, the journal relay.sqlite3 (deliveries, settings), relay.lock (byte 0) and the relay-ready record. Service answers map to the same states and retry times; a post interrupted mid-flight stays uncertain and is never resent. When coa-launcher.exe supervises a world it runs the relay itself; the Python supervisor still runs relay.py. Verified: - examples/relay_equivalence: the same reports and scripted service answers through relay.py and the Rust relay give identical statuses, journal rows (including retry times) and posts, and each continues the other's journal. - examples/manager_launcher_e2e on a disposable repack: supervisor and relay are coa-launcher.exe, start/stop interoperates with manage.py. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>