Add a dbt-optimizer agent: scan dbt projects for fixable issues with cost/impact reporting

docs/internal/2026-08-12-dbt-optimization-taxonomy-research.md から始め、その検出領域を Optimize ワークフローの背後にある予定の dbt-optimizer エージェントに対応付けます。読み取り専用スキャン、候補の選定、修正の適用、コスト/影響のレポート、および PR 出力を定義し、明記されている warehouse-write、equivalence、query-history の安全ゲートを維持します。指定されたエージェントが合意した範囲をカバーし、これらの要件を弱めていなければ完了です。

Feature

Add a new native primary agent, dbt-optimizer, that scans an existing dbt project for concrete, fixable issues and proposes targeted fixes with cost and impact reporting. This is the agent behind the planned Optimize workflow.

Input: an existing dbt project (connected repository and environment).
Output: candidates (detected issues), fixes for user-selected candidates, impact reports (batch effect incl. estimated cost change), and PRs for applied fixes.

Detection scope (from the dbt-optimization taxonomy research, docs/internal/2026-08-12-dbt-optimization-taxonomy-research.md):

• materialization & incremental processing (strategy-aware: merge / delete+insert / insert_overwrite / microbatch, precondition-gated)
• warehouse physical design (clustering / partitioning / sort keys, query-history gated)
• SQL anti-patterns, DAG economics (fan-out, duplicate scans, dead models), run-level orchestration (Slim CI, threads, full-refresh overuse), tests/docs/storage

Safety requirements: scan phase is read-only; warehouse writes denied non-overridably; SQL rewrites gated on decidable equivalence; cost claims only from attributed query-history evidence.

Named dbt-optimizer (not optimizer) because more optimizer agents are planned later.