docs: Update the plugin catalog

[esnible]

Summary

I was unaware of all the plugin settings in litellm-budget-track because the catalog did not include them.

This PR updates the catalog to match the current code.

My intention is to "graduate" this catalog and have it appear in https://www.rossoctl.dev/ soon, so it is extremely high priority to me that users and AI can discover which plugins we offer, and how to configure them.

Summary by CodeRabbit

• Documentation
  • Documented per-token pricing options for streamed responses in litellm-budget-track.
  • Documented token ceilings and session fallback pooling for session-budget.
  • Clarified that session-budget requires at least one usage limit or duration constraint to be configured.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: e5381799-be6d-4860-8bee-e245417dc3f3

📥 Commits

Reviewing files that changed from the base of the PR and between 25b3a4a and 5b695bb.

📒 Files selected for processing (1)

• authbridge/docs/plugin-catalog.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The plugin catalog documents streamed-response pricing fields for litellm-budget-track and per-kind token limits, fallback behavior, and required constraints for session-budget.

Changes

Plugin catalog configuration

Layer / File(s)	Summary
Configuration reference updates authbridge/docs/plugin-catalog.md	The catalog adds streamed-response pricing fields for litellm-budget-track. It adds per-kind token ceilings, default_session_fallback, and configuration requirements for session-budget.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to 5b695

The plugin catalog now documents available pricing and session-budget settings. The documented session-budget behavior matches the implementation, with no remaining merge-readiness risk identified.

Suggested reviewers: huang195

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the plugin catalog documentation.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[esnible]

Note that I generated this using AI, the prompt was

There is a plugin catalog at authbridge/docs/plugin-catalog.md
- Consult the code to determine if any plugins have been added that are not present in the catalog
- Consult the code to determine if any plugins in the catalog have been removed
- At least one plugin has new parameters.  Check that the parameters in the catalog match the code.  If not, update the catalog.

[evaline-ju]

lgtm

[Alan-Cha]

Suggested change

	- `input_cost_per_token` (float64) — USD per uncached input token. Optional; used to price **streamed** responses, whose `x-litellm-response-cost` header is 0 because the total isn't known when headers are sent. When every rate is zero, streamed responses contribute 0 to the ledger.
	- `input_cost_per_token` (float64) — USD per uncached input token. Optional; used to price **streamed** responses, whose `x-litellm-response-cost` header is 0 because the total isn't known when headers are sent. When every rate is 0, streamed responses contribute 0 to the ledger.

Why are some 0s spelled out and other not?

[Alan-Cha]

I don't quite understand the meaning of everything after the semi colon. Maybe I don't have enough context