chore(ci): extend token-wiring debug (prefix + rate_limit + nix.conf)

[thedavidmeister]

Follow-up to #243. The token is present (len=426) yet the flake fetch still 429s. This logs: token prefix (type — ghs_ vs JWT), a rate_limit auth check (does the token actually authenticate?), and whether access-tokens landed in /etc/nix/nix.conf (i.e. does nix develop even read it). Temporary; revert after diagnosing. NOT self-merging — for review/merge by a human.

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ae32c5a3-5658-47f0-89b6-ef71189587ea

📥 Commits

Reviewing files that changed from the base of the PR and between 307bf27 and 7f61239.

📒 Files selected for processing (2)

• .github/actions/nix-cachix-setup/action.yml
• .github/workflows/rainix-manual-sol-artifacts.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch debug/token-wiring-2

---

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.}

[thedavidmeister]

Superseded. Diagnosis complete: the 429 is GitHub's burst rate-limit on the flake HEAD-resolution call (api.github.com/commits/HEAD), not a token-wiring issue — the token is present and valid (ghs_, applied via NIX_CONFIG) but the fetch still fails. Real fix is pinning the flake rev: #245. Closing this debug PR.