Remove the standalone RelayHistory component; native History is the base (agent-relay 0.7.0)

Merged
KH
9d ago
+1471-6007

Removes the standalone RelayHistory component (charts/relayhistory, built from the private relayhistory-cloud repo, image ghcr.io/agentworkforce/relayhistory). History is always the native Sessions path: relay-control's native backend, the Sessions read API (session-read-api, built from relayhistory-pipeline) and the ingest edge on the history.<domain> origin, with no RelayAuth.

Chart (agent-relay 0.6.59 -> 0.7.0)

  • The relayhistory dependency is gone. components.relayhistory: true or a non-empty relayhistory: values block now fails the render with a pointer to docs/self-hosted-no-relayauth.md, so an old values file can't silently drop History on upgrade. components.relayhistory: false is still accepted and ignored.
  • Chart defaults: relay-control.services.relayhistoryBackend: native, relayauthEnabled: false, components.relayauth: false (RelayAuth stays available as an opt-in for relaycast.credentials.authority=relayauth).
  • values-eks.yaml and values-gcp.yaml are now native on their own. They contain what values-eks-native.yaml / values-gcp-native.yaml used to add, and values-gcp.yaml also carries REQUIRED OVERRIDE placeholders for the reader, ingest edge and search indexer. The two native overlays are now empty {} compatibility files, so existing commands that name them still work.
  • gkeIngress: the history host always routes to the native read and ingest edges. The legacy "route / to the relayhistory Service" branch and gkeIngress.backends.history are removed, and a non-native Control backend behind gkeIngress is refused.
  • values-gcp-proof.yaml is native. values-gcp-proof-live.yaml is now only a legacy-name overlay (the old proof release is being retired). values-kind-core.yaml is now only the base layer for the native kind composition.
  • No other chart changes, so no other version bumps.

Render evidence (helm template, before = origin/main f4cae9b, after = this branch, full nested deps built)

Byte-identical (zero diff lines, chart labels included):

  • values-eks.yaml + values-eks-native.yaml
  • values-eks.yaml + values-eks-rds-native.yaml
  • values-eks.yaml + values-eks-rds-native.yaml + ci/agent-relay/eks-rds-native-site-values.yaml
  • values-eks.yaml + values-eks-native.yaml + a customer-pack-shaped site values file (placeholders filled locally, not committed)
  • values-gcp.yaml + values-gcp-native.yaml + ci/gcp-native-values.yaml
  • ci/agent-relay/kind-durable-actors-values.yaml
  • every leaf chart's ci/*-values.yaml render

Also: values-eks.yaml alone now renders exactly what values-eks.yaml + values-eks-native.yaml rendered before. values-gcp.yaml alone differs from the old gcp-native CI render only in 3 placeholder strings / one hash-suffixed Job name. Renders that changed on purpose: the base-only GCP and GCP proof profiles (legacy to native), recorded in the updated ci/agent-relay/subdomain-golden.sha256 (eks-rds-native, kind-durable-actors, relay-control and relay-webapp goldens are unchanged).

Harness and tooling

  • ci/agent-relay/render.sh and scripts/ci/charts.sh: legacy History checks (write hold, migrate Job, ConfigMap audience, historyOrigin match) are replaced by native checks: Control env, history host backends, no relayauth, base == base + compat overlay, and refusal of the removed keys.
  • kind: the single-phase make kind-up / kind-render / kind-proof / kind-reconcile-names, which ran the standalone server, now refuse with a pointer to make local-up and the native core installer. proof.py, named_upgrade.py and cost.mjs are removed, and the offline tests now cover the native composition.
  • scripts/selfhost: e2e-gcp-proof* are native-only (--history-profile accepts only pipeline). eks-alb-ingress.sh drops the legacy History backend option and defaults the ingest routes on. eks-proof-install.sh is removed: it installed only published 0.3.x/0.4.x charts that shipped the removed component.
  • Release records: the RelayHistory image is removed from self-hosted/customer-images.yaml, along with its license and relayHistoryMigrations from the evidence, schema and validator. The release-gate fixture uses a neutral first-party image. The release manifest overlay no longer emits a relayhistory: block, which would now fail the render. The requirements registry drops the relayhistory chart entries, and the unreleased 0.6.59 matrix row becomes 0.7.0. docs/self-hosted-requirements.md is regenerated.
  • Terraform: the aws-environments application_contract drops components.relayhistory.
  • Docs and READMEs: rewritten for native History. Dated evidence and handoff records get a one-line removal note instead of a rewrite. THIRD_PARTY_NOTICES.md: only the Relay History row is removed, to avoid conflicting with #278.

Tests run locally (macOS, Helm 4.3.1 for chart checks)

Pass: scripts/ci/charts.sh static (lint, kubeconform), ci/agent-relay/render.sh (including the subdomain goldens), scripts/ci/deps.sh, ci/actors-s3/render.sh, ci/relaycast/render.sh, ci/sessions-pipeline-profiles/matrix.sh static, node ci/self-hosted-requirements/registry.mjs check plus the doc-render diff, make local-acceptance-test, every python and node test step in lint.yml, make dev-test, ci/customer-release-gate/test.py, validate-customer-release.py --consistency, scripts/ci/version-bump.sh, and tofu test for aws-environments (57 passed).
Still failing, with identical output to an untouched origin/main checkout (macOS stat/sed/tar, and the handoff scan matching the local git user): scripts/selfhost/tests/run-tests.sh, test_ci_deploy.py, ci/customer-handoff/smoke.sh, ci/self-hosted-requirements/test.sh. With a neutral git user in a scratch clone, smoke passes.

Not run: kind/Docker e2e. That proof runs separately on the ar-lap machine.

Left on purpose

  • Shipped compatibility-matrix rows in self-hosted/requirements.yaml still list relayhistory 0.1.x: they are release records checked against tags.
  • The relay-control leaf chart keeps its relayhistoryBackend: legacy|native setting (leaf default unchanged) and the managed-reader mode used by nativeRouting. The relayauth chart's own History-assertion settings are unchanged.
  • Terraform keeps the retained relayhistory database in the GCP example and the history service in postgres-layout: removing them would drop a database on apply.
  • docs/gcp-install/* is pinned to release 2026.11.1 (chart 0.6.53) and is unchanged.
  • THIRD_PARTY_NOTICES.md still names relayhistory-cloud in the "unlicensed suite sources" paragraph; it is left for #278.

šŸ¤– Generated with Claude Code


Autofix with [code]smith
Open in [code]smith Ā· Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

Removes the standalone RelayHistory component (charts/relayhistory, built from the private relayhistory-cloud repo as ghcr.io/agentworkforce/relayhistory) so History is always the native Sessions path: relay-control's native backend, the Sessions read API, and the ingest edge on the history host, with no RelayAuth. RelayAuth stays available as an opt-in for relaycast.credentials.authority=relayauth. agent-relay goes from 0.6.60 to 0.7.0.

Migration

  • Setting components.relayhistory: true or a non-empty relayhistory: values block now fails the render with a pointer to docs/self-hosted-no-relayauth.md; components.relayhistory: false is accepted and ignored.
  • values-eks.yaml and values-gcp.yaml are native on their own, and the native overlay files are now empty compatibility files; the native install profiles render byte-identically to before.
  • The GKE ingress routes the history host only to the native read and ingest edges.

Tooling

  • The single-phase kind profile (kind-up, kind-proof, kind-reconcile-names) is retired in favor of make local-up and the native core installer; eks-proof-install.sh is removed.
  • The local Postgres proof now accepts the image's SQLite fallback so the proof runs when a database URL is set, and the kind acceptance usage check reads the wrapped Usage API report envelope.
  • The local installer refreshes chart packages when the locked dependency graph changes, so a cached install drops the removed relayhistory subchart.
  • Release records, Terraform (with re-recorded aws-environments plan goldens for both the tofu and terraform engines), and docs no longer reference the RelayHistory image or its migration evidence.