2.1 KiB
Prompt
The human asked to sanity-check the current PR94 landing state against the qualified new Tractor pin before deduplicating branch history. After the initial offline checks passed, the human authorized changing the selector to piker_pin, resolving the lock, and verifying the installed dependency without the temporary local-source PYTHONPATH override. The human explicitly authorized network resolution and a scoped update of Tractor/runtime dependencies while preserving unrelated packages.
Response summary
Updated the branch selector and lock to published piker_pin@b64c89f0. Installed the exact locked Tractor revision, verified its installed source metadata, and reran 14 offline logger/startup cases without a local Tractor source override. Preserved the rest of the environment.
Files changed
pyproject.toml: select piker_pin and bound Polars below 2.0.uv.lock: lock b64c89f0 and Polars/runtime 1.44.2.- This provenance pair.
Verification and limits
14 distinct offline cases passed against the installed Tractor update with the existing Polars 1.36 installation. The actor.uid deprecation warning remains. No live provider/order testing occurred.
The initial resolver selected Polars 2.0 and rejected retaining 1.36 for its Windows target. The human then requested the latest pre-2.0 release instead. PyPI metadata identified non-yanked stable 1.44.2; adding <2.0.0 to the existing lower bound and relocking succeeded with both polars and polars-runtime-32 at 1.44.2, without platform edits. The raw partner retains the original, superseded 2.0 generation history.
The scoped install changed only Tractor. Polars 1.44.2 is locked but not installed or data-path qualified yet. The human’s existing staged checkpoint is preserved; the pre-2.0 correction is in the worktree. No history cleanup, staging or commit was performed by this agent.