docs: reopen issue 105 after withdrawn verification

[BigSimmo]

Summary

• Reopen issue #105 because its LoadingPanel browser verification was withdrawn and remains incomplete.
• Remove the inaccurate #105 archive row introduced by merged PR fix: track upload parity deployment inputs #1482.
• Preserve the intended #085, #119, and #125 closures, the upload-limit deployment-input fix, and main’s later #136 archival.

RAG impact: no retrieval behaviour change — issue-ledger documentation and review evidence only.

Verification

• npm run check:outstanding-issues
  • 146 rows: 68 open, 78 archived; unique IDs; issues:next-id=149.
• npm run check:branch-review-ledger
  • 162 live plus 1,206 archived records; merge protection active; no malformed or duplicate records.
• npm run docs:check-links
  • 1,422 repository path references resolve.
• npm run docs:check-scripts
  • 405 npm script references resolve.
• npm run format
• Current-main reconciliation reviewed at 65635235c91527c57d33dd8311d062d28ccff6d9; no findings.

Risk and rollout

• Risk: Documentation-only correction. It restores the detailed open-row evidence from the prior corrected main state.
• Rollback: Revert this PR, though that would reintroduce the inaccurate closure.
• Provider or production effects: None.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Disclosures

• The earlier unrelated verify:ui PWA failure remains disclosed: installed Chrome reported in-incognito.
• Hosted mergeability behavior was not tested locally; GitHub is checked separately after this push.
• No provider-backed clinical, retrieval, Supabase, or deployment workflow was run.

[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:5 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: afb6f674-556d-4a3a-b8de-18d35927b67b

📥 Commits

Reviewing files that changed from the base of the PR and between 4d30646 and 75253f8.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• 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 ↗︎.