Provider migration verification protocol: GREP THE BUNDLE before trust…
Decision
Provider migration verification protocol: GREP THE BUNDLE before trusting any docs/summary; INVOKE BEFORE TRUSTING available=true; map provider-specific thinking ceilings empirically (live error → schema → docs in that order). Anchored as standard pre-flight for any future provider/model swap (codex, anthropic, gemini, etc.).
Rationale
Three concrete failures this session traced to two root biases (anchoring on summarized docs + confirmation on available=true flag): (1) WebFetch summary hallucinated gpt-5.5 under openai provider — only verified by grepping the actual installed bundle. (2) gpt-5.5-pro showed available=true in models list but Codex backend rejected at runtime with explicit ChatGPT-tier error. (3) Schema accepted xhigh in JSON but backend silently capped at off for openai-codex. The empirical hierarchy that actually works: live invocation → bundle grep → schema validation → docs. Reverse of intuitive trust order. Codifying as: “no provider migration commits without one full round-trip per agent under the new model + thinking config”. Smoke-test-first, document-second.
Alternatives Rejected
Outcome
Pending