You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TypeScript modules remain the easiest authoring path. Without an explicit
portability floor, important features may stay trapped in Node-only modules and
never prove the WASM or Rust-host story.
Hill
New cross-host capability families prove a WASM fixture or explicitly declare
themselves Node-only.
Done looks like
capability metadata includes execution mode such as typescript-node, wasm, rust-native, or wasm-or-native
docs mark TypeScript modules as Node-hosted unless compiled to WASM
module-load and capability execution reports show execution mode
cross-host capability families require at least one WASM fixture before being
called portable
Node-only capabilities remain allowed but cannot be mistaken for portable
module truth
Execution mode and portability floor metadata now live in Rust. Hermetic
fixture checks prove that portable capability outputs must agree across
Rust-native, WASM, and external-process hosts for the same input digest.
Browser, Bun, and Deno host packages are explicitly external host experiments,
not proof of portable compiler truth. The Node host package has been retired,
so future Node execution evidence must arrive through a new, explicit adapter
design rather than the deleted legacy host.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.
docs/method/backlog/up-next/RUNTIME_capability-portability-floor.mdup-nextlane:asapRUNTIMEOriginal Local Backlog Card
Capability portability floor
up-nextRUNTIMEWhy now
TypeScript modules remain the easiest authoring path. Without an explicit
portability floor, important features may stay trapped in Node-only modules and
never prove the WASM or Rust-host story.
Hill
New cross-host capability families prove a WASM fixture or explicitly declare
themselves Node-only.
Done looks like
typescript-node,wasm,rust-native, orwasm-or-nativecalled portable
module truth
Repo Evidence
docs/design/0009-rust-core-and-wasm-capability-abi/rust-core-and-wasm-capability-abi.mddocs/design/0017-rust-native-front-door-and-node-retirement/HOST_COMPATIBILITY_BOUNDARY.mdcrates/wesley-core/src/domain/capability.rscrates/wesley-core/tests/module_capability_registry.rsdocs/method/backlog/cool-ideas/DX_inspect-module-capabilities-command.mddocs/method/backlog/cool-ideas/DX_module-authoring-and-loading-guide.mdCurrent Slice Status
Execution mode and portability floor metadata now live in Rust. Hermetic
fixture checks prove that portable capability outputs must agree across
Rust-native, WASM, and external-process hosts for the same input digest.
Browser, Bun, and Deno host packages are explicitly external host experiments,
not proof of portable compiler truth. The Node host package has been retired,
so future Node execution evidence must arrive through a new, explicit adapter
design rather than the deleted legacy host.