shipped-probelisted

# Shipped probe `identity-probe` asks whether the version a server reports is *correct*. This asks whether it is *current*, and then whether it *runs*. A repository can be green, audited and entirely fixed while every `pip install` still hands out the broken release — nothing in CI contradicts that, because CI tests the branch, not the artifact. This absorbed the former `release-gap` skill. That question — is the published metadata consistent with the repository? — is now the **cheap depth** of this one, not a separate tool. Run: ```bash # metadata only: index + git. Two HTTP requests, no venv, no install. python scripts/shipped_probe.py --target <path> --metadata-only python scripts/shipped_probe.py --target <path> --offline # git-only, says so python scripts/shipped_probe.py --target <path> --max-age-days 14 # full: also install the distribution into a fresh venv and speak MCP to it. python scripts/shipped_probe.py --dist <name> --target <path> python scripts/shipped_probe.py --dist <name> --target <path> --tool health --format json # any PEP 503 index, as pip takes it python scripts/shipped_probe.py --target <path> --index-url https://pypi.example.com/simple # a re-check after a release: pin the version, or you re-check the one before it python scripts/shipped_probe.py --dist <name> --target <path> --pin-version 0.3.4 ``` `--dist` defaults to the `[project] name` in the target's `pyproject.toml`. Exit `0` clean, `2` **findings**, `127` the harness could n