Files
pipdock/crates
poli0981andClaude Opus 5 779c1e8560 feat: complete the M1 command surface and close the milestone
Adds the last commands: env use, pip-upgrade, snapshot rollback, schema,
self report-bug, and engine <pip|uv>. Every P0 CLI command now works
except health, which belongs to M3 with the tools venv.

Rollback follows DATA-FLOW section 8 including the part that is easy to
skip: it snapshots the current state before replacing it, because a
rollback is itself reversible. Verified end to end — installing httpx
0.23.0 and rolling back left the environment with pip alone, and the diff
afterwards reported "matches snapshot".

Two things the compiler and the smoke test caught:

- `pipdock engine pip` was never handled. Only the no-argument form was
  wired, so the documented setter silently did not exist; the
  non-exhaustive match surfaced it once the catch-all arm was removed.
  That catch-all had been hiding it.
- engine_for ignored any stored preference and always returned pip, so
  configuring an engine would have had no effect. It now reads the store,
  and setting an unavailable engine is refused rather than saved —
  storing a preference that cannot be honoured just moves the failure to
  the next command.

schema generates from the Rust types via schemars rather than being
hand-written, because a hand-written schema drifts the moment a field is
added and then lies to every script pinning against it. A test asserts
every advertised type actually resolves.

ci-integration.yml implements TESTING L2: real pip and uv against
throwaway venvs on Windows, across the 3.10 floor and 3.14 ceiling, with
an end-to-end pass that checks the claims the docs make — the SP-1
conflict is still reported and attributed, update/rollback round-trips
leave the environment matching the snapshot, the guard still refuses to
break requests, and the exit codes still match CLI-SPEC section 5. A
weekly job re-captures fixtures against the newest engines so an output
change surfaces as a failed job rather than as PD-ENG-003 on a user's
machine.

The ROADMAP entry is honest about what is not done: L2 has never actually
run, the L4 golden-output tests are not written, and the SP-5 exit
criterion named a real numpy/scipy/pandas environment that the
httpx/httpcore construction stood in for.

173 tests, clippy -D warnings clean, npm audit clean, all workflows parse.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 20:26:05 +07:00
..