Native TypeScript open HTTP contacts and Agent runtime - #33
Merged
Conversation
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.
Native TypeScript can now join the explicit open profile, publish or discover signed contacts over constrained HTTP, and run an independent finite directory node. The existing Agent selects this native contact path from an open config. Python and TypeScript share the original client configuration, identities, transport SQLite schema and durable control/index formats.
Routing kernels, maintenance schedule and numeric budgets are unchanged. The transport validates every DNS answer, pins the socket destination, retains TLS hostname verification and bounds concurrent resolution, requests and incoming exchanges. Open messaging, first-contact consent and ciphertext repair remain pending; this targets the smaller
0.28.0-alpha.0.1preview and preserves the full alpha.1 milestone.Validation: 35 selected local methods passed, with no failures, errors or skips, including nine native HTTP tests, six native state tests, two retained private Agent HTTP tests and 18 packaging/core methods. Actual mixed-language tests cover seven synthetic HTTP node processes plus one native client, cold response-derived multihop lookup, original bootstrap exit, alternate-language restart, DNS/TLS refusal, pending capacity and unchanged existing memory/proofs. These are not real models, physical fault domains or a new scale experiment. Exact-source cloud CI now passes: 99-method open and direct-regression run and three-platform protocol run, both pinned to
0ddf0c5ac6aa8d12562c1df2a26ee25aeb851ed3. The complete light artifact was downloaded: 99 distinct methods passed, zero failures/errors/skips, and every recorded source hash matched Git. Artifact 10046978942, ZIP SHA25659b3d810026b08cbcad243aea5531953363f169a106144b927bcb0fb2b6552e4. Exact-source 6 Pro code and packaging review passed with zero blocking findings. The reviewer independently verified all 725 archive members and the final client package, and passed 18 packaging/core methods. Its environment did not execute 17 native/private methods; those are covered by the exact-source cloud run above. Final CI evidence review also passed: all 99 methods match the candidate method inventory and all 27 recorded source fingerprints match the reviewed source. No remaining delivery blockers were reported in the reviewed scope.Only generic implementation, public documentation and wholly synthetic fixtures are included. No private installation, credentials, Vault, invitations, public service or paid resources are changed. Preserve previously published releases and their bytes.