1.3 KiB
1.3 KiB
Prompt
The human requested completion of inbound runtime peeling using the same per-step implementation and commit-plan workflow.
Response summary
Preserved tunnel declarations through listener configuration, peeled them immediately before Endpoint construction, and used the overlay for backend-specific random listener allocation after registry discovery. Added a real listener regression for the reflection and exact-type boundary.
Files changed
tractor/ipc/_server.py- accept wrapper declarations and peel atEndpointconstruction.tractor/_root.py- allocate random transport addresses from the contacted registry’s overlay.tests/ipc/test_server_tunnel_boundary.py- verify a real listener stores only TCP while preserving the source annotation.
Human edits
The human selected the runtime-boundary work and previously corrected the architecture so tractor retains future bindspace provisioning ownership while Endpoint sees only application transports. The agent implemented and tested that direction; no direct manual source edits were observed during this step.