26 lines
938 B
Markdown
26 lines
938 B
Markdown
|
|
---
|
||
|
|
model: gpt-5.6-sol
|
||
|
|
service: opencode
|
||
|
|
timestamp: 2026-08-19T21:31:44Z
|
||
|
|
git_ref: f81fc5e5
|
||
|
|
diff_cmd: git diff HEAD~1..HEAD
|
||
|
|
---
|
||
|
|
|
||
|
|
# Raw output - outbound tunnel boundary
|
||
|
|
|
||
|
|
The human requested the next tunnelled-address slice using the same
|
||
|
|
per-step commit-plan flow. Existing design decisions require retaining
|
||
|
|
tunnel metadata until the narrow IPC transport boundary and never
|
||
|
|
teaching exact-type transport tables about tunnel wrappers.
|
||
|
|
|
||
|
|
> `git diff HEAD~1..HEAD -- tractor/ipc/_chan.py tests/ipc/test_channel_tunnel_boundary.py`
|
||
|
|
|
||
|
|
Extended channel address inputs to accept tunnel declarations, then
|
||
|
|
called `strip_tunnels()` immediately before exact-type transport lookup
|
||
|
|
and `connect_to()`. Added plain/tunnel parameterized coverage proving
|
||
|
|
both operations receive the identical TCP overlay while the original
|
||
|
|
wrapper retains its tunnel spec.
|
||
|
|
|
||
|
|
Verification included focused IPC tests, Ruff, discovery/IPC suites,
|
||
|
|
and the full tractor suite.
|