fix(ci): paginate nightly scorecard trend lookup

[jyaunches]

Summary

• add a regression test for scorecard trend lookup when selective dispatch volume fills the first workflow-runs API page
• paginate the prior scheduled-run lookup in the nightly scorecard
• keep the lookup bounded while allowing the previous scheduled run to be found beyond page one

Validation

• npm test -- test/nightly-scorecard.test.ts test/validate-e2e-coverage.test.ts test/e2e-advisor-dispatch.test.ts

Summary by CodeRabbit

• Tests

  • Added test coverage for detecting prior scheduled workflow runs with filtering and pagination.

• Chores

  • Improved nightly test workflow to use optimized pagination when fetching prior workflow runs for trend comparison.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 56e19e0d-9051-4325-afb7-c47cf66f1ddb

📥 Commits

Reviewing files that changed from the base of the PR and between e122450 and 1a4eddc.

📒 Files selected for processing (2)

• .github/workflows/nightly-e2e.yaml
• test/nightly-scorecard.test.ts

---

📝 Walkthrough

Walkthrough

The nightly-e2e workflow's scorecard job now fetches prior-day scheduled runs using pagination (up to 10 pages, 100 items per page) to improve trend comparison lookup, replacing a fixed single-page call. A new test suite validates the core pagination filtering logic.

Changes

Nightly Scorecard Prior-Run Pagination

Layer / File(s)	Summary
Workflow pagination implementation .github/workflows/nightly-e2e.yaml	Scorecard job's prior-run fetch replaces a single listWorkflowRuns call (per_page: 50) with a paginated loop (10 pages, per_page: 100) that stops once qualified completed scheduled runs older than 24h are found.
Pagination helper test test/nightly-scorecard.test.ts	New Vitest suite adds findPriorScheduledRunFromPages helper that filters paginated workflow runs by completion status, schedule event, and creation time; test confirms correct run selection across multiple pages.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• NVIDIA/NemoClaw#3735: Both PRs modify .github/workflows/nightly-e2e.yaml's nightly scorecard script around how "prior-day" workflow runs are looked up for trend comparison.

Suggested labels

CI/CD, fix, E2E, enhancement: testing

Suggested reviewers

• ericksoa
• cv

Poem

🐰 A paginated sprint through workflow runs,
Finding scheduled friends from days before,
With tests to prove each loop is true,
The scorecard trends shine bright once more! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: implementing pagination for the nightly scorecard trend lookup to find prior scheduled runs across multiple API pages instead of just the first page.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}