docs(ci): correct clean-install action description

[BigSimmo]

Summary

• Confirm PR CI: enforce reproducible dependency installs #1360 already merged the correct reproducible npm/CI installation changes.
• Correct the remaining stale UI setup-action description so it accurately states that CI performs a clean npm install and caches npm downloads, not node_modules.
• Record the completed dependency-installation review in the append-only ledger.

Review outcome

No P0-P2 findings. The merged implementation uses Node 24/npm 11, the single synchronized package-lock.json, npm ci --include=dev, npm download caching, and explicit Vitest/ESLint installed-lock parity. Vitest remains correctly declared and invoked from the root package.

Verification

• npm run check:github-actions — GitHub Actions pin check passed.
• npm run check:branch-review-ledger — Branch review ledger guard passed: 95 live table records + 1206 archived ...
• npm run check:ci-scope — CI change scope self-test passed.
• git diff --check
• committed merge-marker scan — none found

Verification not run: npm run verify:pr-local; this follow-up only changes composite-action description text and the review ledger, and the isolated worktree has no dependency installation. The underlying setup implementation was already merged in #1360.

Risk and rollout

• Risk: Documentation-only metadata correction; no runtime or workflow execution behavior changes.
• Rollback: Revert commit 6dd67737d.
• Provider or production effects: GitHub branch push and PR creation only; no hosted checks were rerun and no application provider was contacted.

RAG impact: no retrieval behaviour change — documentation-only action description and review ledger record.

Summary by CodeRabbit

• Documentation
  • Clarified the UI end-to-end testing environment, including clean npm installation, cached downloads, Chromium availability, and dependency setup.
  • Added a review record documenting CI reproducibility findings and updated cache description details.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in:24 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0598b229-f137-4f38-bc42-2a93c966cbb0

📥 Commits

Reviewing files that changed from the base of the PR and between d0d5ddd and a91ed88.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

📝 Walkthrough

Walkthrough

The UI E2E composite action description now documents npm and Chromium caching behavior, while the branch review ledger records the related CI reproducibility review and cache-description correction.

Changes

UI E2E documentation

Layer / File(s)	Summary
UI E2E setup contract .github/actions/setup-ui-e2e/action.yml	The action description now specifies clean npm installation, cached downloads, Chromium archive reuse, and fresh-runner installation of Playwright system dependencies.
Review ledger record docs/branch-review-ledger.md	A new review record documents the dependency installation and CI reproducibility check and its cache-description correction.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• BigSimmo/Database#657: Adds a related branch-review-ledger.md review record.
• BigSimmo/Database#870: Extends the same review ledger with another record.
• BigSimmo/Database#1325: Adds a related append-only ledger row.

Suggested reviewers:claude, cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: correcting the CI clean-install action description.
Description check	✅ Passed	The description covers the required summary, verification, and risk/rollback sections, with only minor template-format omissions.
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.

---

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