fix(veo): reject 4K resolution for veo-3.0 models

[MillerMedia]

Description

Veo3VideoGenerationNode advertises in its resolution tooltip that 4K is not available for veo-3.1-lite or veo-3.0 models, but the execute-time guard added in #13330 only rejected the lite combination:

if "lite" in model and resolution == "4k":
    raise Exception("4K resolution is not supported by the veo-3.1-lite model.")

Selecting 4K with veo-3.0-generate-001 or veo-3.0-fast-generate-001 would fall through to /proxy/veo/<model>/generate; the upstream Google API would reject it, surfacing as a generic API error rather than the intended client-side validation message.

Not observed — #13330 only landed today, so filing this as a code-review finding rather than a bug report.

This PR broadens the guard and updates the error message to match the tooltip.

if resolution == "4k" and ("lite" in model or "3.0" in model):
    raise Exception("4K resolution is not supported by the veo-3.1-lite or veo-3.0 models.")

Notes

• Veo3FirstLastFrameNode has the same-shaped guard but only exposes veo-3.1-generate, veo-3.1-fast-generate, and veo-3.1-lite, so its existing lite-only check is already correct — no change needed there.
• The price_badge expression still falls through to the standard 3.0 rate for the now-rejected 4K + 3.0 combo. With the stricter guard the combo can no longer execute, so the mispriced badge is display-only. Happy to tighten that in a follow-up if preferred.
• No test changes: this file has no existing unit tests for the execute guards.

API Node PR Checklist

Scope

• Is API Node Change

Pricing & Billing

• Need pricing update
• No pricing update

If Need pricing update:

• Metronome rate cards updated
• Auto‑billing tests updated and passing

QA

• QA done
• QA not required

Comms

• Informed Kosinkadink

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 804760f4-eef4-4fff-bd11-49075ac0e552

📥 Commits

Reviewing files that changed from the base of the PR and between 43a1263 and 65eb54a.

📒 Files selected for processing (1)

• comfy_api_nodes/nodes_veo2.py

---

📝 Walkthrough

Walkthrough

The change modifies the 4K resolution validation in the Veo 3 video generation system. Previously, 4K resolution was blocked only for models containing "lite". The updated logic now blocks 4K resolution for models containing either "lite" or "3.0". The corresponding error message was updated to reference both veo-3.1-lite and veo-3.0 models instead of only veo-3.1-lite. This expands the scope of models subject to the 4K restriction.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: broadening the 4K resolution rejection guard to include veo-3.0 models alongside veo-3.1-lite.
Description check	✅ Passed	The description is well-detailed and directly related to the changeset, explaining the guard clause improvement, its rationale, and relevant context about related nodes.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[Kosinkadink]

Wanting to confirm with @bigcat88 first

[bigcat88]

LGTM