suaveplan/openspec/archive/2026-05-12-network-transport-webtorrent/DECISION.md

Decision: FOLD into network-discovery-webtorrent (not split)

• Date: 2026-05-12
• Decided by: autonomous Wave 3.4 implementation
• Parent: network-transport-family proposal, §"Split vs. fold" for discovery-bundled transports

Outcome

@suaveplan/network-transport-webtorrent is NOT shipped as a separate package. Its functionality lives at @suaveplan/network-discovery-webtorrent/transport (subpath export of the existing discovery package).

Rationale

1. Upstream code bundles transport + discovery as one integrated unit; the existing P2PT data-channel lifecycle inside WebTorrentDiscovery IS the transport machinery.
2. Splitting would extract working integrated code into two packages with no functional gain.
3. Fold preserves upstream parity and ships an actual usable transport in ~3× less effort.

What to import

• Discovery: import { WebTorrentDiscovery } from "@suaveplan/network-discovery-webtorrent"
• Transport: import { WebTorrentTransport, WebTorrentPlugin } from "@suaveplan/network-discovery-webtorrent/transport" (or /plugin)