Problem

When openclaw.json has an invalid enum value (e.g. tools.profile: "none"), the error message says:

agents.list.3.tools.profile: Invalid input (allowed: "minimal", "coding", "messaging", "full")

Three things make this hard to debug:

1. No line number — you can't grep or vim /none to find the offending value
2. No bad value shown — Zod's invalid_enum_value error already carries a received field (e.g. "none"), but it's silently dropped before formatting
3. Array index as dot-segment — agents.list.3 looks like a property path, not an array index. Should be agents.list[3]

Expected

openclaw.json:247 — agents.list[3].tools.profile: Invalid input, got: "none" (allowed: "minimal", "coding", "messaging", "full")

That's grep-able, tells you exactly what you set wrong, and points to the line.

Implementation sketch

• formatConfigPath() in src/config/validation.ts — use bracket notation for numeric segments
• mapZodIssueToConfigIssue() — read Zod's received field and append got: ${JSON.stringify(received)}
• runConfigValidate() in src/cli/config-cli.ts — walk the Zod error path against the raw file text (already available in ConfigFileSnapshot.raw) to find the line number

Related

• ConfigFileSnapshot already has raw: string | null — the full raw file text
• ConfigValidationIssue type in src/config/types.openclaw.ts — could add an optional line field