[backryun]

Summary

• refresh the curated ChatGPT Web GPT-5.5/GPT-5.6 catalog and effort variants
• map each curated variant to its actual upstream live slug for authoritative catalog validation
• include the GPT-5.6 Luna free lanes in the free-model catalog

Validation

• node --import tsx/esm --test ChatGPT Web and live-catalog reconciliation tests (123 passing)
• npm run typecheck:core
• git diff --check

[diegosouzapw]

Reviewed PR #10637. Ran the full touched chatgpt-web test suite in an isolated worktree — all 123 tests pass, matching the PR description. Confirmed the CI redness on this PR (Fast Quality Gates / Unit Tests fast-path ×4 / ESLint / Vitest) is 100% inherited base-red from release/v3.8.50 (tracked in #9985 — i18n-vi-completeness, the SSE-trailer/#10539 stream-utils failures, and the cli-oauth-commands/executor-gitlab ESLint errors), none of it touches any file this PR modifies. The typecheck:core failure I saw locally is an unrelated stale-node_modules/omniglyph-1.4.0 environment issue on my end, also outside this PR's diff. Verified the README/SVG free-forever counter bump (56→57) is correct given the provider-dedup counting logic. No security, DB-migration, or cross-layer gaps found. One nit: the retired chatgpt-web IDs (gpt-5.6-pro, gpt-5.6-thinking, gpt-5.5-thinking, gpt-5.3-instant, o3) have no back-compat aliases, so saved configs referencing them will stop resolving — consistent with this provider's prior GPT-5.4 cutover precedent, flagging for awareness rather than as a blocker. Looks ready to merge.