docs: archive resolved phone header flake

[BigSimmo]

Summary

• archive fix(text): follow-up — normalize indexed-page viewer text, flat-memory backfill dry-run #127 after its documented post-ci: shard Production UI, and make the phone-scroll drag report what it did #1427 close condition was satisfied
• retain the fixed short/clamped-drag mechanism and later browser/PWA no-recurrence evidence

Validation

• npm run check:outstanding-issues (pass: 61 open, 85 archived)
• npx prettier --check docs/outstanding-issues.md (pass)
• npm run check:branch-review-ledger (pass)
• git diff --check (pass)

Risk and rollback

Documentation-only issue disposition. Revert the commits to restore the open row; no runtime or provider behavior changes.

RAG impact: no retrieval behaviour change — documentation-only issue disposition.

Summary by CodeRabbit

• Documentation
  • Archived issue #127 as resolved after post-fix verification.
  • Updated the outstanding issues record to document the confirmed resolution and successful validation checks.

[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

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

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in:45 minutes

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

Run ID: 1291b04d-1e33-4731-941c-727b8cc0bbb3

📥 Commits

Reviewing files that changed from the base of the PR and between 3610f92 and 953ba8c.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

📝 Walkthrough

Walkthrough

Issue 127 was moved from the open-items table to the resolved archive, and its post-fix verification was recorded in the branch review ledger.

Changes

Issue 127 archive

Layer / File(s)	Summary
Archive and verification records docs/outstanding-issues.md, docs/branch-review-ledger.md	Issue #127 was removed from open items, added to the resolved archive with its resolution date and outcome, and recorded in the review ledger with validation checks.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• BigSimmo/Database#1428: Updates the same documentation ledger with append-only archive records.
• BigSimmo/Database#1302: Modifies both outstanding-issues and branch-review ledger tracking documents.
• BigSimmo/Database#1088: Adds resolved and review disposition rows to the same documentation ledgers.

Suggested reviewers:claude

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and clearly describes the main change: archiving the resolved phone header flake.
Description check	✅ Passed	The description includes summary, validation, and risk/rollback details; only minor template items like Notes are missing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/outstanding-issues.md`:
- Around line 168-170: Update the `#127` row’s Outcome text to accurately state
that PR `#1427` fixed or retained the short/clamped drag mechanism and that the
runway polling and delivered-travel assertions verified the issue did not recur;
remove the claim that those assertions removed the mechanism.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4d37ccab-5b0b-45ec-bf58-5136ebf355b1

📥 Commits

Reviewing files that changed from the base of the PR and between 936ec07 and 3610f92.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md