[repo-assist] Flaky scriptgen integration test scenarios resolve against live NuGet feed (no committed paket.lock)

Context

PR #4395 added a linux-integration-scriptgen CI job. It has been failing intermittently, e.g.:

Failed simple dependencies generates expected scripts
ERR: DirectoryNotFoundException: Could not find a part of the path
".../loading-scripts/simple-dependencies/temp/packages/NUnit/lib/nunit.framework.dll"

Other scriptgen tests in the same run also failed (fslab generates expected load of package loader script, issue 1676 casing, mscorlib excluded from f# script), including one case where FSharp.Core 11.0.100 was unlisted upstream.

Root cause

The scenario fixtures under integrationtests/scenarios/loading-scripts/{simple-dependencies,fslab,issue-1676,mscorlib}/before/ only contain a paket.dependencies file — there is no committed paket.lock. Each CI run therefore performs a live dependency resolution against nuget.org, so results (and even which NUnit/FSharp.Core version gets resolved) can vary run-to-run as upstream packages are updated, unlisted, or restructured. This is test-infrastructure flakiness, not a Paket regression, and mirrors the broader flakiness already tracked in #4346.

Immediate mitigation

As requested, I marked the linux-integration-scriptgen job as continue-on-error: true in .github/workflows/ci.yml (pushed to PR #4395) so it no longer blocks merges while remaining visible for maintainers to observe.

Suggested follow-up

• Add committed paket.lock files to each affected scenario's before/ directory so resolution is deterministic and doesn't depend on live feed state.
• Once deterministic, remove continue-on-error from the job so it becomes a required, reliable check again.

This issue was opened automatically by Repo Assist, an AI assistant, per instructions on PR #4395.
Related to #4395

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

Inspect the before/ directories for simple-dependencies, fslab, issue-1676, and mscorlib under integrationtests/scenarios/loading-scripts, then review .github/workflows/ci.yml. First reproduce or inspect the linux-integration-scriptgen scenarios and generate committed paket.lock files for each fixture. Done means dependency resolution is deterministic and continue-on-error is removed from the job.