Repository navigation
Conversation
MichalCz
force-pushed
the
feat/native-bun-runner
branch
from
November 12, 2026 18:20
1f17f69 to
9f5fade
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tests-first implementation
The first commit adds tests before the runtime change. Against the previous implementation, the native-identity test failed because author code ran in a separate Node PID, and the unusable-NODE_BIN test failed because the runner tried to spawn Node. The independent Node behavior baseline passed.
The implementation and integration updates follow in separate commits. This PR is independent of #1152 and targets
develdirectly.Validation
Package and contract checks
npm run build:packages: passed.npm run check:typings-split: 4 passed.npm run check:runtime-invariants: 8 passed.The new tests cover author identity, unusable NODE_BIN, supported export shapes, multi-function chains, DataStream/StringStream/BufferStream output, args/context, declarations and initialization ordering, lifecycle/errors/exit artifacts, inherited-descriptor framing/EOF/cancellation/backpressure, and Agent-aware requests/streaming/abort.
Hosted BDD
All runs use the supported Docker BDD runner and report no leaked repository processes.
NO_HOST=true SCRAMJET_SPAWN_TS=1 node scripts/run-bdd.js --mode=docker -- features/appcontext/APPCONTEXT-002-hosted-runtimes.feature --name 'APPCONTEXT-002'3 scenarios / 86 steps passed: Python, Node, and native Bun. Exercises real Hub client routing, initialization-time declarations, logging, health, events, raw HTTP exposure, and author-side identity.
Each passed: 1 scenario / 18 steps. Both producer and consumer report the actual Bun executable/PID and the selected source or built runner entry. The exact loaded-package provenance checks remain intact; no Node sequence-runner process appears below Bun.
NO_HOST=true SCRAMJET_SPAWN_TS=1 node scripts/run-bdd.js --mode=docker -- features/api-router/hub-event-watch.feature --name 'REALCONTAINER native Bun observer'1 scenario / 18 steps passed: actual Bun 1.4.2 executes the observer, acquires/releases the watch, aborts the pending read, and completes the control probe successfully.
Boundaries and known baseline issues