core: re-arm and re-install after the core module reloads
Editing KetylCore re-runs that chunk and leaves its dependents alone: the module
table keeps its identity, its functions are replaced, and every local behind
them starts over — including the record of who holds the controls and the table
the conductor leaves its handlers in. Neither component's awake() runs again to
notice, so a mid-session edit left the ketyl still and the bus deaf while every
reading said the game was fine.
Each half now watches for the one reading that says it happened — nobody holding
the controls, an empty handler table — and re-arms or re-installs from update.
Verified by reloading the module under a live run: the pilot re-armed, the
conductor re-installed, and one uiIntent produced exactly one runStart.