System type not updated after initial config message from trunk-recorder

[LumenPrima]

Bug

P25 trunked and P25 conventional systems are both displayed as conventional system_type in tr-engine. Restarting trunk-recorder fixes it — TR only publishes the system config (including type) at startup via the config MQTT message.

Root Cause

tr-engine ingests the system type from trunk-recorder's initial config message. If:

• tr-engine starts before trunk-recorder, it misses the config message
• tr-engine restarts while TR is running, TR doesn't re-publish
• The system type defaults to conventional when unknown

Expected Behavior

tr-engine should either:

1. Request/re-derive system type from subsequent MQTT messages (e.g., presence of control channel data implies trunked)
2. Persist system type from the config message so it survives restarts
3. Re-request config from TR on reconnect (if TR supports it)

Workaround

Restart trunk-recorder after tr-engine is running.

Reported by gofaster in Discord #bot-support (2026-03-30).