[f2calv]

Related Issue

None — follow-up to #129 after verifying its publication workflow.

Summary

• Tag-dispatched run 40109557076 published the 1.1.0 image and chart, but the shared NuGet action's default-branch gate silently skipped all packing and pushing. None of the eight expected packages became available within the verification deadline.
• Add nuget-release to the existing deploy-all workflow. Run from the default branch to validate an existing stable GitHub release, check out its exact tag, and publish only its missing NuGet packages. Version calculation, the application build job, image/chart publication and release tagging are skipped in recovery mode; the package action still restores and builds the Release solution.
• Reject stable NuGet publication from non-default workflow refs explicitly. Reject malformed versions, drafts and prereleases before building recovery packages. Preserve the release source revision instead of the newer workflow commit in build provenance.
• Document full publication, immutable artifact boundaries, recovery inputs and NuGet availability verification in docs/artifact-publication.md.
• This workflow-only correction does not change public application contracts. The approved recovery targets 1.1.0 and must not rebuild or replace its published image/chart. No workload deployment is included.

Validation

• Full repository pre-commit lint passed, including YAML and Markdown checks; actionlint 1.7.12 passed for deploy-all.yml.
• Privacy scan found zero high-confidence matches and only reviewed existing synthetic example/fixture patterns.
• No .NET source changes. Exact-head CI40111443025 passed, including the Release build and offline tests. Sonar analysis matches commit 194e143: Quality Gate OK, zero findings. Merge-ref scanning and review threads are empty.
• After merge, dispatch recovery from the default branch with nuget-release=1.1.0, verify all eight exact NuGet versions through the restore endpoint, and recheck that published image/chart identities remain unchanged before continuing the train.

Checklist

• The linked issue, or the summary when there is none, describes and scopes this change.
• Any small unrelated change is called out in the summary.
• Tests and documentation are updated where behavior or public interfaces changed.
• No credentials, personal data or private-system details are included.
• Breaking changes, migrations and operational follow-up are called out.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud