ClickHouse Performance Optimization

Seven stages, run sequentially: SETUP → PROFILE → PROPOSE → BASELINE → EXPERIMENT → COMPARE → SHIP. Complete each stage fully before moving to the next. Use conversation context as state.

Inside Stage 4, start the baseline deployment and all approved candidate deployments in parallel. Do not wait for the baseline preview deployment before creating candidate branches from the local perf/baseline commit.

If the user provided a project slug as an argument, skip the project selection prompt in Stage 1.

Command safety

Guardrailed (run freely): 514 agent auth whoami, 514 agent project list, 514 agent deployment list, 514 agent deployment wait, 514 agent table list, 514 agent materialized-view list, 514 agent sql-resource list, 514 agent metrics query, 514 logs query, 514 clickhouse query, moose add benchmark, moose dev, moose ls, pnpm env:preview, pnpm bench

Require user approval before running:

• 514 env list --platform --dotenv — emits platform secrets; pipe directly to .env.*, not for inspection
• Any 514 clickhouse seed — copies rows from a source branch into a preview branch

Use AskUserQuestion to show the exact command and get explicit approval for approval-gated commands. Never show a template with unresolved placeholders.