docs: add wiki Home page and init-wiki workflow

[CornerstoneCode]

Summary

• Adds wiki/Home.md — the source-of-truth for the GitHub wiki Home page
• Adds .github/workflows/init-wiki.yml — a one-shot workflow_dispatch workflow that bootstraps the GitHub wiki by pushing wiki/Home.md to the wiki git endpoint using GITHUB_TOKEN

Why a wiki/ directory in the main repo?

GitHub wiki pages live in a separate git repository ({repo}.wiki.git). Storing the source in wiki/ keeps wiki content version-controlled, PR-reviewable, and diff-able alongside the code it documents. The init-wiki workflow is the bridge that syncs it across.

After merging

Trigger the Initialize Wiki workflow once via Actions > Initialize Wiki > Run workflow. The wiki Home page will be live at:
https://github.com/CornerstoneCode/EntityFrameworkCore.Sqlite.Concurrency/wiki

Wiki Home page covers (SEO targets)

• SQLite Error 5: database is locked - exact exception string, root cause, fix
• SQLITE_BUSY_SNAPSHOT (error 517) - why it differs from SQLITE_BUSY and why simple retry fails
• A second operation was started on this context - DbContext thread safety
• Task.WhenAll SaveChanges EF Core - IDbContextFactory pattern with working code
• bulk insert EF Core SQLite performance - BulkInsertOptimizedAsync with real benchmark numbers
• WAL mode, PRAGMA tuning, common pitfalls (Cache=Shared, network filesystem)

Test Plan

• wiki/Home.md renders correctly as markdown
• Merge PR, then trigger Initialize Wiki workflow
• Confirm wiki page live at repo wiki URL

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 27 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

Run ID: 6e132d1e-0a73-4788-a177-ad68bbb2f279

📥 Commits

Reviewing files that changed from the base of the PR and between fc681a1 and 466abb4.

📒 Files selected for processing (3)

• .github/workflows/deploy.yml
• .github/workflows/init-wiki.yml
• wiki/Home.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wiki-home-page

---

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