Preserve typed obstruction identity in executable operation packages

[flyingrobots]

Outcome

Preserve the application-authored obstruction identity through generic Edict-to-Echo lowering, independent verification, executable-package admission, and the external runner witness.

Executable claim

A compiler-produced create-if-absent package lowered from an authored obstruction arm retains that exact obstruction coordinate. Duplicate execution reports the retained coordinate while Echo production code remains application-neutral.

Acceptance criteria

• Lowering emits a canonical package field binding the authored obstruction coordinate.
• The structurally separate verifier derives and checks the same field from real Core and Target IR closure.
• Package admission rejects missing, malformed, or substituted obstruction identities.
• The generic runner reports the package-declared obstruction when the runtime returns the corresponding generic precondition obstruction.
• Generic fixtures prove at least two distinct application-owned obstruction coordinates.
• The checked provider package is regenerated only through its owning generators and embeds the updated lowerer and verifier.
• Production modules contain no Hello Echo, Graft, or other application vocabulary.

RED witness

cargo test -p echo-edict-provider-lowerer --test executable_operation_package

cargo test -p echo-edict-provider-verifier --test executable_operation_package

cargo test -p xtask --test run_edict_operation

Non-goals

No native application callback, application-specific runner branch, handwritten package, provider import, external-effect protocol, or multi-Action Tick claim.

[coderabbitai]

🔗 Related PRs

#672 - Implement Echo Edict provider lowerer [merged]
#673 - Implement the Echo Target IR semantic verifier [merged]
#677 - Prove Edict provider conformance and semantic parity [merged]
#683 - Execute admitted data-only operations in Echo [merged]
#695 - Run compiler-produced Edict operations through durable Ticks [open]

---

📝 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!