ci: Configure NUGET_API_KEY secret for NuGet publishing

[MCGPPeters]

Problem

The Picea.Glauca and Picea.Glauca.KurrentDB packages are not published on nuget.org despite the CD workflow (cd.yml) being in place and triggering on pushes to main.

The CD workflow was added in commit c6d2c70 and should have triggered on push to main. The most likely cause is that the NUGET_API_KEY repository secret is not configured.

What's Needed

1. Configure NUGET_API_KEY Repository Secret

Go to Settings → Secrets and variables → Actions → New repository secret and add:

• Name: NUGET_API_KEY
• Value: NuGet.org API key with push permissions for Picea.Glauca and Picea.Glauca.KurrentDB

2. Re-trigger the workflow

Once the secret is configured, either:

• Push a new commit to main, or
• Re-run the failed workflow run from the Actions tab

Verification

After the workflow succeeds, verify packages appear at:

• https://www.nuget.org/packages/Picea.Glauca
• https://www.nuget.org/packages/Picea.Glauca.KurrentDB

Context

Part of the Picea org migration (Phase 6.10 — NuGet package verification). Packages from picea/picea (2) and picea/abies (7) are already live on nuget.org.