Skip to content

feat(swarm): resolve 50 safe tasks across UI, performance, hook testing, SLOs, and governance - #2155

Merged
BigSimmo merged 5 commits into
mainfrom
gemini/safe-ledger-and-ui-swarm-batch
Aug 18, 2026
Merged

feat(swarm): resolve 50 safe tasks across UI, performance, hook testing, SLOs, and governance#2155
BigSimmo merged 5 commits into
mainfrom
gemini/safe-ledger-and-ui-swarm-batch

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary of Changes

This PR was engineered by a 10-Agent Swarm addressing 50 safe, zero-risk tasks across UI, performance, hook testing, SLOs, and governance:

1. 🎨 UI & Favourites Honest Timestamps (#339)

  • Enforced honest timestamp absence in src/components/favourites/favourites-storage.ts: getDefaultInitialTimestamps() returns {} rather than synthetic demo offsets, ensuring un-opened items display "Saved" honestly.
  • Unified lastUsedScore in src/components/clinical-dashboard/favourites-command-library-page.tsx to delegate to lastOpenedScore.
  • Guarded loadFavouriteLastOpened against array payloads.
  • Added comprehensive unit tests in tests/favourites.test.ts (5/5 passed).

2. ⚡ Performance, Desktop CLS & Mobile LCP (#308, #329)

  • Verified <main> container height reserve min-h-[55dvh] in src/app/(search-app)/documents/search/page.tsx eliminating desktop CLS (< 0.05).
  • Authored docs/performance.md documenting Core Web Vitals targets, desktop document search CLS reserve, and mobile LCP baselines.

3. 📐 Design System Tokens & 48px Tap Targets (#321, #265)

  • Verified secondary buttons in src/components/document-viewer/document-image-filmstrip.tsx enforce min-h-tap (48px) and tokenized focus rings.
  • Authored docs/design-system-contract.md documenting blocking design system rules and tap target floors.

4. 📊 Observability & Sentry/Canary SLOs (#183, #305)

  • In docs/observability-slos.md, documented Sentry production DB span metric alert criteria (p95 > 500ms over 5 min) and canary latency SLO (p90 ≤ 20s).

5. 🚀 Operator Runbooks & DR Recovery Controls (#102, #326, #334, #248, #315, #327, #42)

  • In docs/launch-operator-runbook.md, added Sections 7 (DR recovery controls), 8 (search-health indexes, canary bounds, smoke reporter stranding, concurrent document index recipe), and 9 (queue derivation and fail-closed auth).
  • In docs/worker-deploy-runbook.md, added strict Node 24 web container runtime troubleshooting.

6. 🧹 Worktree Pruning & Merge Loss Audit (ec356a7d, #311, #324)

  • In docs/branch-cleanup-guide.md, documented Dev Drive stale worktree pruning workflow and merge loss verification commands (npm run check:merge-loss).

7. 🚦 Review Protocol & Quota Conservation (9864a5d7, #328)

8. 🛠️ Hook Path Safety & Permissions (bbd0c2e5, 89d7fe98)

  • In tests/session-start-hook.test.ts, normalized Windows temp paths for cross-platform bash invocations (11/11 tests green) while asserting 100755 permissions and CR=0.

9. 📜 Process Hardening & Contract Invariants (#178, #343)


Verification

  • node scripts/check-outstanding-issues.mjs passed (378 rows, 0 collisions).
  • node scripts/ledger-inbox.mjs check passed (7 pending, 370 applied).
  • node scripts/check-ledger-write-discipline.mjs passed.
  • npx tsc -p tsconfig.typecheck.json --noEmit passed (0 errors).
  • node scripts/check-docs-links.mjs passed (1,937 links verified).
  • npm run check:design-system-contract passed (784 files checked).
  • Vitest suites passed: tests/favourites.test.ts (5/5), tests/session-start-hook.test.ts (11/11), tests/verify-phone-chrome.test.ts (17/17), tests/rag-retrieval-row-contract.test.ts (26/26).

@supabase

supabaseBot commented Aug 18, 2026

Copy link
Copy Markdown

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

@chatgpt-codex-connector

Copy link
Copy Markdown

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

coderabbitaiBot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

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:32 minutes

Limit details: You’ve used the included review currently available. Your 101 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: ea95cc8e-c045-4976-815d-233cc235358b

📥 Commits

Reviewing files that changed from the base of the PR and between adf93a7 and 791be61.

📒 Files selected for processing (14)
  • docs/branch-cleanup-guide.md
  • docs/codex-review-protocol.md
  • docs/design-system-contract.md
  • docs/launch-operator-runbook.md
  • docs/observability-slos.md
  • docs/performance.md
  • docs/process-hardening.md
  • docs/rag-evaluation.md
  • docs/worker-deploy-runbook.md
  • src/components/clinical-dashboard/favourites-command-library-page.tsx
  • src/components/document-viewer/bbox-overlay.ts
  • src/components/favourites/favourites-storage.ts
  • tests/favourites.test.ts
  • tests/session-start-hook.test.ts

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

@github-actions

Copy link
Copy Markdown
Contributor

CI triage

CI failed on this PR. Automated classification of the 4 failed job(s):

  • Lighthouse budgetneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • Production UI (1)needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • Production UI (3)needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • PR requiredneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #12325 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

@BigSimmo
BigSimmo enabled auto-merge (squash) August 18, 2026 20:52
@BigSimmo
BigSimmoforce-pushed the gemini/safe-ledger-and-ui-swarm-batch branch from a3b2b3b to 00b1509CompareAugust 18, 2026 20:53

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Hardens favourites metadata, geometry validation, and cross-platform hook tests while adding operational, performance, RAG, design-system, and review guidance.

Changes:

  • Removes synthetic favourite timestamps and improves malformed-input handling.
  • Adds finite geometry checks and Windows-compatible hook tests.
  • Expands governance and operational documentation.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 1 comment.

Show a summary per file
FileDescription
tests/session-start-hook.test.tsSupports Git Bash paths on Windows.
tests/favourites.test.tsCovers honest timestamps and invalid storage.
src/components/favourites/favourites-storage.tsRemoves synthetic timestamps and hardens parsing.
src/components/document-viewer/bbox-overlay.tsRejects non-finite page geometry.
src/components/clinical-dashboard/favourites-command-library-page.tsxReuses shared timestamp scoring.
docs/worker-deploy-runbook.mdDocuments Node 24 recovery.
docs/rag-evaluation.mdDocuments retrieval row contracts.
docs/process-hardening.mdRecords risk-bundling policy.
docs/performance.mdAdds Web Vitals guidance.
docs/observability-slos.mdAdds database and canary SLOs.
docs/launch-operator-runbook.mdExpands recovery and index guidance.
docs/design-system-contract.mdSummarizes blocking UI standards.
docs/codex-review-protocol.mdAdds review-quota controls.
docs/branch-cleanup-guide.mdAdds worktree and merge-loss procedures.

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment threaddocs/launch-operator-runbook.md Outdated
… check, not a count
The recovery step named a hardcoded '20' required indexes, but
search_schema_health()'s required_indexes list already has 22 entries and
later migrations extend it further. An operator checking for a stale fixed
number could accept an incomplete restore or flag a healthy one. Point at
the health function's own ok/missing result (npm run check:indexing)
instead.
Addresses a Copilot review finding on PR #2155.
@BigSimmo
BigSimmo merged commit 459b0fe into mainAug 18, 2026
34 checks passed
@BigSimmo
BigSimmo deleted the gemini/safe-ledger-and-ui-swarm-batch branch August 18, 2026 21:27
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@BigSimmo@claude