Follow-up: multiaddr_support (PR #429)

[goodboy]

Follow-up from multiaddr_support (PR #429)

Tracking items identified during the
multiaddr_support PR.

• Support tunnelled multiaddrs
  for composed protocol stack connections, e.g.
  /ip4/10.0.0.1/udp/666/ip4/192.168.0.13/tcp/80.
  The runtime should reconstruct layered tpt protos
  per sub-actor Address and bind all necessary
  endpoints from a single multiaddr input.

• Get wireguard protocol support into upstream
  py-multiaddr per
  multiformats/py-multiaddr#107.
  Currently no wg proto exists in the multiaddr
  spec — this needs to be proposed and patched
  upstream before tractor can express
  WG-tunnelled actor connections as multiaddrs.

  • First-draft PR opened:
    multiformats/py-multiaddr#108.

• Revisit Multiaddr|str return type on
  MsgTransport.maddr — standardize on returning
  Multiaddr everywhere once py-multiaddr has
  better unix path support; see Copilot review
  discussion on PR Multiaddresses: a novel libp2p peep's idea worth embracing #429.

• Update wrap_address() docstring to document
  the multiaddr str input path (leading-/
  dispatch).

---

(this tracking issue was generated in some part by claude-code)