Phase 4: consume and validate the worker secret fix on main

Description

Phase 4 of the worker secret-deployment repair.

Consume the fixed API chart on the main self-managed stack line and complete
end-to-end validation for both maintained stack lines.

Parent tracking issue: #404

Entry condition

• Phase 2 is complete and the API chart is published.
• Phase 3 has identified the fixed 0.6 release candidate.

Definition of Done

• Update the main self-managed stack API chart pin.
• Update matching chart-version validation and documentation metadata.
• Render the stack and verify the worker-init image resolves to the fixed
  version.
• Deploy and invoke a container function with secrets.
• Deploy and invoke a Helm-chart function with secrets.
• Confirm secrets-less deployment coverage still passes.
• Confirm the 0.6 release candidate passes the same secret-bearing deployment
  checks.
• Record validation evidence and close the parent tracking issue.

Out of scope

• Changes unrelated to worker secret injection.

By submitting this issue, you acknowledge that you are an assigned member of the
NVCF development team and agree
to follow our code of conduct and our
contributing guidelines.

Start by locating the main self-managed stack API chart pin, matching chart-version validation, and documentation metadata. Render the stack to verify the worker-init image, then run the container-function, Helm-chart-function, and secrets-less deployment checks for both maintained stack lines. Done means the fixed version is consumed and validation evidence is recorded against the parent issue.