Slice: Retire frontend operation orchestration and the compatibility host

[flyingrobots]

Slice

Finish #295 after the Jim.edict observer slice by deleting or quarantining
frontend/native operation orchestration and the GraphQL/Wesley compatibility
execution route. Make Gate E prove that only canonical event delivery to the
verified Jim.edict composition can satisfy production.

Parent: #295.

Dependencies

• Slice: Author and prove Jim's first Edict operation ReplaceRange #296
• Slice: Author Jim lawpacks for CreateBuffer TextWindow and DeclareCheckpoint #297
• Slice: Host Jim.edict as an active observer #301
• Gate E - jedit Native Operation Proof #143
• Emit a machine-readable authority-gate evidence manifest #283

Acceptance criteria

• Remove production command-to-ReplaceRange mapping from TypeScript.
• Remove native Jim semantic dispatch, planner callbacks, and direct
  operation invocation that exist only for compatibility.
• Remove the production echo-wesley-gen --contract-host package and
  generated host/client artifacts from the executable route.
• Quarantine retained compatibility corpora under historical or test-only
  boundaries.
• Production composition requires verified Jim.edict plus its lawpacks,
  semantic-free event/artifact transport, the real generic Echo runtime, and
  disposable rendering.
• Missing Edict/Echo capability fails closed; no compatibility or fake
  fallback exists.
• The cutover guard rejects direct operation orchestration, handwritten
  packages, native callbacks, caller patches, fake transports, local text
  authority, manufactured receipts, and optimistic mutation.
• Gate E executes the designated event -> reading -> child operation ->
  outcome -> Jim state transition and emits the Emit a machine-readable authority-gate evidence manifest #283 evidence manifest.
• Evidence binds exact Jedit, Edict, and Echo commits; source/package/verifier
  digests; receipts; recovery; and negative bypass tests.
• Documentation describes the active-observer corridor as current only
  after executable gates pass.

Closure rule

Do not close this issue merely because direct operation conformance is green.
The old route must be absent or production-unreachable, and the negative gate
must prove that fact.

[coderabbitai]

🔗 Related PRs

#23 - feat(echo): add Echo release gate witness [closed]
#27 - feat(echo): wire trusted runtime lifecycle into jedit [closed]
#152 - Add editor trust and strand worldline UX [merged]
#193 - docs: lock Jim roadmap evidence slices [merged]
#261 - Complete CR-00 snapshot escape hatch guard [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!