feat(reddog): add Kimi K3 fusion research

[Foundup]

What changed

• adds the exact OpenRouter Kimi K3 model (moonshotai/kimi-k3) to the RedDog Fusion critic panel while retaining Kimi K2.7 Code for implementation comparison and capacity fallback
• gives Kimi K3 its required 4096-token critic budget, sends mandatory maximum reasoning, omits unsupported temperature, and records the per-panel budget in review receipts
• extends the existing AutoResearch/AI Gateway path with an explicit-only OpenRouter provider, Kimi K3 candidate metadata, capability/pricing data, and separate input/output cost accounting
• prevents explicit research candidates such as OpenRouter from leaking into normal optimized routing or bypassing the established candidate-pool, benchmark, promotion, and feedback-ledger gates
• updates RedDog and AI Gateway interfaces, roadmaps, ModLogs, and extension contract/version metadata

Why

The existing AutoResearch combination and promotion machinery was already present. The operational gap was that its configured gateway could not invoke OpenRouter, while RedDog Fusion did not know the released Kimi K3 identifier or its request constraints. Low output budgets also let Kimi K3's mandatory reasoning consume the response, causing Fusion to fail closed without a challenging critic.

Validation

• 283 passed across AI Gateway, advisory/Fusion hardening, and RedDog architect tests
• complete RedDog extension contract passed
• strict WSP_00 awakening/check passed
• live OpenRouter single-model Kimi K3 smoke passed
• live manual RedDog Fusion passed quorum with Kimi K3 recorded as the challenging critic and a 4096-token panel budget

Truth boundary

This registers Kimi K3 as an available research candidate and makes it executable through the existing governed path. It does not silently mutate the external candidate pool, auto-promote Kimi K3, or bypass benchmark receipts and promotion gates.