Generate Target-IR-bound Echo registration and invocation helpers #656
Description
Activity
- added
on Jul 13, 2026 🔗 Related PRs
#365 - feat(wesley): emit query observer host helpers [merged]
#671 - feat(echo-wesley-gen): generate canonical Edict provider artifacts [merged]
#672 - Implement Echo Edict provider lowerer [merged]
#673 - Implement the Echo Target IR semantic verifier [merged]
#674 - Assemble digest-locked Edict provider package [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand 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!
- added a parent issue
on Jul 13, 2026 - moved this from Todo to In Progress in Continuum Stack Convergence
on Jul 17, 2026 - moved this from In Progress to Done in Continuum Stack Convergence
on Jul 17, 2026
Purpose
Generate the first Echo-owned Rust/API helpers carried as provider output roles, bound to the exact Target IR and contract bundle identities rather than to mutable application names.
Acceptance criteria
Runtime installation boundary
This goalpost ends at a pure, opaque provider proposal. The proposal is not an
InstalledContractPackage, does not implement the legacy GraphQL/WesleyRegistryProviderfacade, and grants no artifact admission, installation, scheduling, execution, durability, receipt, or observation authority.A trusted Echo runtime must independently authenticate/select the callback implementation and consume the proposal during native provider admission. Equality between generated and host-claimed implementation identities proves cross-binding only; it does not prove arbitrary callback semantics. Native admission/invocation remains tracked by #583, with the end-to-end Jedit execution gate in #589.
Prerequisites #652 and #653 are complete.
Parent: #650
Downstream app-safe delivery remains tracked by #516.