Correct the kospex pin wording in CLAUDE.md

[sabbaticas]

CLAUDE.md described kospex's dependency on panopticas incorrectly, in a way that made release step 8 misleading.

What it said

Two places claimed an exact pin in kospex's pyproject.toml:

Update panopticas==X.Y.Z in kospex's pyproject.toml — kospex uses an exact pin, so a new release does not reach it until this is bumped. This step is mandatory, not conditional.

What is actually true

kospex pins panopticas in two files, differently:

File	Pin	Effect
pyproject.toml	panopticas>=0.0.19	floor — a PyPI install of kospex picks up a new release automatically
requirements.txt	panopticas==0.0.19	exact — development and deployment installs stay put until regenerated

The move to >= was deliberate, in kospex commit 527bcf3 — "deps: panopticas>=0.0.19, and regenerate requirements.txt" — which updated both files together. That is the pattern the docs should have described.

So the old wording was wrong about which file carries the exact pin, and wrong that a release cannot reach kospex without a bump — but right that something needs doing each release.

What changed

Release step 8 now says to read both files, and states which one actually needs updating every time:

• requirements.txt — regenerate for every release
• pyproject.toml — raise the floor only when kospex starts depending on something the new release added

The integration-points entry is corrected the same way, and keeps its self-correcting note, now recording both times it has gone stale: the earlier 0.0.16 claim, and this exact-pin claim. The instruction to read the files rather than trust any version quoted in CLAUDE.md stands.

Also verified

last_panopticas_version is still real — kospex_core.py reads and writes it, and it is declared in migration 0003_repos_sync_provenance.sql — so the re-sync bullet above it remains accurate.

🤖 Generated with Claude Code