[iamgp]

Superseded by the Phlo monorepo PR

Do not merge this temporary-repository PR as a product deliverable. The replacement now belongs to Phlo #1051, inside the existing phlo-observatory package, image, and CI/security lanes. Follow the corrected landing plan. This PR remains open as the validated source reference; the evidence below describes that source branch.

Scope

Replace fixture-backed Observatory workflows with the public Phlo /api/v1 contract across overview, incidents, assets, pipelines, query, branches, staging, settings, members, and audit.

Mutations use confirmations, pinned environments, durable retry keys, and API-owned outcomes. Errors and unavailable evidence remain visible. No old Phlo routes or UI are removed.

This is the real-service-validated replacement for the older draft Observatory PR #1. Do not merge both client cutovers.

Verification

• CI passed: locked dependency installation, pnpm typecheck, and pnpm build.
• scripts/verify-api-client.mjs passed against live OpenAPI and independent prod/staging inventories: 63 client route shapes, three prod rows, and seven staging rows.
• Disposable Authentik, Traefik, Dagster, Nessie, Trino, Iceberg, and PostgreSQL checks verified OAuth, environment isolation, stored mutations, outage/retry, signatures, branch workflows, and code promotion. The combined Phlo Python suite passed 5,263 tests; real-service checks ran separately.
• Browser screenshots were inspected at desktop and narrow widths, including denied actions, accepted backfill, cancelled runs, and settings conflicts.

Merge gate

The corrected merge destination is Phlo #1051, after the API stack through #1049 and OAuth #1050. This source branch's PR CI passed, but only fresh Phlo #1051 CI and merge-queue checks govern the integrated deliverable. Merging is not deployment approval.

Explicit limits

Do not close Phlo issue #1035 with this slice. Governed Dataset inventory, shared query-history listing, automatic failure correlations, detailed usage/SLA history, per-column schema-decision editing, and old-route retirement remain follow-ups. PR #1's stronger schema-level contract checker is not included here; this branch checks mounted route shapes and validates runtime responses with Zod. No production installation was accessed, and no regulatory-compliance claim is made.