v1.108.60 - config --check distinguishes sandbox-limited storage probes

config --check distinguishes sandbox-limited storage probes (#335)

The storage check creates the index root, writes a .jcm_probe file, and unlinks it. It previously treated every exception as a confirmed storage issue and exited 1. Inside a restricted/sandboxed agent shell that can read the index but cannot write to the index root, an EPERM/EACCES on the probe write made a perfectly healthy install look broken (✗ index storage not writable … Operation not permitted) — the false-failure an agent might try to "repair" or report.

Fixed

• A PermissionError whose errno is EPERM/EACCES is now classified as host-confirmation-needed: it prints ⚠ index storage writability needs host confirmation plus a hint to rerun outside a sandbox or restricted shell before repairing or reporting drift.
• When only host-confirmation items are present (no confirmed issues), the command exits 0 so an agent client does not mistake a healthy install for a broken one.
• Confirmed non-writable roots (e.g. a read-only filesystem, EROFS) still print ✗ index storage not writable and exit 1.
• 4 regression tests in tests/test_config.py (TestServerConfigCheckStorageProbe).

Reported by @mmashwani.

pip install -U jcodemunch-mcp