test: add auth acceptance test script + verify .env gitignore

[isaJrKai]

What this adds

1. Auth acceptance test script

scripts/test-auth-persistence.sh — a curl-based smoke test for the authentication and session management system. Tests:

Test	Description
TEST 1	Login → refresh → still logged in
TEST 2	Login → logout → refresh → remain logged out
TEST 3	Two browsers (cookie jars) — both logged in
TEST 4	Logout browser A → browser B still works

Usage:

# Local dev
bash scripts/test-auth-persistence.sh

# Deployed URL
BASE_URL=https://my-project-one-rust-23.vercel.app \
  TEST_EMAIL=your@email.com \
  TEST_PASSWORD=yourpassword \
  bash scripts/test-auth-persistence.sh

Exit code 0 = pass, 1 = fail — can be used in CI to gate deploys.

2. .gitignore verification

• Confirms .env is gitignored (it was already)
• Adds .env.local and .env.*.local patterns (Next.js convention)
• Adds db/*.db and db/*.db-* patterns (prevents SQLite binaries from being committed)

3. scripts/README.md

Documents how to run the tests, locally and against deployed URLs.

Files changed

• scripts/test-auth-persistence.sh (new) — 4 acceptance tests
• scripts/README.md (new) — usage docs
• .gitignore — added env + db patterns

Vercel env vars

None needed.

Deployment risk

Zero. This only adds test scripts and gitignore patterns. No application code changes.

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 27 minutes and 4 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9be44c40-8f77-4be6-99a0-b8dd0c704d54

📥 Commits

Reviewing files that changed from the base of the PR and between 7053878 and 9d2609d.

📒 Files selected for processing (3)

• .gitignore
• scripts/README.md
• scripts/test-auth-persistence.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/test-script-and-gitignore

---

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