Run compiler-produced Hello Echo through scheduler-owned Ticks

[flyingrobots]

Claim

Echo's existing cargo xtask hello-echo demo registers native Rust matcher, executor, and footprint callbacks. Replace that application behavior with the exact package emitted from the standalone Edict examples.hello_echo@1.createGreeting source tracked by flyingrobots/edict#169.

Echo remains the only native runtime code. The application action, effect, obstruction, and package semantics originate in Edict and the Echo-owned provider artifacts; no application callback or handwritten executable package remains in the demo.

Acceptance criteria

• The demo consumes exact compiler-produced ExecutableOperationPackageV1 bytes and a structurally separate verifier report from Compile standalone Hello Echo through the provider boundary edict#169.
• Echo installs the package and submits a canonical executable-operation Action through the WAL-backed application boundary.
• Submission acknowledgement occurs only after accepted-submission WAL commit.
• The scheduler selects and privately evaluates the Action inside Tick construction.
• One atomic decided Tick is committed to the WAL before state, frontier, outcome, or Receipt publication.
• A fresh filesystem-backed host recovers the installed package, pending or decided Action, Tick, greeting state, typed outcome, and Receipt.
• createGreeting succeeds exactly once for an absent greeting.
• Repeating the same greeting creation produces typed AlreadyExists/precondition obstruction evidence and no hidden mutation.
• A mutated pre-Tick initial state causes recovery refusal.
• The demo contains no GraphQL dependency, fake transport, native application matcher/executor/footprint callback, or handwritten package builder.
• The existing native counter demo is removed or explicitly renamed as a low-level runtime diagnostic; it no longer claims to be the application-level Hello Echo path.

Test shape

The end-to-end witness must begin with the exact .edict source and lawpack closure, consume compiler/provider outputs without reconstructing them, execute through the scheduler-owned Action route, restart, and assert the recovered semantic result and Receipt.

Dependency

Blocked by flyingrobots/edict#169.

Non-goals

• Graft domain modeling.
• git-warp migration.
• Arbitrary multi-record programs.
• Reopening provider-v1 callback semantics.
• Direct prepare_echo_operation_v1 / commit_prepared_echo_operation_v1 application use; issue Remove transitional direct executable-operation prepare/commit seams #689 removes those transitional seams separately.

[coderabbitai]

🔗 Related PRs

#529 - Add Hello Echo demo and docs lifecycle policy [merged]
#672 - Implement Echo Edict provider lowerer [merged]
#673 - Implement the Echo Target IR semantic verifier [merged]
#683 - Execute admitted data-only operations in Echo [merged]
#688 - Route executable-operation Actions through scheduler-owned Ticks [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!