docs: record primary reconciliation dispositions

[BigSimmo]

Summary

• Record both preserved dirty-primary snapshots, verified bundle evidence, landed PRs, duplicates, rejected content, and the final synchronization contract.
• Capture the two valid deferred remnants as Refresh dependencies #75 (search-scope label pagination) and Audit fixes + Node 24 toolchain bump #76 (fixture-first malformed PDF crop reproduction).
• Make no source, workflow, schema, retrieval, provider, or production behavior change.

Verification

• npx prettier --check docs/outstanding-issues.md docs/audit/primary-checkout-reconciliation-2026-07-24.md — passed.
• npm run docs:check-links — 1,149 repo path references resolved.
• npm run docs:check-scripts — 341 npm-run references resolved.
• npm run docs:check-index — all 42 top-level modules/routes and all schema tables indexed.
• git diff --check — passed.
• Not run: npm run verify:cheap; this PR changes Markdown only. Focused documentation guards and protected hosted checks are the proportionate gate.

Risk and rollback

• Risk: documentation accuracy only. Archive refs and hashes were checked against the local repository/bundle evidence before writing.
• Rollback: revert this PR's merge commit; archive refs and external bundles are unaffected.
• Provider effects: GitHub PR/check activity only; no OpenAI, Supabase, Railway, live RAG, migration, or production-data call.

RAG impact: no retrieval behaviour change — documentation and deferred-work disposition only.

[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

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

Next review available in: 21 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e76400dd-9a6c-49fc-8e2f-c487106f71fc

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4e249 and 98a5312.

📒 Files selected for processing (2)

• docs/audit/primary-checkout-reconciliation-2026-07-24.md
• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/primary-reconciliation-record

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b1717b918f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".