NuGet: stop pushing the stale committed napper.1.0.0.nupkg

v0.13.5 actually PUBLISHED Nimblesite.Napper.0.13.5 ("Created / Your
package was pushed"). The job then failed only because the *.nupkg glob
also matched a stale build artifact committed at
src/Napper.Cli/nupkg/napper.1.0.0.nupkg — pushing that 403s on the
foreign-owned `napper` id.

- git rm the committed artifact and gitignore **/nupkg/ + *.nupkg so packed
  packages are never committed again.
- Push only "Nimblesite.Napper.${VERSION}.nupkg" (explicit, version-scoped)
  instead of a broad glob.

Author: MelbourneDeveloper

.github/workflows/release.yml

@@ -601,10 +601,11 @@ jobs:
         with:
           user: ${{ env.NUGET_USER }}
       - name: Push to NuGet (skip if already published)
-        # Glob the single packed .nupkg so the push is decoupled from the PackageId
-        # (currently Nimblesite.Napper.<version>.nupkg, not napper.<version>.nupkg).
+        # Push ONLY this version's package. A bare *.nupkg glob once also matched a
+        # stale committed napper.1.0.0.nupkg and 403'd on the foreign-owned `napper` id;
+        # the artifact is now gitignored, and this explicit path is belt-and-suspenders.
         run: |
-          dotnet nuget push src/Napper.Cli/nupkg/*.nupkg \
+          dotnet nuget push "src/Napper.Cli/nupkg/Nimblesite.Napper.${VERSION}.nupkg" \
             --api-key "${{ steps.nuget_login.outputs.NUGET_API_KEY }}" \
             --source https://api.nuget.org/v3/index.json \
             --skip-duplicate

.gitignore

@@ -113,3 +113,11 @@ scripts/.too_many_cooks/
 __pycache__/
 
 .playwright-mcp/
+
+# =============================================================================
+# Build artifacts — NEVER commit packed packages (a stale napper.1.0.0.nupkg
+# here once broke the NuGet publish: the push glob matched it and 403'd on the
+# foreign-owned `napper` id). dotnet pack regenerates these every release.
+# =============================================================================
+**/nupkg/
+*.nupkg