WASM control intent authority boundary is too implicit

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/bad-code/wasm-control-intent-authority-boundary.md
Original lane: bad-code

Original backlog card

WASM control intent authority boundary is too implicit

Status: partially addressed. The immediate bug was fixed by making public
application dispatch reject CONTROL_INTENT_V1_OP_ID before the kernel can
run scheduler control. WarpKernel::dispatch_intent(...) also rejects the
reserved control op id directly, while trusted runtime control now uses a
separate TrustedKernelControlPort Rust host/runtime-owner path. The raw WASM
package now exposes dispatch_control_intent_trusted(...) for host adapters.

The remaining concern is product packaging and host architecture: browser
adapters must not hand untrusted application code a raw privileged runtime
owner. A worker or host adapter should own Echo's scheduler lifecycle and expose
only application-safe intent ingress plus observation APIs.

Fix direction:

• Keep generated Wesley helpers unable to produce scheduler control envelopes.
• Add browser/package integration tests proving untrusted application adapters
  cannot reach trusted runtime control.
• Document the worker/runtime-owner shape before publishing a high-level
  browser application package.

Acceptance criteria:

• Browser package APIs expose application-safe dispatch and observation only.
• Host/runtime control can start Echo deterministically without exposing the raw
  control path to application code.
• README, WASM ABI docs, and package docs describe the authority split
  consistently.

Current design packet:

• WASM Trusted Runtime Host Control Boundary

[coderabbitai]

🔗 Related PRs

#326 - Echo contract hosting roadmap [merged]
#330 - test(wasm): own package export smoke boundary [merged]
#353 - Fix WASM application intent authority boundary [merged]
#380 - feat(core): expose retained evidence posture on readings [merged]
#382 - 0024 universal LE binary codec + 0025 sessions design (design-only) [merged]

---

📝 Issue Planner

_{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!