feat(gateway): default Gateway image to hummingbot/gateway:development

[fengtality]

Summary

• Change the /gateway/start default image from hummingbot/gateway:latest to hummingbot/gateway:development.
• Meteora DAMM v2 support (the /gateway/amm/* routes backing GatewayAMMRouter in hummingbot-api-client 1.5.7) currently only ships in the development Gateway image — the published latest image has no AMM routes for Meteora, so starting Gateway with defaults produced a deployment that cannot serve DAMM v2 agents.

Test plan

• POST /gateway/start with an empty body → container comes up on hummingbot/gateway:development, /gateway/connectors reports meteora ['clmm', 'amm'].
• End-to-end: client.gateway_amm.get_pool_info() against a live Meteora DAMM v2 pool returns price/reserves.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

Changes the default Docker image used by POST /gateway/start from hummingbot/gateway:latest to hummingbot/gateway:development, enabling the Gateway AMM routes required for Meteora DAMM v2 when callers omit the image field.

• Updates GatewayConfig.image to select the development image by default.
• Preserves support for explicitly specifying another Gateway image.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or non-blocking defects identified.

The default is intentionally used by empty-body Gateway startup requests, while callers retain the ability to override the image, and no repository evidence establishes an incompatible contract or startup failure.

Important Files Changed

Filename	Overview
models/gateway.py	Updates the reachable Gateway startup default to the development image; no concrete defect is established by the change.

_{Reviews (1): Last reviewed commit: "feat(gateway): default Gateway image to ..." | Re-trigger Greptile}