Admit generic Edict pure-program contracts

[flyingrobots]

Goal

Admit and execute compiler-produced generic pure Edict programs without adding
application ontology to Echo.

Progresses #684.

Plan

• Vendor and admit the exact Edict docs: dependency DAG automation + workflows (#200) #201 contract publication.
• Regenerate and identity-bind the provider package closure.
• Rebuild both provider components twice in the designated Linux/amd64 builder and promote only byte-identical output.
• Prove the checked components through the native Edict provider host witness.
• Admit the exact Echo-owned compiler-produced-bounded-pure/v1 target configuration.
• Package and independently verify the compiler-produced generic pure Target IR.
• Evaluate the generic pure program under its declared budgets.
• Add runtime settlement evidence without consumer-specific branches.

Current status

The generic package-and-verification slice is complete. The real Jedit
ReplaceRange.edict application build now reaches the checked Echo lowerer,
which emits a distinct compiler-produced pure package retaining the exact Core,
lawpack exports, Target IR, and result projection. Echo's structurally separate
verifier reconstructs that relation without calling the lowerer and emits an
accepted report.

The zero-choice target configuration contains only Echo's API version and
generic program kind. It carries no application operation, policy, budget
override, graph patch, or runtime authority. Both checked provider components
were rebuilt twice in the designated Linux/amd64 environment; each pair was
byte-identical before promotion.

The real Jedit build is package conformance evidence only. This draft does not
claim generic program evaluation, graph mutation, runtime settlement, rope
mutation, or end-to-end Jim behavior. Echo production code and ABI surfaces
remain free of Jim, Jedit, rope, buffer, range, and editor semantics.

Documentation accuracy gate: reviewed the repository entrances and canonical
provider-hosting owners. Updated contract provenance, target-configuration and
package posture, both checked component identities, package identity closure,
and the changelog. No superseded application-specific execution path was
documented or introduced.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2d670636-9b7f-448d-a994-9d1961de5300

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}