Summary

Fixes #1534.

doctor's stale_locks check hard-coded gbrain sync --break-lock as the recovery hint for every stale row. But that command, per sync.ts, only handles gbrain-sync:* keys — it silently no-ops on gbrain-cycle (and per-source gbrain-cycle:<source>) locks with Lock gbrain-sync:default is not held (nothing to break)., leaving operators with no shipped path to clear the lock.

Fix

Extracted a small formatStaleLockBreakHint(lockId) helper that branches on the lock-id prefix:

• gbrain-sync:<src> → gbrain sync --break-lock --source <src>
• gbrain-sync → gbrain sync --break-lock
• anything else (notably gbrain-cycle, gbrain-cycle:<src>, future kinds) → an honest SQL-fallback hint:
  manual clear required (no CLI breaker for <id>): DELETE FROM gbrain_cycle_locks WHERE id = '<id>';

The id is single-quote-escaped so the printed snippet is safe to copy verbatim.

Why this shape instead of shipping a new CLI breaker

The issue suggests also adding gbrain dream --break-lock or gbrain admin break-lock <name>. That's the right next step but it's a CLI-surface decision (PID liveness, force-break semantics, cross-host guards) that's better landed on its own with proper tests. This PR is the minimum honest-hint change so that doctor stops actively misleading operators today.

Risk

Pure formatter change inside the doctor output builder. No DB writes, no new CLI surface, no behavior change for the existing gbrain-sync:* cases. Output text changes for cycle locks only.

Test plan

No unit tests target this string today. Verified the helper output by extracting it into a Node REPL (covers sync, sync-with-source, cycle, cycle-with-source, and single-quote-in-id):

gbrain sync --break-lock --source default
gbrain sync --break-lock
manual clear required (no CLI breaker for gbrain-cycle): DELETE FROM gbrain_cycle_locks WHERE id = 'gbrain-cycle';
manual clear required (no CLI breaker for gbrain-cycle:notes): DELETE FROM gbrain_cycle_locks WHERE id = 'gbrain-cycle:notes';
manual clear required (no CLI breaker for weird's-lock): DELETE FROM gbrain_cycle_locks WHERE id = 'weird''s-lock';

Did not run the full bun test / bun run verify suite locally (no Postgres + Bun on this machine); CI will cover.