Establish Echo's sealed public runtime boundary

[flyingrobots]

Goal

Establish a sealed Rust host facade and an authority-safe Cargo package boundary before a public alpha release.

Plan

• Add a publish-disabled flyingrobots-echo-runtime facade for construction and recovery.
• Prove construction and recovery without native rule bootstrap.
• Record protocol, kernel, WAL, and sealed-runtime ownership.
• Classify the facade as determinism-critical and regenerate package assets plus their provenance corpus.
• Add package-prefix, dependency-direction, feature-surface, and authority-escape guards.
• Extract the public package closure and prove it with a clean-room external host.

Current status

Construction/recovery and the canonical ownership policy are implemented. The crate remains publish = false, and warp-core remains an unpublished dependency. This PR targets #724's provider branch.

Review follow-up corrected the determinism classifier and stale generated Cargo assets. Regeneration also updates provenance/review evidence in all three checked corpus locations. The classifier test and all 16 provider artifact-corpus/package-asset tests pass locally. Replacement CI runs against the published repair; previous failures are not represented as current validation.

No registry publication, tag, release, or ownership change is included. Package extraction and its guards remain unfinished, so the PR remains a draft.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[flyingrobots]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[flyingrobots]

Both independent CI causes are repaired and pushed:

• 88dab2e adds crates/echo-runtime/** to the explicit determinism policy. The existing classifier regression reproduced the missing-member failure locally and passes after the change.
• 0f33559 regenerates the provider package's repository manifest and lockfile carriers with echo-edict-provider-assets --write. The exact-owner/Cargo-archive regression now passes.

The push hook passed. Replacement CI still needs to confirm the published tree. CodeRabbit's requested review was rate-limited, so this does not represent a completed new bot review or a merge approval.

[flyingrobots]

Landing decision: keep the broader runtime/public-release boundary draft deferred. It is not a prerequisite for the correctness/source-function/observation/cache/retained-strand outcomes now integrated on main.

At current head b948df95, the proposed facade is flyingrobots-echo-runtime 0.1.0-alpha.1 with publish = false. That internal preparatory facade does not establish a completed public release workflow. This branch still needs its own current-main integration, bounded authority/API compatibility claim, external consumer and release-artifact validation, and fresh exact-head review/CI before any independent admission decision. Its old stacked-parent or validation text is historical, not current gate evidence. No release or production Keep adoption is implied by the landed sequence; original commits remain preserved for later review.