Reviewed and documented merged PRPublic

Agent

Model

GPT-5.2 Codex

Started

Jan 30, 12:45 AM

Messages31

Downloads0

Summary

In Progress

Understand
Reviewed PR description, comments, commits, and changed files.
Understand
Understand
Identified and read linked issues.
Understand
Understand
Analyzed PR diff and changelog updates.
Understand

You are given one or more GitHub PR URLs: https://github.com/badlogic/pi-mono/pull/1051 looks good,already merged, just needs to be documented in @models.md i think

For each PR URL, do the following in order:

Read the PR page in full. Include description, all comments, all commits, and all changed files.
Identify any linked issues referenced in the PR body, comments, commit messages, or cross links. Read each issue in full, including all comments.
Analyze the PR diff. Read all relevant code files in full with no truncation from the current main branch and compare against the diff. Do not fetch PR file blobs unless a file is missing on main or the diff context is insufficient. Include related code paths that are not in the diff but are required to validate behavior.
Check for a changelog entry in the relevant packages/*/CHANGELOG.md files. Report whether an entry exists. If missing, state that a changelog entry is required before merge and that you will add it if the user decides to merge. Follow the changelog format rules in AGENTS.md. Verify:
- Entry uses correct section (### Breaking Changes, ### Added, ### Fixed, etc.)
- External contributions include PR link and author: Fixed foo ([#123](https://github.com/badlogic/pi-mono/pull/123) by [@user](https://github.com/user))
- Breaking changes are in ### Breaking Changes, not just ### Fixed
Check if packages/coding-agent/README.md, packages/coding-agent/docs/.md, packages/coding-agent/examples/**/.md require modification. This is usually the case when existing features have been changed, or new features have been added.
Provide a structured review with these sections:
- Good: solid choices or improvements
- Bad: concrete issues, regressions, missing tests, or risks
- Ugly: subtle or high impact problems
Add Questions or Assumptions if anything is unclear.
Add Change summary and Tests.

Output format per PR: PR: Changelog:

... Good:
... Bad:
... Ugly:
... Questions or Assumptions:
... Change summary:
... Tests:
...

If no issues are found, say so under Bad and Ugly.

PR: https://github.com/badlogic/pi-mono/pull/1051 Changelog:

packages/ai/CHANGELOG.md: Missing entry under ## [Unreleased] -> ### Added for Vercel AI Gateway routing support. Required before merge. I can add it if you want.
packages/coding-agent/CHANGELOG.md: Missing entry under ## [Unreleased] -> ### Added for models.json schema support. Required before merge. I can add it if you want.

Good:

Mirrors the OpenRouter routing pattern, so behavior is consistent.
Adds schema validation for models.json and updates docs with a concrete example.
Keeps compat defaults normalized in detectCompat and getCompat.

Bad:

No direct test coverage for providerOptions.gateway injection in openai-completions. Only the compat fixture was updated.

Ugly:

None found.

Questions or Assumptions:

Should routing apply when provider is vercel-ai-gateway even if baseUrl is a custom domain, or is ai-gateway.vercel.sh the only supported hostname?

Change summary:

Adds vercelGatewayRouting to OpenAICompletionsCompat and model registry schema.
Injects providerOptions.gateway only for Vercel AI Gateway base URLs.
Documents the new compat field in packages/coding-agent/docs/models.md.

Tests:

Not run.