Fixes
cozempic reload --session — escape hatch for multi-agent sessions
User reported a real failure: in a multi-agent session (@main @dev-1 @dev-2 @dev-2-2 on darkchain-codebase-audit), auto-prune fired at 75% context and tried cozempic reload -rx aggressive. Session auto-detection couldn't disambiguate (strict mode, correctly), then the assistant hallucinated a retry with a positional UUID — which argparse rejected because reload had no --session flag (unlike guard).
Both attempts failed and the user was stuck at 75% with no pruning.
Fix: cozempic reload now accepts --session <uuid|prefix|path>. Matches the existing guard --session. The error message now names the flag instead of vaguely saying "use an explicit session ID".
Auto-update: clearer success message
After a successful pip install --upgrade cozempic, the currently running Python process still executes the old code — so --version prints the old number. Multiple users have reported thinking "cozempic was not really doing its job" because of this.
Fix: success message now says updated to v1.7.1 — active on next run (this process still v1.7.0) so the transition is explicit.
Tests
332 passing (+4 for `--session` flag parsing).