Review — structured logger migration in steps.ts

Clean, well-targeted change. The level mapping is the right fix: info is suppressed under the prod warn floor, so the console spam disappears in real sessions while staying visible in dev, and the structured context objects are a clear improvement over string concatenation. Verified the logger API (info/warn/errMessage) and the ../log.js ESM import path against the call sites — all correct.

One gap and two minor nits:

Important — one console.error is left behind (contradicts "Switched all logging").
readStepsFile at electron/ipc/steps.ts:80 still does:

console.error('[steps] Failed to read steps file:', e);

This is the one genuine error path in the file (corrupt/unreadable steps.json, non-ENOENT), and it's exactly what log.ts's error(category, msg, err, ctx) exists for — it also captures the stack. Suggest:

import { error as logError, info as logInfo, warn as logWarn, errMessage } from '../log.js';
// ...
logError('steps', 'failed to read steps file', e);

Minor — watch event logs before the filename filter.
At steps.ts:160, the logInfo('steps', 'watch event', …) fires for every file change in .claude/, not just steps.json (the filename \!== 'steps.json' early-return is on the next line). It's the highest-frequency log here, so debug reads as more honest than info — relevant if a user lowers the floor to info via the renderer's level_min, which would re-introduce spam one level down. No-op under the current prod/dev floors, so purely a level-choice nuance.

Minor — stack traces dropped for watch-setup failures.
errMessage(err) keeps only err.message. For failed to watch worktree root / failed to watch steps dir (steps.ts:194,220), the failure silently disables live step updates for that task. The old console.warn(msg, err) printed the full Error incl. stack; consider error level here so the logger captures the stack for the cases that actually break the feature. Fine to keep as warn if these are treated as recoverable.

Otherwise good to merge.

_{🤖 Automated review via Claude Code}

Thanks for the thorough review! Pushed a follow-up commit addressing all three points:

1. Remaining `console.error` — replaced with `logError' in `readStepsFile`. It now captures the full stack trace through the structured logger instead of just printing to stderr.

2. Watch-event `info` → `debug` — the `onChange` callback now logs at `debug` level, so it won't fire at all under the default `warn` floor. This is the highest-frequency log site in the file, so the level choice matters.

3. Watcher setup errors → `error` level — the three watcher error handlers (`parentWatcher.on('error', …)`, the `fs.watch` catch, and `attachStepsDirWatcher`'s catch/error) now use `logError` instead of `logWarn`. These failures silently disable live step updates, so the stack trace capture matters. The `errMessage()` wrapper is gone — `logError` already serialises and clips stacks internally.

All 1420 tests pass, typecheck + lint clean.

Thank you very much! <3