The Prometa reference runtime is tenant-plane software. This release does not
install or move the Orchestra control plane into the synchronous request path.

Service: {{ include "prometa-runtime.fullname" . }}:{{ .Values.service.port }}
Health:  /healthz
Ready:   /readyz
Execute: /v1/runtime/execute
Tasks:   /v1/runtime/tasks/{requestId} (when taskRecovery is configured)
{{ if .Values.backup.enabled }}
Backup:  {{ include "prometa-runtime.fullname" . }}-backup CronJob -> external encrypted PVC
{{ end }}

The chart references, but never creates, the runtime config and credential
objects. NetworkPolicy is fail-closed by default. Verify that your values allow
only the intended gateway ingress plus PostgreSQL, model, DNS, and telemetry
egress before promotion.
The migration hook is followed by a target-image compatibility check. Future
chart rollback runs that check before replacing runtime pods.
The database-maintenance NetworkPolicy remains for the complete hook sequence;
include it in tenant cleanup after uninstall because Helm does not manage hook
resources as release resources.
Run prometa-runtime-postgres-verify against a fresh restored database before
tenant CI/CD performs a recovery cutover.
