[repo-assist] ci: disable broken scriptgen integration test job

[!CAUTION]
Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: .github/workflows/ci.yml

🤖 This is an automated response from Repo Assist.

Context

PR #4396 added a new linux-integration-scriptgen CI job to run the previously-disabled TestCategory=scriptgen integration test suite. As reported in a comment on that PR, the job fails consistently:

Failed! - Failed: 3, Passed: 9, Skipped: 1, ... (net9.0)
Failed! - Failed: 5, Passed: 7, Skipped: 1, ... (net461)

Root cause

This is not a bug introduced by #4396 or any recent Paket code change. The loading-scripts scenario fixtures (e.g. simple-dependencies, mscorlib) declare unpinned version ranges in paket.dependencies (nuget NUnit ~> 2, nuget log4net ~> 1, etc.) and ship no paket.lock. Each CI run resolves whatever the current matching package versions are on nuget.org. Several of those packages (NUnit, log4net, Microsoft.Rest.ClientRuntime.Azure) have since changed their lib/ folder layout, so:

• paket install succeeds but downloads different file layouts than the tests expect
• load-script generation throws DirectoryNotFoundException looking for DLL paths that no longer exist
• hard-coded expected file-name assertions (e.g. nunit.csx) no longer match

Fix

Disables the linux-integration-scriptgen job added in #4396 (commented out, not deleted, with an explanatory note) so CI is green again. Filed #4397 to track properly repairing the scenario fixtures (pinning versions / adding a paket.lock, refreshing expectations) before the suite is re-enabled.

Trade-offs

• The scriptgen integration suite remains disabled in CI for now — no regression coverage for load-script generation until the fixtures are fixed.
• Kept the job definition commented in place (rather than reverting the whole commit) so re-enabling it later is a small diff once the tracking issue is resolved.

Test Status

• No F#/build changes were made; this is a CI-workflow-only change.
• Validated .github/workflows/ci.yml with python3 -c "import yaml; yaml.safe_load(open('.github/workflows/ci.yml'))" — parses successfully.
• Did not run the full build/test suite locally (network/tooling not fully available in this sandbox); the change only removes a currently-failing CI job so it doesn't affect other test suites.

Closes nothing directly, but addresses the CI failures reported in #4396.

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

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Original error: The process '/usr/bin/git' failed with exit code 1

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

# Download the artifact from the workflow run
gh run download '33255095604' -n agent -D '/tmp/agent-33255095604'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-33255095604/aw-repo-assist-disable-broken-scriptgen-ci-4396.bundle'
temp_ref='refs/bundles/create-pr-repo-assist-disable-broken-scriptgen-ci-4396-c220953fd1871693-bcbd32c3'
target_ref='refs/heads/repo-assist/disable-broken-scriptgen-ci-4396-c220953fd1871693'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
  bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
  echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
  exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'repo-assist/disable-broken-scriptgen-ci-4396-c220953fd1871693'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"

# Push the branch to the target remote
git push 'origin' 'repo-assist/disable-broken-scriptgen-ci-4396-c220953fd1871693'

# Create the pull request
gh pr create --title '[repo-assist] ci: disable broken scriptgen integration test job' --base 'master' --head 'repo-assist/disable-broken-scriptgen-ci-4396-c220953fd1871693' --repo 'fsprojects/Paket'

Open .github/workflows/ci.yml and inspect the linux-integration-scriptgen job added in PR #4396, along with the failures described for the loading-scripts fixtures. Validate the workflow with the documented Python YAML parse command; done means the broken job is disabled with its explanatory note while the remaining CI configuration parses successfully.