Accept complete lawpack closures in executable-operation provider inputs

[flyingrobots]

The executable-operation lowerer and verifier currently require exactly one lawpack bundle. Edict validates a complete dependency graph, but capability-denied provider components cannot discover dependency artifacts after invocation.

Extend the canonical provider input contract to carry the complete, ordered, digest-bound lawpack closure into both lowering and independent verification. Preserve application-neutral production code and exact-byte ownership.

Acceptance:

• lowerer and verifier accept a canonical complete lawpack closure;
• every dependency manifest, exports, adapter, and configuration is digest-bound;
• ordering and duplicate coordinates fail deterministically;
• existing singleton closures remain compatible;
• provider package artifacts are regenerated through owning generators.

[coderabbitai]

🔗 Related PRs

#672 - Implement Echo Edict provider lowerer [merged]
#673 - Implement the Echo Target IR semantic verifier [merged]
#674 - Assemble digest-locked Edict provider package [merged]
#675 - Generate Target-IR-bound Echo provider helpers [merged]
#677 - Prove Edict provider conformance and semantic parity [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!