docs(issues): capture CI/merge findings and a merged-PR gate gap from PR babysitting

[BigSimmo]

Summary

• Records two operational findings from today's PR-babysitting session (CI testing approach review: flake, waste, and when-to-run matrix #1406/fix(mode-nav): size slots to their content so labels stop being clipped #1405/docs(agents): add PR bundling rule to cut one-task-one-PR churn #1408) in docs/outstanding-issues.md, per the repo's outstanding-work ledger convention.
• #126 (renumbered from #117 after a concurrent collision with PR docs(issues): archive #113 and #114, open #117 for the stale spec reference #1420's own #117/#125 — see Notes): this repo's ci.ymlon: pull_request block has no explicit types:, which defaults to GitHub's [opened, synchronize, reopened]. ready_for_review is not in that list, so marking a draft PR ready does not by itself retrigger the full required-check suite — PR CI testing approach review: flake, waste, and when-to-run matrix #1406 sat with only 3-4 minimal checks for 30+ minutes until an actual new commit (a synchronize event) landed. Distinct from the already-tracked #116 (a real merge conflict silences pull_request-triggered CI entirely) — this is a missing trigger type on a conflict-free, ready-to-check PR.
• #127 (renumbered from #118): GitHub's update-branch API doesn't honor this repo's merge=union.gitattributes driver on docs/branch-review-ledger.md. On PR CI testing approach review: flake, waste, and when-to-run matrix #1406 the API 422'd with "merge conflict between base and head" while git merge-tree --write-tree origin/main confirmed a clean merge — GitHub's server-side merge implementation doesn't read custom merge drivers, so it saw a real textual conflict at the exact hunk local git's union driver auto-resolves. Worked around by merging origin/main locally and pushing directly.
• #128 (new, added while re-checking PR fix(chrome): overlay the phone header so hiding it never moves content #1396 during babysitting): PR fix(chrome): overlay the phone header so hiding it never moves content #1396 repeatedly declared a physical-device Safari/PWA acceptance checklist (docs/phone-chrome-physical-acceptance.md) as required before merge — restated three times across its own review thread, including after its final fix — because headless Chromium cannot certify Safari chrome minimisation or cold-launch PWA paint. It merged anyway with the checklist still a blank template and no device evidence anywhere. Also notes a related pre-paint/cold-load hydration test the same PR's review flagged as missing but never filed. This is a real, unaddressed governance gap on a merged shared-chrome change, not a formality.

Verification

• npm run check:outstanding-issues — self-test passed; guard passed: 123 rows (61 open, 62 archived), unique ids, next-id=129 above the highest
• npx prettier --check docs/outstanding-issues.md — clean
• Verification not run: npm run verify:ui / eval:* / check:production-readiness — no UI, retrieval, ranking, ingestion, privacy, or Supabase behavior changed; this is a ledger-only docs append.

RAG impact: no retrieval behaviour change — no file under src/lib/rag/**, clinical-search, retrieval-selection, ranking-config, the eval harness, the golden fixture, or the retrieval RPCs is touched.

Risk and rollout

• Risk: none to runtime or CI. Documentation/memory-ledger change only; no script, workflow, or gate behavior changed.
• Rollback: revert the commit; nothing depends on it. The ledger is not strictly append-only like docs/branch-review-ledger.md, but no existing row was edited — only new rows appended and the next-id marker bumped.
• Provider or production effects: None. No provider-backed command was run.

Clinical Governance Preflight

Not applicable — the diff touches only docs/outstanding-issues.md. No ingestion, answer generation, search/ranking, source rendering, document access, privacy, production environment, or clinical output behavior is touched.

Notes

• Checked for a next-id allocation race before pushing (per the repo's own #112 finding about exactly this race): confirmed origin/main's marker was still 117 immediately before the first push, so #117/#118 were free at that time. A concurrently-open draft PR (#1420) also claimed #117 for an unrelated finding and landed first on main — exactly the race this row's own #112 predicted. Codex flagged this PR's #117/#118 wording separately (both fixed and resolved — see thread history); a follow-up commit from another session then renumbered this PR's rows to #126/#127 and bumped the marker to 128 once the collision materialized, verified clean (check:outstanding-issues passed, no duplicate ids). #128 was added afterward while re-checking PR fix(chrome): overlay the phone header so hiding it never moves content #1396 during the same babysitting pass.

---

Generated by Claude Code

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

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (1)

• docs/outstanding-issues.md

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9cb2264e-58d2-48de-8bc9-6d4d6934cda3

📥 Commits

Reviewing files that changed from the base of the PR and between c0ceee2 and d2568ce.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The outstanding-issues ledger advances its next-ID marker to 119 and adds open items #117 and #118 covering draft-to-ready CI triggering and update-branch merge conflicts.

Changes

Outstanding issues ledger

Layer / File(s)	Summary
Update issue tracking ledger docs/outstanding-issues.md	Advances the issues:next-id marker to 119 and adds open items #117 and #118 with their respective remediation details.

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

Possibly related PRs

• BigSimmo/Database#1410: Adds validation for the outstanding-issues marker and table integrity.
• BigSimmo/Database#1109: Updates tooling that parses and surfaces the outstanding-issues ledger.
• BigSimmo/Database#1043: Makes similar next-ID and Open items ledger updates.

Suggested reviewers:claude, cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title matches the doc-only change and highlights the CI/merge findings and gate gap.
Description check	✅ Passed	The description follows the template and includes summary, verification, risk/rollout, governance, and notes with the required details.

---

_{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:c0ceee291d

ℹ️ 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".