feat(gateway): serve Claude Opus 5 on Pro + fix Opus 4.8's under-reserving context window

[ndemianc]

Two changes to the gateway roster. One catalog row is the whole first feature — it goes live on deploy with no editor release, since the client reads the roster from GET /account/models.

1. Opus 5, entitled from Pro up

Price confirmed against the OpenRouter models API (2026-07-24):

	in	cached read	out	context
anthropic/claude-opus-5	$5/M	$0.50/M	$25/M	1,000,000

Identical to Opus 4.8's sheet — so Pro's per-turn economics don't move (same 6.67× multiplier, same ~39 turns on $20). What Pro gains is the newer model and the 1M window.

Two things that fail quietly if you get them wrong:

• Row placement. Rates tie Opus 4.8, so multipliers tie. The monotonic-multiplier spec orders by cost, not recency — appending at the end or grouping by family breaks it. Placed directly after 4.8, where equal neighbours sort fine.
• status:. allowed_models filters on :confirmed. An :assumption row renders in the picker and then silently falls back to the plan default when selected, with no error.

2. Opus 4.8's context window was 200K — it should be 1M

Not cosmetic. estimate_cost_micros clamps its input estimate down to the window:

est_input = [ est_input, ctx ].min if ctx.positive?

So the window is a ceiling on what the admission guard reserves. A 600k-token turn on Opus 4.8 was reserved as if it were 200k — about a third of what it can cost — the opposite of the "reserve high, reconcile down on settle" contract. Raising it makes reservations honest. It never over-bills: the ledger still meters real usage afterwards.

Every OpenRouter endpoint for 4.8 (Anthropic first-party, Bedrock, Azure, Google) advertises 1M/128K.

This also corrects a comment I had backwards on the Opus 5 row: understating context under-reserves, it does not "refuse turns the budget can afford."

Deliberately not changed

Pro's default stays moonshotai/kimi-k2.7-code. Opus 5 is 6.67× per turn; defaulting would drain a Pro budget ~7× faster. Opt-in pick, same call as the K3 rollout. Opus 4.8 stays on the roster.

Verification

Runtime behavior (a wrong id here downgrades silently rather than erroring):

orbits_pro / pro_plus / max / ultra  -> REACHES anthropic/claude-opus-5
free                                 -> downgraded to openai/gpt-oss-120b
multiplier 6.67 (ties 4.8) · rate_for {5.0, 0.5, 25.0} · ANTHROPIC_FAMILY -> caching on

236 LevelCode examples pass. The two new context specs were checked as a negative control — reverting the window to 200K fails both, so they genuinely guard the bug rather than just restating the constant.

Marketing features: copy now names Opus 5; it's served verbatim by /api/levelcode/v1/pricing, so the pricing page updates on deploy with no frontend change.

Editor companion: levelcode #42 (BYOK picker + the same context correction in the local caps table).

[Copilot]

Pull request overview

Adds the anthropic/claude-opus-5 model to LevelCode’s server-driven model roster (and updates pricing/plan copy + specs accordingly), while also introducing a production Sidekiq Web mount gated by Devise admin (and optional email allowlist).

Changes:

• Add anthropic/claude-opus-5 as a confirmed, Pro-entitled OpenRouter model with 1M context in ModelCatalog::MODELS.
• Update LevelCode plan marketing copy and multiple specs to include/validate Opus 5 availability and multiplier parity with Opus 4.8.
• Mount Sidekiq::Web at /web_sidekiq in all environments behind Devise admin + optional SIDEKIQ_WEB_EMAILS allowlist, with request specs.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
app/services/levelcode/model_catalog.rb	Adds Opus 5 model entry (confirmed pricing, 1M context, Pro+) adjacent to Opus 4.8.
lib/levelcode.rb	Updates plan features strings to name Opus 5 in pricing copy.
spec/requests/api/levelcode/v1/account_spec.rb	Extends account/models request spec to assert Opus 5 appears live with expected multiplier.
spec/models/levelcode_model_catalog_spec.rb	Adds Opus 5 to catalog confirmation + multiplier expectations and entitlement assertions.
spec/models/levelcode_plans_spec.rb	Updates allowed_models roster expectations to include Opus 5 for Pro.
config/routes.rb	Mounts Sidekiq Web at /web_sidekiq behind admin/authenticate + optional email allowlist.
spec/requests/sidekiq_web_spec.rb	Adds request-level coverage ensuring Sidekiq Web is reachable only when properly entitled/allowlisted.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ndemianc]

This one is moot here — config/routes.rb came from the unpushed 74d3a28 that I'd accidentally branched over, and it's no longer in this PR after the rebase. The point looks correct though (the HTML catch-all before not_found means a non-admin gets the SPA, not a 404), so it's worth keeping for whoever lands the Sidekiq change.

[ndemianc]

Also moot here — spec/requests/sidekiq_web_spec.rb came from the same accidentally-included commit and is out of this PR now. Worth carrying over to the Sidekiq PR.

[ndemianc]

You were right, and this was my error — thank you. I branched off the local develop, which had an unpushed commit (74d3a28, the Sidekiq console work) that I then carried into this PR unintentionally. The PR description was accurate about my intent and wrong about its contents.

Rebased onto origin/develop (now at 48efb77), so this PR is back to exactly what it claims: 2 commits, 5 files, all LevelCode roster. config/routes.rb and spec/requests/sidekiq_web_spec.rb are no longer in the diff. The Sidekiq commit is untouched on the local branch and can go up as its own PR — which is what you suggested.