[Dav-14]

Summary

EN-3313: consume the released Ledger RC.3 scope fix in the Regions v4.0-beta profile.

Component	Before	After
Stack Operator chart	3.21.1	3.21.2
Connectivity Core/API	v1.0.0-beta.5	v1.0.0-beta.6
Regions chart	3.26.3	3.26.4
Parent Formance chart	3.14.2	3.14.3

The single Connectivity version selects both Core and API images. Both beta.6 tags are published at d518138f: Core release, API release. Operator #575 is published as v3.21.2, including its OCI chart.

Update owned dependency locks and generated documentation. Preserve Ledger/its operator at RC.3, Connectivity Operator beta.6, PostgreSQL and every unrelated pin.

Evidence

• Both beta.6 release workflows succeeded and their linux/amd64 + linux/arm64 image manifests were verified. Operator OCI chart 3.21.2 was verified.
• Core beta.6 contains Connectivity #524: canonical Ledger scopes, RC.3 fixture/pins and protocol-40 qualification. API source is unchanged from beta.5; its paired tag prevents a missing API image.
• Full just pre-commit passed with existing Nix-provided Go 1.27.3, Helm 3.19.1, Just 1.51.0 and golangci-lint 2.15.0: locked dependency builds, lint/render, signing-key scenarios and generated docs. Initial native-flake setup was interrupted before checks to avoid rebuilding unrelated tooling; CI will qualify that environment.
• Focused rendering confirmed Operator v3.21.2, the beta.6 Connectivity profile and unchanged Ledger RC.3. The lock audit excludes unrelated floating PostgreSQL updates.
• Principal Engineer, Product Engineer and SRE source lenses passed. No Regions deployment or runtime qualification is claimed.

Merge Danger

Door: coordinated rollback.

Blast Radius: Stack-managed Connectivity and the Operator dependency.

Core and Operator now use ledger:ReadAccount/WriteLedger/WriteTransaction/WriteMetadata/WriteQuery. Existing Credentials update in place, without deleting the object or rotating its signing key. The Ledger Operator watches grant changes and automatically rolls Ledger pods because Ed25519 grants load at startup.

This is incompatible with custom Core versions still claiming RC.1 scope names. Upgrade consumer and credential producer together; a Core-only rollback can interrupt ingestion after grants change. No API shape or storage migration is introduced by this chart change. The Ledger RC.3 pin and existing storage stay unchanged.

The earlier Thierry PR-image qualification verified in-place generation 3→4 migration, Ledger 3/3 readiness, authenticated ledger creation and cursor loading. Architect then reported a separate provider contract error (missing onboarding flag), so full provider ingestion is not asserted. That evidence does not qualify this Regions chart's rollout.

[NumaryBot]

The required automated review completed with no remaining findings.