Contract QueryView Observer Bridge

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/asap/PLATFORM_contract-queryview-observer-bridge.md
Original lane: asap
Original legend: PLATFORM

Original backlog card

Contract QueryView Observer Bridge

Status: core observer bridge, generated query helper checkpoint, installed
contract package registry boundary, and local installed mutation dispatch proof
complete.

Depends on:

• Installed Wesley contract host dispatch
• Contract-aware receipts and readings
• 0018 - Contract-Hosted File History Substrate

Why now

echo-wesley-gen can emit query helpers that build
ObservationRequest { frame: QueryView, projection: Query { ... } }.

warp-core now routes QueryView/Query observations to installed contract
query observers when one is available for the generated query op id. The
observer receives the query id, canonical vars bytes, original request, resolved
causal basis, runtime, and provenance store as read-only context. It returns
bounded bytes and residual posture; Echo wraps the bytes in
ObservationPayload::QueryBytes and stamps the ReadingEnvelope with the
authored observer plan identity.

echo-wesley-gen --contract-host now emits std-only query observer helpers for
that boundary: deterministic authored observer plan identity, typed
context-vars decoders that return Result, and read-only observer constructors
that install host closures through warp-core.

RED

Added failing tests that prove:

• a missing observer returns typed UnsupportedQuery;
• an installed observer receives query id, vars bytes, and basis coordinate;
• emitted QueryBytes carry a ReadingEnvelope naming the authored observer
  plan;
• changing schema/plan identity, op id, vars, or basis changes artifact
  identity;
• bounded observers can report residual posture.
• generated contract-host output includes query observer helper constructors;
• generated query observers decode typed vars from observer context and return
  typed observer errors for malformed canonical vars;
• generated mutation host helpers and query observer helpers compile and install
  together in a consumer smoke crate.

GREEN

ObservationService routes QueryView/Query observations to an installed
contract observer when one is available.

Return:

ObservationPayload::QueryBytes(bytes)

and a ReadingEnvelope that names contract/query identity.

echo-wesley-gen --contract-host emits generated query observer helpers that
bind Wesley query definitions to this read-only observer boundary without
adding application nouns to core.

Acceptance criteria

• Unsupported query op returns typed obstruction/error, not fake empty success.
• Same query, basis, and vars produce stable reading identity.
• Changing schema hash, op id, vars, or basis changes identity.
• Bounded observers can report budget/residual posture.
• Generated query observer helpers install through
  Engine::register_contract_query_observer.
• Malformed generated query vars become typed observer errors, not None.

Remaining work

• Contract-aware readings still need package identity carried through the
  evidence surface used by product-facing consumers.

Non-goals

• Do not add jedit-specific read APIs.
• Do not make generated query helpers call KernelPort::observe in this slice.
• Do not require full file materialization for the bridge test.

[coderabbitai]

🔗 Related PRs

#326 - Echo contract hosting roadmap [merged]
#365 - feat(wesley): emit query observer host helpers [merged]
#368 - feat(core): connect installed contract intent pipeline [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#380 - feat(core): expose retained evidence posture on readings [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!

[flyingrobots]

Closing from the 2026-07-03 issue fate audit. The useful work here is complete or superseded by the current GitHub-native release/goalpost structure; active follow-through now lives in the narrower open Echo issues.