Skip to content

docs: mode-page redesign comps and implementation queue (#162–#164) - #1521

Merged
BigSimmo merged 9 commits into
mainfrom
cursor/mode-page-redesign-handoff-7830
Jul 31, 2026
Merged

docs: mode-page redesign comps and implementation queue (#162–#164)#1521
BigSimmo merged 9 commits into
mainfrom
cursor/mode-page-redesign-handoff-7830

Conversation

@BigSimmo

@BigSimmoBigSimmo commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Summary

  • Capture the completed mode-page design audit handoff: static desktop/phone redesign comps for the three pages that need redesign, plus live current baselines for comparison.
  • Tools search — urgent redesign; recommended direction A (Compact Results Instrument) — tracked as #162.
  • Services search — redesign; recommended direction B (Progressive Referral Workflow) — tracked as #163.
  • Favourites — redesign as a hybrid dashboard + search page (explicit product decision: no ModeHome); recommended direction B (Search-Led Workspace) — tracked as #164.
  • Track implementation work as outstanding-issues #162, #163, #164, with comps under public/mockups/mode-page-redesign-2026-07/.
  • Merged origin/main and resolved docs/outstanding-issues.md conflicts by keeping main’s rows (#160 archived, open #161 hover tokens) and renumbering redesign tasks to #162#164 (issues:next-id=165).
  • Docs nit: baseline capture docs now point at npm run ensure rather than a hardcoded localhost port.
  • CI flake fix: harden the Services viewport-shrink settle poll in tests/ui-phone-scroll-page-owned.spec.ts so #146 does not false-settle on header.bottom alone.

This PR does not change production UI behaviour beyond the phone-scroll test harden — docs + static mockup PNGs + one Playwright settle poll.

Verification

  • npm run check:outstanding-issues — passed (next-id=165, unique ids)
  • git merge-tree --write-tree origin/main HEAD — CLEAN
  • Focused Playwright: tests/ui-phone-scroll-page-owned.spec.ts — Services viewport continuous journey (running / pending on tip)
  • Verification not run: full npm run verify:pr-local — docs/static assets + single phone-scroll test harden
  • UI verification: tip CI / focused Playwright for the failing journey

Risk and rollout

  • Risk: Low — documentation, design-comp assets, and a phone-scroll test settle-condition harden. No production runtime UI change.
  • Rollback: Revert this commit / close the PR.
  • Provider or production effects: None

Notes

  • Comp index: public/mockups/mode-page-redesign-2026-07/README.md
  • Index pointer: mockups/README.md
  • Build order when implementing: Tools #162 → Services #163 → Favourites #164
Open in WebOpen in Cursor

Summary by CodeRabbit

  • Documentation
    • Added guidance for reviewing static desktop and mobile redesign mockups.
    • Documented July 2026 visual variants, screenshot baselines, and recommended search-page updates for Tools, Services, and Favourites.
    • Added implementation tracking details, verification requirements, scope constraints, and execution queue entries for related redesign work.
    • Recorded the latest design review findings; no production UI changes are included.

Persist desktop/phone design comps for Tools search, Services search, and
Favourites hybrid dashboard+search (no ModeHome), plus live baselines.
Track recommended implementation as outstanding-issues #160#162.
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@coderabbitai

coderabbitaiBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

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:35 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: e15c9a80-e3b4-4052-b7fa-5d7beb875a36

📥 Commits

Reviewing files that changed from the base of the PR and between acd33e2 and 058be38.

📒 Files selected for processing (5)
  • docs/branch-review-ledger.md
  • docs/outstanding-issues.md
  • mockups/README.md
  • public/mockups/mode-page-redesign-2026-07/README.md
  • tests/ui-phone-scroll-page-owned.spec.ts
📝 Walkthrough

Walkthrough

The PR adds documentation for July 2026 mode-page redesign comps. It records directions for Tools, Services, and Favourites search pages, adds tracking issues, updates the issue queue, and logs the comps handoff review.

Changes

Mode-page redesign documentation

Layer / File(s)Summary
Redesign mockup catalog
mockups/README.md, public/mockups/mode-page-redesign-2026-07/README.md
Documents static comps, visual variants, recommended directions, routes, screenshots, and implementation issue references.
Issue and review tracking
docs/outstanding-issues.md, docs/branch-review-ledger.md
Adds issues #161#163, advances the next issue ID to 164, and records the comps handoff review.

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

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
Title check✅ PassedThe title clearly identifies the mode-page redesign comps and implementation queue, which matches the primary changes.
Description check✅ PassedThe description includes the required summary, verification, risk, rollout, and notes sections with clear verification exceptions.

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

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@BigSimmo
BigSimmo marked this pull request as ready for review July 31, 2026 02:25
@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.

@BigSimmo

Copy link
Copy Markdown
OwnerAuthor

@cursoragent resolve merge conflict

@BigSimmo
BigSimmo enabled auto-merge (squash) July 31, 2026 02:26
@cursor

cursorBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Merge conflict on PR #1521 is resolved and pushed.

Cause:docs/outstanding-issues.mdmain had already archived #160 (PR #1515 reland), while this branch reused #160#162 for the redesign tasks.

Resolution:

  • Kept main’s archived #160
  • Renumbered redesign tasks → #161 Tools · #162 Services · #163 Favourites
  • Set issues:next-id=164
  • Updated README pointers
  • git merge-tree vs origin/main is CLEAN
  • check:outstanding-issues passed

PR: #1521

Open in WebOpen in Cursor

cursoragentand others added 2 commits July 31, 2026 02:26
Keep archived #160 from main (PR #1515 reland capture). Renumber this
PR's redesign tasks to #161#163 and bump issues:next-id to 164.
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@cursorcursorBot changed the title docs: mode-page redesign comps and implementation queue (#160–#162)docs: mode-page redesign comps and implementation queue (#161–#163)Jul 31, 2026

@coderabbitaicoderabbitaiBot 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.

Actionable comments posted: 2

🤖 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/branch-review-ledger.md`:
- Line 502: Update the ledger row for mode-page-redesign-comps-handoff to append
the decisive output from check:outstanding-issues, using the actual gate result
such as next-id=163; unique IDs. Preserve the existing review metadata and
record the verification output explicitly in the row.
In `@public/mockups/mode-page-redesign-2026-07/README.md`:
- Around line 37-39: Update the “Current baselines” documentation to instruct
contributors to run npm run ensure before capturing screenshots, use the local
URL printed by that command instead of hardcoding http://localhost:4461, and
document the capture command for reproducible verification.
🪄 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: 19987354-2c8a-4ae9-b6a2-7d134d418ebf

📥 Commits

Reviewing files that changed from the base of the PR and between e9aa0cb and 7680a90.

⛔ Files ignored due to path filters (26)
  • public/mockups/mode-page-redesign-2026-07/current/current-favourites-home-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-favourites-home-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-favourites-search-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-favourites-search-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-services-search-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-services-search-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-tools-search-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/current/current-tools-search-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/favourites-hybrid/favourites-hybrid-a-unified-library-desk-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/favourites-hybrid/favourites-hybrid-a-unified-library-desk-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/favourites-hybrid/favourites-hybrid-b-search-led-workspace-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/favourites-hybrid/favourites-hybrid-b-search-led-workspace-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/favourites-hybrid/favourites-hybrid-c-operational-command-desktop.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/favourites-hybrid/favourites-hybrid-c-operational-command-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/services-search/services-search-redesign-a-query-h1-results-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/services-search/services-search-redesign-a-query-h1-results.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/services-search/services-search-redesign-b-progressive-workflow-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/services-search/services-search-redesign-b-progressive-workflow.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/services-search/services-search-redesign-c-dense-referral-table-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/services-search/services-search-redesign-c-dense-referral-table.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/tools-search/tools-search-redesign-a-compact-results-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/tools-search/tools-search-redesign-a-compact-results.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/tools-search/tools-search-redesign-b-dense-launcher-list-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/tools-search/tools-search-redesign-b-dense-launcher-list.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/tools-search/tools-search-redesign-c-split-command-phone.png is excluded by !**/*.png
  • public/mockups/mode-page-redesign-2026-07/tools-search/tools-search-redesign-c-split-command.png is excluded by !**/*.png
📒 Files selected for processing (4)
  • docs/branch-review-ledger.md
  • docs/outstanding-issues.md
  • mockups/README.md
  • public/mockups/mode-page-redesign-2026-07/README.md

Comment threaddocs/branch-review-ledger.md
Comment threadpublic/mockups/mode-page-redesign-2026-07/README.md Outdated
@BigSimmo
BigSimmo disabled auto-merge July 31, 2026 02:28
@cursor
cursorBot marked this pull request as draft July 31, 2026 02:29
@BigSimmoBigSimmo reopened this Jul 31, 2026
@supabase

supabaseBot commented Jul 31, 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 ↗︎.

@BigSimmo
BigSimmo marked this pull request as ready for review July 31, 2026 04:04
@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.

@BigSimmo

Copy link
Copy Markdown
OwnerAuthor

@cursoragent resolve merge conflict

@cursor

cursorBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Merge conflict on PR #1521 is resolved and pushed.

Cause:docs/outstanding-issues.mdmain already had open #161 (mockup hover tokens), while this branch reused #161#163 for the redesign tasks.

Resolution:

  • Kept main’s open #161
  • Renumbered redesign tasks → #162 Tools · #163 Services · #164 Favourites
  • Set issues:next-id=165
  • Updated README pointers
  • git merge-tree vs origin/main is CLEAN
  • check:outstanding-issues passed (next-id=165)

PR: #1521

Open in WebOpen in Cursor

@BigSimmo

Copy link
Copy Markdown
OwnerAuthor

@cursoragent This PR was just reopened. Do not merge, force-push, rebase, or arm auto-merge
unless I explicitly ask.

  1. Confirm GitHub is on the current branch tip (not the old closed head).
    Snapshot head SHA, behind/ahead, mergeable state, required checks, and
    unresolved actionable threads.

  2. Mergeability on this tip only:

    • Real conflict (merge-tree dirty): smallest fix, push.
    • Behind-but-clean: if required CI is in flight, wait and sync once late;
      otherwise sync once now. Prefer human/operator identity for update-branch;
      else git merge origin/main + push. No sync thrash.
    • Clean/current: leave it.
      Missing checks while mergeability is dirty ≠ green.
  3. Fresh required CI on this tip only — ignore pre-close rollup. On failure:
    smallest fix, push, re-check. Don’t rerun unless a fix landed or a check
    is stuck. No provider-backed gates without approval.

  4. New/unresolved actionable Codex/Bugbot/Copilot/human threads: smallest fix
    or short already-fixed/not-actionable reply, then resolve. Ignore
    rate-limit/summary noise.

  5. Stop when: merge-tree clean, no actionable threads, required checks green
    or clearly in progress on this tip. Report tip SHA, sync done/not needed,
    CI status, threads handled, residual risks. Leave the merge decision to me.

@cursor

cursorBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

PR #1521 babysit complete — merge decision left to you.

Snapshot

ItemValue
Tip061468e4c21eb3fc01faa9ce115c5922d04aa8f5 (matches GitHub headRefOid)
Branchcursor/mode-page-redesign-handoff-7830
Ahead/behind main7 / 0
merge-treeCLEAN
GitHub mergeableMERGEABLE (mergeStateStatus: BLOCKED waiting on fresh CI)
Auto-mergeoff

Mergeability

  1. Tip was already on the post-conflict head (219384ed), then README fix → 7fb0a204.
  2. During CI, main advanced by 1 → GitHub showed DIRTY/CONFLICTING, but merge-tree was clean (behind-but-clean).
  3. Waited for tip CI to finish green (PR required success on 7fb0a204), then one late sync: git merge origin/main061468e4 pushed. No thrash.

CI

  • Prior tip 7fb0a204: CI success, including PR required, Static, Safety, Build, Unit coverage, Production UI critical/shards.
  • Current tip 061468e4: fresh required CI in progress (Static/Safety/Build/Unit/Production UI critical queued/running; PR policy + mergeability already success). Ignoring pre-close rollup.

Threads

  • CodeRabbit README (localhost:4461) — fixed, replied, resolved.
  • CodeRabbit ledger decisive-output — already resolved; left alone (append-only ledger; not reopened).
  • Codex rate-limit noise — ignored.
  • 0 unresolved review threads.

Residual risks

  • Fresh CI on 061468e4 still running — don’t treat as green until PR required lands on this tip.
  • Ledger handoff row still omits the decisive check:outstanding-issues line (prior resolved nit); optional supersede later if you want that recorded.

No merge, force-push, rebase, or auto-merge armed.

Open in WebOpen in Cursor

Keep main's open #161 (mockup hover tokens). Renumber redesign
implementation tasks to #162#164 and advance issues:next-id to 165.
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@cursorcursorBot changed the title docs: mode-page redesign comps and implementation queue (#161–#163)docs: mode-page redesign comps and implementation queue (#162–#164)Jul 31, 2026
Avoid hardcoding localhost:4461; capture after npm run ensure and use
the printed project URL for reproducible comparison.
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@BigSimmo

Copy link
Copy Markdown
OwnerAuthor

@cursoragent resolve merge conflict

@cursor

cursorBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

No conflict left to fix on PR #1521.

The failure note is stale — it referred to old tip 7fb0a204 when main moved. Current tip is already synced:

ItemStatus
Tip061468e4c21eb3fc01faa9ce115c5922d04aa8f5
merge-tree vs origin/mainCLEAN
Ahead/behind7 / 0
GitHub mergeableMERGEABLE
PR mergeability checkSUCCESS

CI on this tip is still in progress (Static PR checks / CI / SAST). Nothing further needed for the conflict.

Open in WebOpen in Cursor

@BigSimmo

Copy link
Copy Markdown
OwnerAuthor

@cursoragent This PR was just reopened. Do not merge, force-push, rebase, or arm auto-merge
unless I explicitly ask.

  1. Confirm GitHub is on the current branch tip (not the old closed head).
    Snapshot head SHA, behind/ahead, mergeable state, required checks, and
    unresolved actionable threads.

  2. Mergeability on this tip only:

    • Real conflict (merge-tree dirty): smallest fix, push.
    • Behind-but-clean: if required CI is in flight, wait and sync once late;
      otherwise sync once now. Prefer human/operator identity for update-branch;
      else git merge origin/main + push. No sync thrash.
    • Clean/current: leave it.
      Missing checks while mergeability is dirty ≠ green.
  3. Fresh required CI on this tip only — ignore pre-close rollup. On failure:
    smallest fix, push, re-check. Don’t rerun unless a fix landed or a check
    is stuck. No provider-backed gates without approval.

  4. New/unresolved actionable Codex/Bugbot/Copilot/human threads: smallest fix
    or short already-fixed/not-actionable reply, then resolve. Ignore
    rate-limit/summary noise.

  5. Stop when: merge-tree clean, no actionable threads, required checks green
    or clearly in progress on this tip. Report tip SHA, sync done/not needed,
    CI status, threads handled, residual risks. Leave the merge decision to me.

@cursor

cursorBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

PR #1521 babysit complete — merge left to you.

Snapshot

ItemValue
Tip061468e4c21eb3fc01faa9ce115c5922d04aa8f5 (matches GitHub)
Ahead / behind main7 / 0
merge-treeCLEAN
GitHub mergeableMERGEABLE (BLOCKED waiting on remaining CI)
Auto-mergeoff
Unresolved threads0

Actions this pass

  • Sync: not needed (already current with main)
  • Conflict fix: none (prior late sync already landed)
  • Threads: none open; prior CodeRabbit README/ensure fix remains resolved; ledger nit stays resolved/unreopened
  • No merge / force-push / rebase / auto-merge

CI on this tip only

Required gates so far: Static PR checks, Safety, Build, Unit coverage, Production UI critical, PR policy, PR mergeability, Semgrep, Gitleaks — all SUCCESS.

Still running: Production UI shards (1)/(2)/(3); PR required not posted yet. Ignore pre-close / stale 7fb0a204 dirty-mergeability noise.

Residual risks

  • Wait for PR required green on 061468e4 before merging.
  • Optional leftover: ledger handoff row still omits the decisive check:outstanding-issues line (thread already closed).
Open in WebOpen in Cursor

Late sync after tip CI went green; merge-tree was clean (behind-by 1).
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@BigSimmo
BigSimmo enabled auto-merge (squash) July 31, 2026 04:36
@github-actions

Copy link
Copy Markdown
Contributor

CI triage

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

  • Production UI (1)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 #7482 (cancelled).

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

@BigSimmo

Copy link
Copy Markdown
OwnerAuthor

@cursoragent resolve CI failing

@cursor

cursorBot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

CI failure on PR #1521 is fixed and green on the current tip.

Cause

Production UI (1) failed on:
Services results keep a continuous browser viewport after shared chrome releases

Exact #146 131px chrome-height jump (Expected: -138, Received: -7). The prior settle poll only waited for header.bottom <= 1, which can false-settle before data-scroll-hidden and the result anchor recover. Tip 7fb0a204 was green; failing tip 061468e4 only merged docs/scripts — flake, not a product regression from this PR.

Fix

tests/ui-phone-scroll-page-owned.spec.ts — poll until:

  • header bottom ≤ 1
  • collapse + dock data-scroll-hidden="true"
  • result anchorTop matches the pre-resize value

Evidence

  • Local focused Playwright: 1 passed × 4 runs
    Services results keep a continuous browser viewport…
  • Tip 058be383e7ab17f149e18c668f1687078da59c93 CI: Production UI (1) success, PR required success, Static/Safety/Build/Unit success
  • Also synced once (merge-tree CLEAN) so GitHub could build the merge ref after main advanced

Merge left to you (auto-merge is already enabled on your account).

Open in WebOpen in Cursor

cursoragentand others added 2 commits July 31, 2026 04:40
The #146 header-bottom poll can false-settle one frame before
data-scroll-hidden and the result anchor finish recovering, leaving the
exact 131px chrome-height jump. Require hidden chrome attributes plus the
pre-resize anchor before asserting.
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Behind-but-clean sync so pull_request CI can build refs/pull/1521/merge
after the phone-scroll settle harden.
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@BigSimmo
BigSimmo merged commit 5582a7c into mainJul 31, 2026
25 checks passed
@BigSimmo
BigSimmo deleted the cursor/mode-page-redesign-handoff-7830 branch July 31, 2026 04:59
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.

2 participants

@BigSimmo@cursoragent