[bug] status ignores --config and reports ok with empty runs while a run is active #46

Summary

meshloop status --config <file> --json ignores --config. Run from a directory with no meshloop.toml, it returns {"ok": true, … "runs": []} while a detached run is active. inspect --graph <id> --config <file> on the same graph works and shows nodes Running.

Version / OS

meshloop 0.3.0, origin/main @ 2769f08. Windows 11 native.

Reproduction

1. Put the config outside the repository (e.g. a scratch dir); no meshloop.toml in the repo root.
2. meshloop run --plan <plan> --config <cfg> --detach --json → status: running.
3. meshloop status --graph <id> --config <cfg> --json → ok: true, runs: [].
4. meshloop inspect --graph <id> --config <cfg> --json → node 1 Running.

Cause

cmd_status (crates/meshloop-cli/src/main.rs:926) calls crate::config::discover(None) and with_saga(None, None, …), so it never receives the parsed --config/--db. When discovery fails, it returns success with empty runs (lines 931–944), and does the same when resolve_graph_id fails (950–963). Both cases are reported as "no runs" instead of as errors.

Expected

• status honours --config and --db like inspect, cancel and review-plan.
• No config found, or an unknown --graph, gives a non-zero exit or ok: false with a reason, not ok: true with no runs.

Acceptance criteria

• Test: config outside cwd plus a detached run → status --config lists the run.
• Test: no config → error result naming the missing config.
• Test: unknown --graph → error naming the graph id.

🤖 Generated with Claude Code