fix: verify Slack webhook setup challenges
Slack setup challenges currently bypass the adapter and return the challenge even when unsigned. Verify this shortcut using each app's existing signing secret, exact raw body and a five-minute replay window. Reject missing/invalid signatures before explicit bot initialization. Resolve supported platform handlers before POST initialization, and reject inherited object keys in GET/POST lookups.
This is a bounded successor to existing #297 (8e907cead1e77a06352a8b0acc6867549ba6d297) under Mono358, adapted to the current shared routing architecture on main e2fb91883891cb55aaac19a70822ccf5152758c5. Coding, content and chat routes use their respective existing secrets. Ordinary events remain with their existing adapter; this does not defer static bot imports or claim all startup effects are avoided. No old branch retarget or unrelated WhatsApp feature is included.
Validation: the new regression tests initially failed31/passed6; final focused suite passes244tests across39files. Full lint, changed-file formatting and diff checks pass. Local whole-project TypeScript has211 diagnostics byte-identical to baseline; clean CI now passes all four required checks and response-contract typecheck. Independent Standards/Spec review identified missing GET probe coverage, now added; final exact-commit Standards and Spec reviews have no remaining actionable findings at ab969dee78e6fd36967ef350ba04495c59eef410 (tree 6ad9331153b959f8960583f42ec772e613f1d6eb).
No real Slack webhook, provider/customer/database/billing operation, deployment setting or credential value was accessed. Live delivery and app configuration are not verified. Verification scope and primary Slack contract link are in docs/verification/slack-webhook-verification.md.