SuavePlan/suaveplan
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial Commit

Browse Source
This commit is contained in:
admin
2026-05-27 23:29:53 +01:00
commit fbc70f96e6
10000 changed files with 1102152 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
openspec/archive/2026-05-12-network-transport-trystero/DECISION.md Normal file
View File

@@ -0,0 +1,22 @@
# Decision: FOLD into `network-discovery-trystero` (not split)
- **Date**: 2026-05-12
- **Decided by**: autonomous Wave 3.3 implementation
- **Parent**: `network-transport-family` proposal, §"Split vs. fold" for discovery-bundled transports
## Outcome
`@suaveplan/network-transport-trystero` is NOT shipped as a separate package. Its functionality lives at `@suaveplan/network-discovery-trystero/transport` (subpath export of the existing discovery package).
## Rationale
1. Upstream code bundles transport + discovery as one integrated unit; the existing four-transport adapter pattern inside the discovery package already provides the multi-wire machinery.
2. Splitting would extract working integrated code into two packages with no functional gain.
3. Fold preserves upstream parity, shares the four-transport selection cleanly, and ships an actual usable transport in ~3× less effort.
## What to import
- Discovery: `import { TrysteroDiscovery } from "@suaveplan/network-discovery-trystero"`
- Transport: `import { TrysteroNodeTransport, TrysteroPlugin } from "@suaveplan/network-discovery-trystero/transport"` (or `/plugin`)
Note: the class is named `TrysteroNodeTransport` (not `TrysteroTransport`) to avoid collision with the existing `TrysteroTransport` string-union type (`"torrent" | "nostr" | "mqtt" | "ipfs"`) in the discovery package.