docs: add a combined oauth2 + models-info example

[stephane-segning]

Summary

Adds a concrete example of the two plugins working together — one provider authenticated by @vymalo/opencode-oauth2 and enriched by @vymalo/opencode-models-info. Docs-only.

{
  "plugin": ["@vymalo/opencode-oauth2", "@vymalo/opencode-models-info"],
  "provider": {
    "my-provider": {
      "npm": "@ai-sdk/openai-compatible",
      "options": {
        "baseURL": "https://api.example.com/v1",
        "oauth2": { "issuer": "https://auth.example.com", "clientId": "opencode-client", "scopes": ["openid", "profile", "offline_access"] },
        "meta": { "modelsInfoUrl": "https://api.example.com/v1/models" }
      }
    }
  }
}

Key point called out

List @vymalo/opencode-oauth2 first in the plugin array. Config hooks run in registration order, so oauth2 must run before models-info to stamp the bearer onto the provider headers before the metadata fetch happens. The example explains the boot sequence (oauth2 auth + discovery + bearer stamp → models-info fetch + enrich) and notes that no models block or Authorization header is needed.

Where

• Top-level README — new "Both plugins together" subsection in the companion section.
• Package README — new example under "Auth composition".

Markdown only → Biome unaffected (62 files clean).

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the documentation in README.md and packages/opencode-models-info/README.md to include examples of configuring the @vymalo/opencode-oauth2 and @vymalo/opencode-models-info plugins together. The feedback suggests changing the example modelsInfoUrl from https://api.example.com/v1/models to https://api.example.com/v1/models/info in both files to prevent confusion with standard model discovery endpoints that do not return rich metadata.