claude
c61b0b3968
It reaches the daemon through ipc.CoreAPI and nothing else, so a telegram turn takes the path POST /api/chat already takes: Chat returns the reply and the trace id it collected off the context (V-630), and CorrectTurn writes the label. Nothing in internal/delivery learns what a handler is. Wired on the unlocked start and on the passkey unlock, like the mail intake, so telegram behaves the same either way. A sink that will not build is logged rather than fatal here, because wireDispatcher already failed the boot on the same config.