test: follow preview manifest sequence

[promisepreston]

Summary

• derive the future preview fixture from the accepted manifest instead of hard-coding preview.9
• keep the R2 transition regression independent from the live manifest state
• verify the catalog test both before and after the exact preview.9 candidate manifest update

Verification

• npm test: 14/14 passed on the current preview.8 manifest
• exact simulated preview.9 manifest: 14/14 passed
• npm run build passed in both states
• git diff --check passed

Publication boundary

Protected run 31912527851 failed at isolated public Preview validation before staging or publishing. The R2 publish job was skipped; no object, branch, PR, release, or manifest was created.

Summary by CodeRabbit

• Tests
  • Expanded release validation coverage for both legacy and current download locations.
  • Added checks to ensure hosted releases include verified download metadata.
  • Added validation for missing or mismatched release assets.
  • Updated preview-release checks to follow the currently published manifest, improving test accuracy as release versions change.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 617b5e6a-de1f-48f6-bc70-df0b8829df16

📥 Commits

Reviewing files that changed from the base of the PR and between 6767e6e and 1096523.

📒 Files selected for processing (1)

• test/site.test.mjs

---

📝 Walkthrough

Walkthrough

The release catalog tests now derive preview tags from the manifest, model both GitHub-hosted and R2-hosted releases, and validate required R2 download metadata.

Changes

Release catalog test coverage

Layer / File(s)	Summary
Model GitHub and R2 release fixtures test/site.test.mjs	Fixtures distinguish legacy GitHub assets from R2 verification metadata. The expected preview tag uses the manifest suffix.
Validate accepted and rejected releases test/site.test.mjs	Assertions retain valid releases and reject R2 releases with empty verification metadata or GitHub assets.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 10965

This localized test change follows the accepted preview manifest sequence and validates the catalog behavior across the preview.9 transition; no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

• PrestonCoreSystems/recordcove-preview#5: Both changes update release manifest and download asset validation in test/site.test.mjs.
• PrestonCoreSystems/recordcove-preview#19: This change extends the related release-catalog tests for manifest-derived tags and GitHub/R2 asset validation.
• PrestonCoreSystems/recordcove-preview#10: This change tests release metadata behavior introduced by the updateRelease workflow.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the test changes that follow the preview manifest sequence.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/wo015-preview-release-catalog-test

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud