feat:OpenAPI: max_output_size descriptions reference final_model limits

[HavenDV]

Summary by CodeRabbit

• Documentation
  • Clarified the max output size description to reflect dynamic limits based on the selected model, replacing the fixed 4000-token cap.
  • Added a link to a chart detailing model-specific maximums for easier configuration.
  • Text-only update; no changes to behavior, defaults, or types.
  • Improves accuracy and consistency of public API documentation.

[coderabbitai]

Walkthrough

Updated OpenAPI descriptions for max_output_size in LemurBaseParams and LemurTaskParams to reference the final_model’s maximum and link to a chart. No types, defaults, or behavior changed.

Changes

Cohort / File(s)	Summary of Changes
OpenAPI docs wording updates src/libs/AssemblyAI/openapi.yaml	Revised descriptions for LemurBaseParams.max_output_size and LemurTaskParams.max_output_size to note the cap depends on final_model and added a documentation link; no schema or logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (2 passed, 1 warning)

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The current title “feat:@coderabbitai” is vague and unrelated to the actual changes, which focus on updating the max_output_size descriptions in the OpenAPI spec; it neither summarizes the documentation updates nor highlights the primary change.	Rename the pull request title to concisely describe the update to the OpenAPI documentation for max_output_size (e.g., “docs(openapi): update max_output_size description to dynamic final_model cap”).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A nibble of text, a hop of a line,
Tokens now flex to the model’s design.
Charts in the clover, links in the dew,
Docs get crisper—hippity, woo!
I twitch my whiskers, delighted to see
Limits aligned with final_model’s key.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 293ee5c and 380cc9e.

⛔ Files ignored due to path filters (2)

• src/libs/AssemblyAI/Generated/AssemblyAI.Models.LemurBaseParams.g.cs is excluded by !**/generated/**
• src/libs/AssemblyAI/Generated/AssemblyAI.Models.LemurTaskParamsVariant1.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

• src/libs/AssemblyAI/openapi.yaml (2 hunks)

🔇 Additional comments (2)

src/libs/AssemblyAI/openapi.yaml (2)

5677-5677: LGTM — consistent wording and valid link
No lingering “4000” references; link matches the base parameters.

---

5613-5613: Docs path usage verified; no stale “up to 4000” mentions found
Docs link /docs/lemur/customize-parameters#change-the-maximum-output-size appears only in the generated YAML and bindings—manually verify it resolves in the published docs.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bot/update-openapi_202509101237

---

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 and usage tips.}