runtime: deliver the path hand-written adapters use, so bitsystem3 can leave nightseam.

[jm9e]

Current delivery and remaining closure gates — 2026-09-26

PR9 merged as e28bb1adefbc8a5cb1b03f172b4e7212584bd7a2 and v0.2.0 is published. Its former conditional closing phrase auto-closed this issue at merge; this issue is reopened because its existing independent released-artifact and actual consumer gates remain.

• Runtime source and v0.2.0 release: Go source tag and @bitspark/bitruntime TypeScript release tarball. The tarball SHA-256 is d19d377ad60037083b3158a7200f734e8bb37b17e7d1f7f7c2cd15e0ff2fb9d1; npm registry publication is not claimed.
• bitwire PR52 consumes the released version, adds TypeScript drivers and passes the independent local/WebSocket cases in both languages. Candidate-only green checks do not satisfy this gate.
• bitsystem3 #7 lands its actual Go/TS migration using released artifacts and passes browser/CLI/Docker/persistence acceptance with no nightseam dependencies.
• Attach final contract, protocol, suite and implementation identities plus links to independent and consumer runs; then close this issue manually.

There is no dependency cycle: the runtime release is already available; independent released acceptance and consumer migration can run in parallel, with both required for this issue's closure. Later full-tree application mapping is bitsystem3 #11. Later streams, tunnels, live references, wider lifecycle integration and received context are separately owned in #2 and do not become automatic blockers on this bounded milestone.

The original scope and acceptance below remain as the historical task definition. References to what bitsystem3 uses describe the pre-migration baseline, not the newly published runtime.

---

The first milestone in the charter is to move bitsystem3 off Nightseam, the first gate in Bitwire decision 0010's migration order.

Approved primitive and tree contract (2026-09-26)

• Data.read() -> Bytes and addressless Wire.send(message) are the primitives. Reads are asynchronous in TypeScript.
• DataTree = DeixisNode<Data> and WireTree = DeixisNode<Wire> have the same full structural contract: own value, complete children under exact byte keys, partial selection, decomposition and recomposition.
• At an existing path, read(tree, p) = select(tree, p).own().read() and send(tree, p, m) = select(tree, p).own().send(m).
• Opaque send(path, message) is the explicitly named AddressedWire compatibility bridge. It is not a WireTree; prefix binding alone cannot establish existence, enumerate children or reconstruct a tree.

The interaction contract is owned by Bitwire #42, with shared structure owned by Deixis #49. Breaking native names do not silently revise the bitwire/1 protocol.

What bitsystem3 uses today

Nightseam v0.6.0 and Bitwire v0.2.0, through hand-written adapters and no generated code: duplex.At, runtime.CallWire, HandleWire, EmitWire, NewDispatcher, NewWirePair and Dial, in Go and TypeScript. Its historical Wire is addressed access. bitsystem3 #10 documents the unchanged installed release boundary.

Scope, Go and TypeScript

• core: full structural WireTree operations and the derived primitive send; explicitly separate legacy prefix selection/mounting/forwarding over AddressedWire, invocation lifecycle and the in-process pair.
• transports: the frame transport interface, the in-memory pipe, WebSocket.
• engine: the protocol engine (bitwire/1, byte for byte the v0.6.0 profile) and connection setup (dial and accept).
• dispatch: the dispatcher and request/response and event helpers, with their required access capability explicit.
• independent changes: received-context evidence and protocol revision-2 negotiation need their own accepted contracts, implementation and tests. Do not assume they ship merely because the native API is versioned Bitwire 0.3.0.

Acceptance

• Port each piece from an identified Nightseam commit, keeping v0.6.0 apart from its unreleased commits, with provenance in NOTICE and no Nightseam compatibility aliases.
• Preserve exact byte keys, branching-node own values, empty versus missing paths, complete reconstruction and retained interaction state for true trees. Test missing children separately from present children whose primitive refuses.
• Bitwire's independent cases pass against released bitruntime artifacts, run from a test-only module in Bitwire, over the in-process pair and WebSocket in both directions.
• A bitruntime peer interoperates with a Nightseam v0.6.0 peer through the explicit addressed compatibility boundary.
• Nightseam's recorded defects in these pieces are fixed, not ported: nightseam #722, the dropped refusals when a pair closes.
• bitsystem3 builds and passes its complete tests on released bitruntime packages, with no Nightseam dependency left. Retaining an honestly named AddressedWire bridge does not claim completion of structural-tree adoption.

This issue remains open for runtime and consumer delivery; contract naming, documentation, runtime code, package release and consumer migration are separate evidence.

[jm9e]

Closing: every gate above has passed.

Gate	Evidence
Runtime release	v0.2.0, annotated tag at e28bb1adefbc8a5cb1b03f172b4e7212584bd7a2 (PR #9). Go module github.com/Bitspark/bitruntime v0.2.0 (h1:6sSEqVB9sRzxZPLcVcca9RtfRNYy+8+E5dvVmDpyFbQ=). TypeScript @bitspark/bitruntime 0.2.0 release asset, sha256 d19d377ad60037083b3158a7200f734e8bb37b17e7d1f7f7c2cd15e0ff2fb9d1. Release workflow run 36238029717. Fresh consumers pass from the public URLs: scripts/go-smoke.mjs v0.2.0, and a tarball install under npm 11.3.0 and 12.1.0. npm 12 needs allow-remote=root, documented in #17.
Independent acceptance	Bitspark/bitwire#52, merged f42d82c, against both released halves; contract v0.3.0 at f825f3f, protocol bitwire/1. Go and TS each: lifecycle 5/5, composition 6/6 ×3, declared reference 39/39 ×3, production 20 + 19 recorded gaps ×3, trees 14/14, over the local pair and WebSocket in both directions.
nightseam v0.6.0 interop	scripts/interop.mjs (CI job interop): all 16 Go/TS × bitruntime/nightseam client/server pairings pass the scenario, and each bitruntime server's transcript equals nightseam's byte for byte.
Consumer migration	Bitspark/bitsystem3#13, merged 46279d5c57104e146787d2cdd5d7a67cb783c567, closes bitsystem3#7. No nightseam in go.mod, go.sum or package-lock.json. Evidence: go test -race, go vet, npm run check, npm run build, Docker e2e 3/3 and the persistence smoke, locally and in CI; the CLI's snapshot, watch, create, fact and remove-fact against an isolated stack.
Recorded defects	nightseam#722's queued refusals and nightseam#658 are fixed, with regression tests. So are R26 (one closed classification) and R27 (observe-only codes never sent). Details in docs/port-from-nightseam.md.

Not claimed here, and owned elsewhere:

• received-context/observation hooks (engine: implement accepted received-context and observation hooks #14, after bitwire#55);
• full-tree composition and the 19 historical addressed gaps (core: verify full WireTree composition across carrier access and disposition legacy gaps #15 / bitwire#29);
• streams (transports: implement bitwire-stream/1 over stdio, TCP and Unix sockets #10), tunnels (tunnel: implement scoped channels with independent authority and close lifetimes #11), live references (live: implement bounded reference ownership, scopes and release #12), lifecycle integration rows (lifecycle: finish independent capture, body and retirement acceptance across integrations #13) and auth integration (auth-integration: replace reusable wire-auth adapter dependencies through public hooks #16);
• full space/WireTree mapping in bitsystem3 (bitsystem3#11).