Admit bounded observation uncertainty without workspace authority

[flyingrobots]

Hello Echo review exposed a recovery gap in the generic bounded-observation host boundary. After a durable claim, workspace authority may be unavailable; Echo must still construct and admit the schema-bound outcomeUnknown settlement from the retained grant and runtime-owned adapter profile without reopening the workspace.\n\nAcceptance:\n- add a rootless, generic reconciliation handle or equivalent API owned by Echo;\n- derive it from the exact bounded-observation profile and expose no read authority;\n- admit outcomeUnknown only for the matching durable grant and Edict request;\n- retain the existing schema, budget, basis, adapter, and settlement validation;\n- prove workspace deletion after claim does not prevent durable ambiguity settlement;\n- reject substituted profiles, grants, requests, and zero evidence;\n- add no application vocabulary, native callback, or convenience filesystem access.\n\nBlocks flyingrobots/hello-echo#10.

[coderabbitai]

🔗 Related PRs

#670 - Add trusted causal anchor admission [merged]
#688 - Route executable-operation Actions through scheduler-owned Ticks [merged]
#701 - Evaluate package-declared typed application results [merged]
#704 - Add durable external-action settlement protocol [merged]
#706 - Host bounded workspace observations [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!