73 lines
3.0 KiB
Markdown
73 lines
3.0 KiB
Markdown
|
---
|
||
|
|
model: gpt-5.6-sol
|
||
|
|
service: opencode
|
||
|
|
session: f3a5eef0-9695-48ab-a336-861187473f8a
|
||
|
|
timestamp: 2026-08-31T02:23:17Z
|
||
|
|
git_ref: ng_tpts_planning
|
||
|
|
diff_cmd: git diff 768b531662a88037e3988885102d2ff24a7ce34e..HEAD
|
||
|
|
scope: code
|
||
|
|
substantive: true
|
||
|
|
raw_file: 20260831T022317Z_768b5316_prompt_io.raw.md
|
||
|
|
---
|
||
|
|
|
||
|
|
## Prompt
|
||
|
|
|
||
|
|
The human asked to continue the retained PR landing sequence and
|
||
|
|
selected "Repair all blockers" after a read-only review of PR #492.
|
||
|
|
They then corrected the TIPC assessment:
|
||
|
|
|
||
|
|
> oh one thing on the tipc findings, they may have already been
|
||
|
|
> addressed in the downstream patch branch no?
|
||
|
|
|
||
|
|
The repair therefore had to use downstream #493 as implementation
|
||
|
|
evidence, avoid duplicating solved TIPC work, preserve the dirty
|
||
|
|
downstream worktree, and repair the remaining shared, QUIC,
|
||
|
|
WireGuard, lock, and provenance defects without committing,
|
||
|
|
pushing, or publishing.
|
||
|
|
|
||
|
|
## Response summary
|
||
|
|
|
||
|
|
Reworked PR #492's plans and executable WireGuard example into a
|
||
|
|
consistent landing candidate. The shared and TIPC documents now
|
||
|
|
match current runtime/downstream behavior while naming remaining
|
||
|
|
risks. The QUIC plan now defines transport ownership across the
|
||
|
|
whole actor lifecycle. The WireGuard example validates keys and
|
||
|
|
binds both hosts and the service actor correctly without elevating
|
||
|
|
Tractor. The dependency lock and historical provenance pointers
|
||
|
|
are synchronized.
|
||
|
|
|
||
|
|
## Files changed
|
||
|
|
|
||
|
|
- `ai/tpt-backends/00_shared_backend_contract.md` - current backend
|
||
|
|
contract, dispatch, capability, and locality rules.
|
||
|
|
- `ai/tpt-backends/01_tipc_backend.md` - #493 reconciliation and
|
||
|
|
bounded unresolved work.
|
||
|
|
- `ai/tpt-backends/02_quic_iroh_backend.md` - lifecycle-safe QUIC
|
||
|
|
and UniFFI implementation plan.
|
||
|
|
- `ai/tpt-backends/03_wg_tunnel_bindspace.md` - corrected address
|
||
|
|
registry and privilege semantics.
|
||
|
|
- `ai/tpt-backends/README.md` - refreshed plan summaries.
|
||
|
|
- `examples/multihost/wg_lan/README.md` - unprivileged two-host
|
||
|
|
setup and accurate verification limits.
|
||
|
|
- `examples/multihost/wg_lan/host_a_srv.py` - local key check,
|
||
|
|
overlay child bind, and stable RPC exposure.
|
||
|
|
- `examples/multihost/wg_lan/host_b_client.py` - peer key check,
|
||
|
|
host-B bind, and explicit missing-service failure.
|
||
|
|
- `examples/multihost/wg_lan/wg_maddr.py` - strict parsing and
|
||
|
|
asynchronous role-specific key inspection.
|
||
|
|
- `uv.lock` - exact `py-multiaddr` Git source resolution.
|
||
|
|
- `ai/prompt-io/claude/20260813T001102Z_27c34aeb_prompt_io.md` -
|
||
|
|
valid scope and immutable Git reference.
|
||
|
|
- `ai/prompt-io/claude/20260813T001102Z_27c34aeb_prompt_io.raw.md`
|
||
|
|
- immutable historical diff pointers.
|
||
|
|
|
||
|
|
## Human edits
|
||
|
|
|
||
|
|
The human chose the full repair path rather than reducing the PR
|
||
|
|
to planning documents or publishing the initial review. They also
|
||
|
|
identified that the initial TIPC review had not accounted for the
|
||
|
|
downstream implementation branch. That correction materially
|
||
|
|
changed the work: solved TIPC items were backported into the plan,
|
||
|
|
remaining defects were separated from implemented behavior, and
|
||
|
|
the dirty downstream worktree was kept read-only.
|