piker/ai/prompt-io/opencode/20260820T163519Z_5f631e19_p...

1.4 KiB
Raw Blame History

Prompt

The human asked to implement the Piker compatibility work caused by tractors canonical tagged-address migration, run the previously deferred tractor verification, and keep runtime-managed WireGuard bindspaces in a later separate PR.

Response summary

Made Piker normalize legacy and tagged registry inputs before semantic comparison and process-global storage. Updated runtime address typing and test assertions for canonical output, retained legacy caller input, and removed a duplicate pytest log-level option that blocked downstream test collection with current tractor.

Files changed

  • piker/service/_registry.py - canonical registry normalization and shared address typing.
  • piker/service/_actor_runtime.py - tagged-compatible runtime API annotations.
  • tests/conftest.py - canonical fixture comparison and shared pytest option ownership.
  • tests/test_services.py - registry regression and canonical runtime assertions.

Human edits

The human explicitly requested the downstream implementation and chose to keep WireGuard bindspace lifecycle work in a separate future tractor PR. The agent implemented and tested those directions; no direct manual source edits were observed.