feat(wasix): add first-class Bun and Deno support

[f0rr0]

Summary

• add first-class Bun and Deno entrypoints, storage adapters, worker/runtime selection, and package exports alongside Node
• keep both TypeScript SDKs npm-only and remove the repository's JSR manifests, publication machinery, readiness checks, fixtures, and documentation
• add Bun/Deno package checks, smoke coverage, CI planning, release metadata validation, and consumer documentation

Why

The portable WASIX TypeScript SDK had first-class browser and Node surfaces, but Bun and Deno depended on incidental Node compatibility and had no explicit runtime contracts. Both runtimes can consume npm packages directly, so a second JSR publication path adds release complexity without a distinct product capability.

Impact

Consumers get explicit Bun and Deno support from @oliphaunt/wasix-ts on npm. Deno uses npm:@oliphaunt/wasix-ts, matching the npm-only model for @oliphaunt/ts. Existing browser and Node exports remain supported.

Validation

• moon run sdk-contracts:check oliphaunt-js:package oliphaunt-wasix-ts:package (22 tasks passed)
• focused release/publication suite (104 tests passed)
• full release suite (1,034 passed, 10 platform skips); its sole stale carrier-count assertion was corrected and its focused regression suite passes (5 tests)
• workflow policy, extension model, and committed-asset checks
• git diff --check

Stack

This PR is intentionally based on #129 and should be reviewed/merged after that base PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
oliphaunt-docs	Ready	Preview	Aug 15, 2026 8:04pm