🔴 Missing 'reasoning' tier in DEFAULT_CONFIG routing.tiers

[evansantos]

Context

During the ClawRouter integration (PR #2), GitSniff identified a config inconsistency between the Zod schema defaults and DEFAULT_CONFIG.

Problem

src/config.ts — The DEFAULT_CONFIG for routing.tiers defines simple, mid, and complex but omits reasoning. The SlimClawConfigSchema (Zod) correctly includes all 4 tiers with defaults.

This means if a user provides a partial routing config without tiers, the merged config will be missing reasoning, causing routing for reasoning-tier tasks to silently fail or fall through.

Expected Behavior

DEFAULT_CONFIG.routing.tiers should include all 4 tiers, matching the Zod schema:

tiers: {
  simple: "anthropic/claude-3-haiku-20240307",
  mid: "anthropic/claude-sonnet-4-20250514",
  complex: "anthropic/claude-opus-4-20250514",
  reasoning: "anthropic/claude-opus-4-20250514",  // ← missing
}

Files to Change

• src/config.ts — add reasoning tier to DEFAULT_CONFIG

How to Verify

npm test -- --grep "config"

Ensure the default config includes all 4 tiers when no user config is provided.

Background

SlimClaw uses a 4-tier complexity classification system: simple, mid, complex, reasoning. The HybridRouter routes requests to different models based on tier. Without reasoning in defaults, those requests get no tier model match → routing skipped.

Ref: PR #2 GitSniff review round 4

[evansantos]

Already fixed — both the Zod schema default and DEFAULT_CONFIG include reasoning tier. GitSniff was likely reviewing a cached version of the diff. Verified in src/config.ts lines 37-41 and 104-108.