openclaw - 💡(How to fix) Fix doctor: 'Multiple state directories' check is noisy on multi-user hosts [1 participants]

Problem

On a host that legitimately runs OpenClaw as multiple Unix users (e.g. separate user accounts for separate agents on a single Mac Mini), `openclaw doctor` walking `/Users/*/.openclaw` reports every sibling user's state directory as a potential split-history concern:

``` ◇ State integrity │ - Multiple state directories detected. This can split session history. │ - /Users/colette/.openclaw │ - /Users/mark/.openclaw │ Active state dir: ~/.openclaw ```

Example: running as `gaston`, doctor reports both colette's and mark's home dirs even though those belong to completely separate users with completely separate agents. There is no actual split-history risk — the dirs belong to different OS users.

Proposal

One of:

1. Ownership filter: only report sibling dirs when they are readable by the current user. Dirs owned by another `/Users/<user>` with `700` perms almost certainly belong to a different agent.
2. Opt-in scope flag: `openclaw doctor --scope=home` to restrict to the current user's `$HOME/.openclaw` and skip the multi-home walk entirely.
3. Suppression config: `doctor.ignoreStateDirs: ["/Users/colette", "/Users/mark"]` in openclaw.json to silence known-intentional sibling dirs.

Option 1 is probably the lowest-friction default.

Impact

Cosmetic. The warning is noise on multi-agent hosts; the actual state-split risk is zero when dirs belong to separate POSIX users. It pollutes `doctor` output enough that it drowns real findings when scripted (e.g. health-check reports).

Repro

• Mac host running two OpenClaw agents as two separate users (`gaston`, `colette`).
• `ssh gaston@host 'openclaw doctor'` → warns about colette's dir even though gaston can't access it.