fix(tools): grok-imagine must not default upscale on (Aug 2026 policy)

[andrexibiza]

Summary

The FAL catalog entry xai/grok-imagine-image/v2.0/text-to-image is the only entry defaulting upscale: True, which violates the Aug 2026 opt-in-only upscaling policy. This fails tests/tools/test_image_generation.py::TestFalCatalog::test_upscale_defaults_are_all_off on every open PR right now (it's a pre-existing main bug, unrelated to the individual PRs that each hit it).

Change

• tools/image_generation_tool.py: set the grok-imagine entry's upscale default to False. Per-call upscale=True still works via the explicit tool-schema path (tools/image_generation_tool.py honors an explicit upscale arg over the catalog default), so this only removes the default-on behavior.

Tests

• test_upscale_defaults_are_all_off passes.

Why this PR

Fixes the pre-existing main regression at its source so it stops blocking unrelated PRs' CI. The same one-line change was temporarily carried on #89252 / #88875 / #86419 to get those green; this is the standalone home so each routing/MCP/Discord PR can drop its copy and be reviewed independently.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #89933: both make the same one-line Grok Imagine catalog default-upscale change; #89933 is the earlier open canonical PR.

[andrexibiza]

Confirmed against the exact current heads: #90067 (a2215e3) is a line-level duplicate of #89933 (07f85f3), and #89933 is the better canonical home because it preserves the policy rationale beside the catalog entry. Closing this PR as superseded by #89933; no unique implementation from this branch needs to be retained.

I am transferring the unique topology instead of discarding it with the duplicate:

• fix(image_gen): Grok Imagine 2.0 upscale default no longer breaks main CI (opt-in policy) #89933, Main is green again: FAL Grok 2.0 upscale flag follows the opt-in policy #89935, fix(image-gen): Grok Imagine 2.0 no longer defaults upscale on — unbreaks main CI #89939, fix(image): keep grok upscale opt-in #89946, and this PR independently opened the same repair.
• WIP(mcp): dual-era hardening — bounded -32602 proof probe pending #88875 and feat(discord): outbound reaction actions for REST v10 #86419 currently carry the same one-line fix inside unrelated MCP and Discord branches to neutralize the shared-main failure; fix(gateway): canonical routing identity — claimant-generation object not published #89252 has already removed its temporary copy.
• The originating defect was a stale-green integration race: fix(image_gen): disable default-on upscaling — opt-in only #87883 merged the catalog-wide opt-in invariant after feat(image-gen): add Grok Imagine Image 2.0 to the FAL image catalog #87465's checks ran, then feat(image-gen): add Grok Imagine Image 2.0 to the FAL image catalog #87465 merged three days later without being tested against that newer base.

So the correct graph operation is: merge #89933 first, close the standalone duplicates, then rebase/drop the hitchhiking hunk from #88875 and #86419. The broader missing primitive is pre-open defect-class claiming/deduplication; post-hoc duplicate triage catches the fan-out only after the queue and attribution graph have already fractured.