Make canonical scheduling core-owned

[dcellison]

Summary

• move APScheduler ownership from the optional Telegram adapter into the transport-neutral Kai application host
• persist deterministic schedule firings so reminders and agent runs recover idempotently across restart
• route reminder and agent outcomes through canonical Workshop messages, runs, bindings, and the durable delivery outbox
• preserve once, daily, interval, conditional, auto-remove, and notification behavior while making scheduling available in Workshop-only mode
• expose canonical ownership and nonterminal firing diagnostics through make install-status

Safety and compatibility

• active jobs without one complete canonical owner fail closed at core startup
• Telegram /job and internal scheduling routes remain supported, but no longer manipulate Telegram JobQueue
• scheduled work cannot create Telegram streaming previews; final delivery is binding-aware and outbox-backed
• APScheduler is now an explicit core dependency rather than an incidental Telegram extra

Validation

• make check
• make typecheck
• make check-install-constraints
• full pytest suite
• focused core-host, scheduler, canonical execution, Telegram adapter, webhook, schema, and installer tests

Closes #1061