[rbjornstad]

Summary

• Map RecoveryFailed=True with reason Unrecoverable to DEGRADED, even when reconcilePhase is Failed.
• Add a Kubernetes fixture for the failed branch and Lua GraphQL coverage for branch state and state facets.
• Add unit coverage for terminal and non-terminal recovery failures.

Validation

• go test ./internal/persistence/postgres (pass)
• go test ./internal/kubernetes/fake (pass)
• Lua integration test was attempted but could not start because sandbox access to /var/run/docker.sock was denied.

[Copilot]

🟢 Approval recommended

The focused mapping change has no identified blocking issues and includes regression coverage, though integration execution remains unverified.

No open issues 🎉

What changed in this PR

Corrects Postgres branch state reporting so unrecoverable recovery failures appear as DEGRADED, even when reconciliation has failed.

Changes:

• Prioritizes terminal recovery failures in state mapping.
• Adds unit coverage and a failed-branch fixture.
• Extends GraphQL coverage for branch states and state facets.

File	Description
internal/​persistence/​postgres/​models.go	Maps unrecoverable recovery failures to DEGRADED.
internal/​persistence/​postgres/​models_test.go	Covers terminal and non-terminal failure conditions.
integration_tests/​postgres_branches.lua	Checks degraded branch state and facet counts.
integration_tests/​k8s_resources/​postgres_branches/​dev/​someteamname/​postgres_foobar_failed.yaml	Adds an unrecoverable branch fixture.

_{Review effort: Balanced}