docs(issues): reconcile 21 queued ledger requests

[BigSimmo]

Summary

• Reconcile the 21 queued requests in docs/outstanding-issues-inbox/ into the canonical ledger in one serialized transaction, moving each request to docs/outstanding-issues-inbox/applied/ as an immutable audit record.
• Includes the PR fix(ui): mark search empty-state tone by stroke and restore its desktop tap floor #2147 follow-up task: hoist the filtered-zero empty state out of the documents results grid so recovery can sit flush under the results band.

This is the deliberately serialized ledger operation — it is the whole deliverable, and no product code changes.

Verification

• npm run check:outstanding-issues — 392 rows (57 open, 335 archived), unique display and durable ids, collision-free allocation, no ids deleted from base b400b138f8c1
• npm run check:ledger-write-discipline — self-test passed; Ledger write discipline passed for b400b138f8c1..HEAD
• npm run format:changed — clean
• Ledger inbox check — 0 pending requests, 391 applied
• npm run verify:pr-local

UI verification not run: no UI, routing, styling or browser behaviour is touched — this change is confined to docs/outstanding-issues.md and the inbox request files.

Risk and rollout

• Risk: Low. Documentation-only. The canonical diff is exactly the recorded reconciliation transaction, which is what check:ledger-write-discipline verifies against the committed refs.
• Rollback: git revert the single commit; the applied records return to pending.
• Provider or production effects: None.

Notes

• Do not use GitHub's "Update branch" button on this PR — it touches the canonical ledger, and AGENTS.md requires the serialized branch to keep its base.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in:59 minutes

Limit details: You’ve used the included review currently available. Your 103 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 16cd6e2f-7458-4df7-8795-d6c8a5b5f9d4

📥 Commits

Reviewing files that changed from the base of the PR and between 42426f4 and b393cdd.

📒 Files selected for processing (22)

• docs/outstanding-issues-inbox/applied/07867a60-274a-4350-a564-2fed480ff997.json
• docs/outstanding-issues-inbox/applied/1b3f0964-1cf4-4fad-b89d-b9393797807a.json
• docs/outstanding-issues-inbox/applied/25e8c062-8fa0-46be-844a-03245fc9857b.json
• docs/outstanding-issues-inbox/applied/2c95ad4c-bbc7-4043-9c79-8afd529fa4c2.json
• docs/outstanding-issues-inbox/applied/338d45ec-397e-4eb4-b991-3185079509a4.json
• docs/outstanding-issues-inbox/applied/51673c73-b0ea-4848-bae4-83a269dfa833.json
• docs/outstanding-issues-inbox/applied/714e714b-dd1d-4a10-8f95-8552fa2c5296.json
• docs/outstanding-issues-inbox/applied/77c314b4-f2d8-4682-a08e-0f34de180f5e.json
• docs/outstanding-issues-inbox/applied/7a93a5a2-d3b9-4f3d-9747-22049300cd64.json
• docs/outstanding-issues-inbox/applied/7d1ba0dc-a3c9-479a-b16c-b1b4aa8f03d6.json
• docs/outstanding-issues-inbox/applied/83bc6aa5-e316-4524-bda8-458cea816f7a.json
• docs/outstanding-issues-inbox/applied/91536913-6cd9-4c61-a109-4d9aa3e76b9d.json
• docs/outstanding-issues-inbox/applied/9226626e-ad01-4504-a8bb-1287fa281f7b.json
• docs/outstanding-issues-inbox/applied/946d0cce-549d-4caf-b74d-af5593e0911b.json
• docs/outstanding-issues-inbox/applied/95093e96-5953-48a0-a8bc-508d625fb57e.json
• docs/outstanding-issues-inbox/applied/aaca6636-f820-4ef5-881c-752440dda09d.json
• docs/outstanding-issues-inbox/applied/abc21f52-0d39-490d-9676-d106b9af4302.json
• docs/outstanding-issues-inbox/applied/b048dbdd-7672-4e47-82e2-2211495e40c6.json
• docs/outstanding-issues-inbox/applied/d96c4613-bdfc-4e80-b084-7c27dfff1bb8.json
• docs/outstanding-issues-inbox/applied/fb87f710-b46c-452a-b349-e3ce71c36959.json
• docs/outstanding-issues-inbox/applied/ff1ea3f9-2bdc-4a9f-86de-185ec1b6c9e5.json
• docs/outstanding-issues.md

---

_{Comment @coderabbitai help to get the list of available commands.}

[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 ↗︎.