fix(csharp): wait for NuGet indexing before release

[konard]

Fixes #86

Summary

• Replace the short inline NuGet verifier with csharp/scripts/wait-for-nuget.mjs, a tested helper that checks the flat-container nuspec endpoint every 2 minutes across the normal NuGet indexing window.
• Use the helper in both automatic C# releases and manual instant releases before creating the GitHub release.
• Add an issue 86 case study under docs/case-studies/issue-86 with GitHub issue/PR/run data, downloaded CI logs, NuGet evidence, template comparisons, and validation logs.
• Report the matching C# template defect upstream: Wait longer for NuGet package indexing before release csharp-ai-driven-development-pipeline-template#13

Root Cause

NuGet accepted clink@2.4.0, but the package was not yet visible from the flat-container API before the old 0/5/10/20/30/60 second retry schedule finished. The package appeared later within the NuGet indexing window, so the release job failed before the registry state it depended on was ready.

Validation

• node --test csharp/scripts/*.test.mjs
• node --check csharp/scripts/wait-for-nuget.mjs
• dotnet test csharp/Foundation.Data.Doublets.Cli.sln --configuration Release
• git diff --check
• node csharp/scripts/wait-for-nuget.mjs --package-id clink --release-version 2.4.0 --max-attempts 1

Evidence

The detailed investigation and preserved logs are in docs/case-studies/issue-86/README.md. Official NuGet references used in the investigation:

• https://learn.microsoft.com/en-us/nuget/nuget-org/publish-a-package#package-validation-and-indexing
• https://learn.microsoft.com/en-us/nuget/api/package-base-address-resource
• https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-push

[konard]

Working session summary

Implemented and finalized PR 87: #87

What changed:

• Added wait-for-nuget.mjs, defaulting to 8 attempts with 120-second intervals.
• Updated both C# release paths to use it in .github/workflows/csharp.yml.
• Added regression tests in release-scripts.test.mjs.
• Preserved the issue/run/log/template evidence in docs/case-studies/issue-86/README.md.
• Reported the matching C# template issue upstream: Wait longer for NuGet package indexing before release csharp-ai-driven-development-pipeline-template#13

Validation:

• Local checks passed: node --test csharp/scripts/*.test.mjs, node --check, dotnet test, git diff --check, and a live NuGet availability probe for clink@2.4.0.
• Latest PR CI passed on head 4dbb7831b739c97fb821c9ebad51d330dcbcaf5e: https://github.com/link-foundation/link-cli/actions/runs/25764039344
• PR is ready for review and the working tree is clean.

Official NuGet references used are linked in the PR body, including Microsoft’s package validation/indexing docs and flat-container API docs.

---

This summary was automatically extracted from the AI working session output.

[konard]

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

• Model: GPT-5.5
• Provider: OpenAI
• Public pricing estimate: $14.369977

📊 Context and tokens usage:

• 330.0K / 1.1M (31%) input tokens, 38.3K / 128K (30%) output tokens

Total: (330.0K + 9.3M cached) input tokens, 38.3K output tokens, $14.369977 cost

🤖 Models used:

• Tool: OpenAI Codex
• Requested: gpt-5.5
• Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (35757KB)

• View complete solution draft log

---

Now working session is ended, feel free to review and add any feedback on the solution draft.

[konard]

🎉 Auto-merged

This pull request has been automatically merged by hive-mind.

• All CI checks have passed

---

Auto-merged by hive-mind with --auto-merge flag