Skip to content

E2E test: TerraYield peer renders map/chart/table in workspace shell (AC-6 / OQ-2) #13

Description

@mortonanalytics

Goal

End-to-end integration test that registers TerraYield (Meridian) as a live federation peer and asserts its resources render through the workspace shell. This is the AC-6 / OQ-2 blocker called out in md/design/map-view.md:275 ("Neither GroundPulse nor TerraYield currently exposes ione_view: map resources … prerequisite for integration testing").

Scope

A test fixture (style of tests/phase12_peer.rs / tests/phase14_bindings.rs) that:

  1. Stands up Meridian's MCP server + OAuth 2.1 AS as a peer (or a faithful mock of the six surfaces).
  2. Runs the peer-join flow: discovery → PKCE → token → tools/list / resources/list → tool allowlist → active.
  3. Creates a workspace_peer_binding (auto-populated from Meridian whoami when available; best-effort otherwise).
  4. Asserts the shell renders Meridian's map (parcel/county tiles), chart (yield series), and table (condition/progress) resources from view-hint metadata with no Meridian-specific UI code.
  5. Asserts a signed webhook from Meridian (publication.created) fans in to a signal with correct severity + replay protection.

Acceptance

  • The "one pane of glass" path (GP + TerraYield as one operator workspace, foreign-tenant-mapping.md:15) is covered by an automated test, not a manual demo.
  • Test gates on live Postgres (mark #[ignore] consistent with the suite).

Cross-repo

  • TerraYield peer surfaces: morton-analytics-llc/eo_ag (MCP server, view-hints, discovery issues).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfederationIONe federation / peer integration

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions