chore: p3 cleanup — stale TODOs, boilerplate, package meta

[Krishan27]

Changes

Boilerplate reduction

• Added startSpinner(text) to shared.ts — creates spinner, wires SIGINT → exit 130, returns the spinner
• All 4 commands (scan, migrate, validate, audit) replaced their identical 2-line createSpinner().start() + process.once("SIGINT", ...) block with a single startSpinner() call

Stale TODO removal

• config.ts — removed TODO v0.3: replace minFileCount with git log (git-based staleness is a post-v1 item, not tracked here)
• scanner/index.ts — replaced bulk-inventory TODO with a factual note: enforcement already exists in the migrator (safelyAutomatable: false, manualReviewReason: "bulk-inventory-call")

pLimit documentation

• Added a 2-line comment above pLimit(50) explaining the concurrency choice and its CPU vs I/O trade-off

package.json

• author: "flaglint" → { name, email, url } object (npm ecosystem standard)
• keywords: added feature-toggle, flag-cleanup, tech-debt

Test plan

• 528/528 tests pass locally

[coderabbitai]

Warning

Review limit reached

@Krishan27, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 384ddbf4-d521-4b27-b768-755390e4b44c

📥 Commits

Reviewing files that changed from the base of the PR and between 28fa0c1 and dbb3ad7.

📒 Files selected for processing (8)

• package.json
• src/commands/audit.ts
• src/commands/migrate.ts
• src/commands/scan.ts
• src/commands/shared.ts
• src/commands/validate.ts
• src/config.ts
• src/scanner/index.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/p3-cleanup-todos-meta

---

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