Skip to content

feat(dashboard): add the fold-detection primitives from the foldable layout RFC - #33546

Open
jeeshofone wants to merge 1 commit into
kirodotdev:mainfrom
jeeshofone:feat/fold-primitives
Open

jeeshofone wants to merge 1 commit into
kirodotdev:mainfrom
jeeshofone:feat/fold-primitives

Conversation

@jeeshofone

@jeeshofone jeeshofone commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: On a book-style foldable that reports its fold, the dashboard shows the sessions list beside the chat and ends the list at the fold, from 640px wide.

The fold-aware layout RFC (docs/request-for-change/rfc-foldable-viewport-segments.md, #29145) describes a two-pane form beside a reported fold, with the sessions list ending at the hinge. Today the dashboard reads no fold signal at all. On the iPhone Duo half-folded at 951px in Safari it shows the phone layout, because a touch-first mobile browser keeps the phone form at every width (#30619), and that rule has no fold input.

Why it matters

Half-folded like a book, the device shows two pages side by side. A one-column phone layout stretched across both bends the transcript through the hinge and hides the sessions list behind a drawer the posture is not made for.

Not a goal

  • Dialogs and sheets kept inside one segment (RFC Phase 2).
  • Padding the transcript past a hinge gap. The Duo reports no gap, so the padding is 0 there.
  • Any change for a device that reports no fold: a flat foldable at 951px, the inner display upright at 669px, and every non-folding window keep today's layout.
  • The laptop pose (two stacked segments).
  • Deleting the compact rail lock (foldHoldsRailCompact, foldCompactRail, the locked prop on RailBrandToggle) this round. If the maintainers drop item 6 when they rule on the RFC, we delete all three in that round.

What changed (motivation → approach → change)

This builds to the precedence rule in #33463, which it depends on: a reported fold at 640px and wider takes the two-pane form ahead of the touch-first phone rule. Until a maintainer signs that line, this PR waits on it.

The RFC on main still reads status: draft in its front matter and "- Status: draft. Nothing is built." in its first line, although #29145 merged and bolichen97 signed its direction.

  • website/src/hooks/useViewportSegments.ts holds the fold query, FOLD_TWO_PANE_QUERY (640px and wider), and useViewportSegments(), which returns the two segments while a fold is reported.
  • website/src/lib/touchLayoutForm.ts: touchFirstForm() returns the two-pane form when that query matches, before its touch check. Every other input gives the same answer as before. website/src/hooks/useIsMobile.ts also listens to the query, since folding at a fixed width fires no resize.
  • website/src/tailwind-theme.css and website/src/styles/shell-chrome.css: the md variant and the top bar's collapse ladder gain the same query, so the styles follow the layout below 768px too. The RFC's fold-x: variant and fold tokens are left for the first PR that reads them (dialogs and sheets, Phase 2).
  • website/src/pages/chat-sidebar/resize.ts, website/src/pages/chat/sidebarWidth.ts and website/src/pages/ChatSidebar.tsx: while folded the sessions list paints to the leading segment less the rail, and the resize handle and board widening are off, so the saved width comes back when the device is flattened. Folding mid-drag ends the drag (body styles and the dragging flag cleared) and saves nothing.
  • website/src/shell/appShell.tsx, website/src/shell/nav/navRail.tsx and website/src/shell/nav/railChrome.tsx: beside a fold the rail stays compact wherever an expanded rail would leave the leading segment less than the 180px list, and its expand toggle is disabled while that holds.
  • website/src/lib/touchLayoutForm.ts, website/src/hooks/useIsMobile.ts, website/src/pages/chat/page/sessionsDrawer.ts, website/src/pages/chat/page/ChatSidePanels.tsx and website/src/pages/ChatPage.tsx: the side panel, and any app frame in it, stays mounted across a fold. The fold rule above flips the layout form on a touch-first phone at 640px or wider, and that flip used to move the panel from its inline host to the shell's column, mounting a second panel and reloading an open MCP App frame on every fold and unfold. The panel now picks its host from the form the device would have without a fold (panelInlineHost, read from the form useIsMobile last committed), so a fold never moves it; a resize across 768px with no fold still moves it in the same commit as the form switch, as on main. src/test/ChatPage.foldAppFrame.test.tsx pins the same iframe node through a fold and an unfold, and src/test/panelInlineHost.resize.test.tsx pins the host across a 768px resize and a fold.

Backwards compatibility

Compatible: every new rule needs (horizontal-viewport-segments: 2), which only a foldable reporting a fold matches, and only with the browser's feature flag on today.

Removes nothing: on a device that reports no fold every layout decision is unchanged, and all #30619 tests in useIsMobile.touchForm.test.ts pass unchanged.

Tests

  • src/test/useIsMobile.foldTwoPane.test.ts: the Duo half-folded at 951px in a mobile-mode browser gets the two-pane form; flat at 951px it keeps the phone form; a fold at 669px is two-pane on a non-touch device too; below 640px it stays phone; folding at the same width switches the form.
  • src/test/foldSidebarWidth.test.ts and src/test/foldLocks.test.tsx: the list width at the fold, right-to-left, the 180px floor, the hidden handle, a board opened while folded, a fold mid-drag, and the disabled rail toggle.
  • src/test/viewportSegmentsParity.test.ts: pins the fold query in the hook, the md variant and the top bar ladder, and fails on any other segments query under src/.
  • src/test/useViewportSegments.test.ts: the hook's readings and listeners.
  • Three existing tests changed, each by one line. The matchMedia mocks in App.foldResize.test.tsx and ChatSidebar.createMenu.test.tsx answered the fold query as matched (one reads only its min-width term, the other answers every query alike), so they now report no fold, which is what those poses are. useTopbarCollapse.test.ts pins the ladder prelude, which now carries the fold term.

Each new guard was checked by breaking it on purpose; each break turned a test red.

Determinism: the new tests pass with --sequence.shuffle.

Manual verification

Captured on the iPhone Duo simulator (iOS 27.2, Safari 27.2, both feature flags on), in a Safari tab with demo data only, main on the left and this PR on the right. The simulator's Safari reports a coarse pointer, no hover and Mobile in its user agent, so it is a touch-first mobile browser.

  • Half-folded at 951px: main shows the phone layout; this PR shows the sessions list beside the chat, its edge at 475.3px against a fold at 475.5px.
  • Flat at 951px and upright at 669px: unchanged.

The built stylesheet grows by about 16 KB raw, 826 bytes gzipped, for the md variant's fold block.

Screenshots / video

Half-folded, 951px (main left, this PR right):

Half-folded at 951px, main on the left, this PR on the right

Flat at 951px and upright at 669px (unchanged)

Flat at 951px, main on the left, this PR on the right

Upright at 669px, main on the left, this PR on the right

Related Issues

Part of #29143

Depends on #33463 (the fold precedence line).

Head re-dated to re-dispatch the fork review lanes; tree identical to the Phase 1 commit under #38238, which adopts this sha next.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@jeeshofone
jeeshofone requested review from a team and KiroCrewCaptain as code owners November 9, 2026 01:20
@github-actions github-actions Bot added fork Pull request from a fork (external contributor) readiness: checking Automated validation is still running labels Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5, fork) — ✅ PASS

Design-level review of 41ee2fd985a1f1ac8b3da9bf8f3d9674301c5cd3 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: every new rule sits behind (horizontal-viewport-segments: 2), a flagged media feature, so it is fully reversible, and the evidence list has three downloaded screenshots.

Notes

  • This build sits on a precedence rule the description itself calls unsigned ("Until a maintainer signs that line, this PR waits on it"). If docs(rfc): record the foldable layout's Phase 0 probe readings and test table #33463 lands differently, touchFirstForm()'s new early return false is the line to revisit, along with its other readers: useKeyboardShortcuts.ts:isNarrowViewport and guideActions.ts:currentGuideViewport.
  • With panelInlineHost and the kept-open overlay in sessionsDrawer.ts, a folded touch-first phone gets the desktop form with the phone's inline panel. That mixed state is what keeps the app frame from remounting, but it is a new layout combination. Record it in website/docs/narrow-viewport.md or the RFC so the Phase 2 dialogs and sheets work builds on it knowingly.
  • The RFC on main still reads status: draft / "Nothing is built". Update it in this PR, since this PR is what builds Phase 1.

[DESIGN-REVIEWED] 41ee2fd

Description read

[DESCRIPTION-READ] 681d56fd48e51c00423f8a12a640cd62d3de45cfe27d9021463439d0f4b26d1a

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5, fork) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)

UX-level review of 41ee2fd985a1f1ac8b3da9bf8f3d9674301c5cd3 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

cannot evaluate: missing a recording of folding and unfolding. That moment turns the phone layout into the two-pane layout and back, and no still image can show whether the user sees one layout become the other.

Evidence gaps

  • Fold and unfold at a fixed width (951px). The diff starts the layout change from the new fold query: foldMql?.addEventListener?.('change', onSignal). That change runs through runLayoutFormChange's view transition. The chat pane changes size, the sessions list goes from a hidden drawer to a column, and the rail appears. ux-recordings.txt is empty. To close: attach a recording of the iPhone Duo going flat → half-folded → flat, with the side panel open.
  • Rail expand toggle disabled while folded (disabled={locked} on RailBrandToggle). Attachment 1 shows the rail compact, but no image or recording shows what happens when someone taps the brand mark while it is locked. To close: attach a recording or a still of that tap.

Notes

  • When the rail is locked, a tap on the brand mark does nothing and says nothing; only the cursor changes, through disabled:cursor-default. Keep the tooltip working in that state and have it say why the rail can't expand, for example "Unfold the device to expand the sidebar."
  • The two-pane layout itself is shown (attachment 1, right). No first-time reader has reviewed it, because this fork review runs as a single pass. A maintainer can get that blind read by pushing the branch to this repository.

[UX-REVIEWED] 41ee2fd

Description read

[DESCRIPTION-READ] dbd8b9e60af224529b87f88e84e52e8db23a2d0619cbbca3b42d39b6edc9beb7

That sha256 names everything this verdict read: the PR description, plus the 6 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5, fork) — 🔴 BLOCK

Premise-level review of 41ee2fd985a1f1ac8b3da9bf8f3d9674301c5cd3 via the fork AI-review pipeline — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: BLOCK

On a touch-first phone at 640px or wider, a reported fold now replaces the phone layout with the two-pane one, overriding the #30619 rule. That changes a default, and its only RFC is draft on base.

Notes

  • Item 9 — zero consumers: ViewportSegment.x is read only to build the cache key and in tests. foldSidebarWidth and foldHoldsRailCompact read only width. Subtraction: drop x from ViewportSegment and from read(), and key the cache on widths.
  • Item 6 — inherited: the description says the rail lock may be dropped "when they rule on the RFC". It has no recorded need of its own yet. Subtraction: defer foldCompactRail, foldHoldsRailCompact and RailBrandToggle's locked until that ruling.

What this change ships

Inventory (9 items) — 5 justified

Intent: on a book-style foldable reporting a fold, show the sessions list beside the chat, ending at the fold. ADDITION.

  1. A touch-first phone at 640px or wider with a fold reported switches from the phone layout to the two-pane one. — unjustified: product-shape change, RFC is draft
  2. A non-touch window from 640 to 767px with a fold reported gets the two-pane layout. — justified
  3. md: styles and the top bar's collapse ladder follow the fold below 768px. — justified
  4. While folded, the sessions list's width is set by the fold, and the saved width comes back on unfolding. — justified
  5. While folded, the sidebar resize handle is hidden, a board opened saves no widened width, and a drag in progress ends. — justified
  6. While folded, the rail stays compact and its expand toggle is disabled. — inherited
  7. Folding or unfolding with the side panel open leaves it, and any app frame in it, mounted where it is. — justified
  8. A source scan test fails on any other segments query under src/. — undeclared shape (TS-parser comment stripping)
  9. New useViewportSegments hook, with the posture listener and an x field. — zero consumers (x)

Blockers

product-shape change without accepted RFC — unjustified
Trigger: Item 1. touchFirstForm() now returns false when FOLD_TWO_PANE_QUERY matches, "ahead of the touch-first phone rule". The description admits "Until a maintainer signs that line, this PR waits on it." The RFC status list on base reads rfc-foldable-viewport-segments.md:status: draft.
Outcome: the default layout form for every folded device changes, and a recorded layout rule loses precedence there, with no recorded decision.
Clears when: an RFC covering a reported fold taking the two-pane form ahead of the touch-first phone rule is merged non-draft on base (then push or rebase), or a maintainer posts /ai-review override first-principles 41ee2fd985a1f1ac8b3da9bf8f3d9674301c5cd3 product-shape: <decision>.

[FIRST-PRINCIPLES-REVIEWED] 41ee2fd

Description read

[DESCRIPTION-READ] 3ca2474bb94c89916e37ca57c95412df0bebbfb95af81a8001602cf424bf8691

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review (fork) — ✅ no blocking findings

Reviewed 41ee2fd985a1f1ac8b3da9bf8f3d9674301c5cd3 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 41ee2fd

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review (fork) — ✅ no blocking findings

Reviewed 41ee2fd985a1f1ac8b3da9bf8f3d9674301c5cd3 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 41ee2fd

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 9, 2026
@jeeshofone
jeeshofone force-pushed the feat/fold-primitives branch from 181fecc to 0918b69 Compare November 9, 2026 02:01
@jeeshofone

Copy link
Copy Markdown
Contributor Author

Re the First Principles BLOCK on 181feccf68 (comment): fixed by subtraction in 0918b6984a.

Removed: FOLD_TWO_PANE_MIN, FOLD_TWO_PANE_QUERY, the fold-2pane: variant, useFoldedTwoPane(), and their tests and parity checks. The review is right that they had no consumer and went past the RFC's Phase 1 list, which is the custom variant, the tokens, the hook and their tests. They return in the surface PR for the folded two-pane form, where something uses them and their query and floor get reviewed with that design.

Kept: FOLD_X_QUERY, the fold-x: variant, the fold tokens, useViewportSegments(), and the parity test that fails when the CSS and the constant disagree. The description now matches this head.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 9, 2026
@jeeshofone
jeeshofone force-pushed the feat/fold-primitives branch from 0918b69 to ed6c843 Compare November 9, 2026 07:21
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 9, 2026
@jeeshofone

Copy link
Copy Markdown
Contributor Author

Re the First Principles BLOCK on 0918b6984a (comment), "zero consumers": ed6c843b64 adds the first consuming slice. When the device reports a fold and the window is 640px or wider, the session list sits beside the chat and ends at the fold. Every other window keeps the 768px switch point.

What now reads the fold signal:

  • FOLD_TWO_PANE_QUERY (built from FOLD_X_QUERY) is read by lib/touchLayoutForm.ts and hooks/useIsMobile.ts, which pick the shell form, and by the md variant in tailwind-theme.css and the top bar ladder in styles/shell-chrome.css.
  • useViewportSegments() is read by pages/chat-sidebar/resize.ts (the list width at the fold, the hidden resize handle) and shell/appShell.tsx (the rail held compact below 768px).

Two pieces from the original inventory still have no reader in this diff: the fold-x: variant and the four --fold-* / --segment-* tokens. I'm not claiming those are cleared.

On the RFC being draft: the description quotes the RFC's own status lines. The precedence rule this slice relies on is in #33463, waiting on a maintainer's sign-off. I haven't asked for an override.

@jeeshofone

Copy link
Copy Markdown
Contributor Author

Re the GPT 6.1 BLOCK on 0918b6984a (comment), Windows path separators in viewportSegmentsParity.test.ts: fixed in ed6c843b64. The scanner now stores each path through srcPath(), which does relative(root, full).split(sep).join('/'). A test calls it with node:path's win32 and posix implementations and checks that both give the pinned forward-slash names (TOKENS_FILE, HOOK_FILE). I haven't run it on native Windows.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 9, 2026
@jeeshofone
jeeshofone force-pushed the feat/fold-primitives branch from ed6c843 to 04ce98f Compare November 9, 2026 08:00
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 9, 2026
@jeeshofone

Copy link
Copy Markdown
Contributor Author

Re the GPT 6.1 BLOCK on ed6c843b64 (comment): a fold during a sidebar drag left the drag state stuck. Fixed in 04ce98fb8c.

  • useSidebarResize now ends the drag when foldLocked turns true mid-drag, before the handle goes. It clears the body cursor and user-select, calls onDragChange(false), and puts back the width from before the drag, so nothing is saved while folded. The unmount guard shares the same abandonDrag function.
  • onMove and onEnd do nothing once a drag has been abandoned. That covers moves or a release that still reach the hook after the handle comes back on unfolding.
  • A new test in foldLocks.test.tsx covers it: a fold mid-drag, then a move and release after unfolding. It fails if the fold-time cleanup is removed, and also if the onMove guard is removed.

@jeeshofone

Copy link
Copy Markdown
Contributor Author

Re the First Principles review of ed6c843b64 (comment):

  • Item 6, zero consumers: fixed in 04ce98fb8c. The fold-x variant, the @media (horizontal-viewport-segments: 2) token block and the parity-test cases that pinned them are gone. Everything left in the diff has a reader in it. The description says the variant and tokens wait for the first PR that reads them (RFC Phase 2).
  • The product-shape blocker (fold before the touch-first phone rule): this version doesn't answer it. The rule is written into the RFC in docs(rfc): record the foldable layout's Phase 0 probe readings and test table #33463, which waits on a maintainer's sign-off, and this PR depends on that. I haven't asked for an override.
  • Item 1, framing: the title still reads "add the fold-detection primitives". The description covers the shipped scope: the session list, the rail and touchFirstForm.

@jeeshofone

Copy link
Copy Markdown
Contributor Author

Update for First Principles: with its next push, the fold-detection commit also keeps the side panel, and any app frame in it, mounted across a fold.

Why it belongs in this commit: the fold rule here flips useIsMobile() on a touch-first phone at 640px or wider. Before this change, that flip moved the side panel from its inline host to the shell's column, so a fold or unfold mounted a second panel and an open MCP App frame loaded again from its payload. The panel now picks its host from the form the device would have without a fold (panelInlineHost in lib/touchLayoutForm.ts, read from the form useIsMobile last committed), so a fold never changes the host. A resize across 768px with no fold still moves the panel in the same commit as the form switch, as on main.

New tests: ChatPage.foldAppFrame.test.tsx (the iframe stays the same node, never hidden, through a fold and an unfold on a touch-first phone) and panelInlineHost.resize.test.tsx. The fold-precedence blocker itself is unchanged and stays the maintainers' call.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 19, 2026
@jeeshofone

Copy link
Copy Markdown
Contributor Author

Rebased onto current main with no content change (range-diff =), so the head picks up #39479, which fixes the _NOT_DUE_MEMO test-isolation failure that was turning backend shard 1 red on this stack.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 19, 2026
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 19, 2026
@jeeshofone

Copy link
Copy Markdown
Contributor Author

Fixed in 0abdc538013b, in reply to the GPT 6.1 Review finding at website/src/lib/touchLayoutForm.ts:106 (a folded pane hidden to 0x0 moved the side panel to the shell portal and reloaded the app frame).

  • panelInlineHost keeps the server-only guard (typeof window === 'undefined') on its own. A window with no viewport now reads committedUnfoldedPhoneForm(), so hiding a pane leaves the host where it was.
  • committedUnfoldedPhoneForm() also covers a pane first mounted hidden, before any form is recorded, a case the local Opus lane raised. There a 0x0 window reads as useIsMobile reads it: the touch-first answer, else the desktop form, never the narrow width query that a 0x0 window matches.

Pinned by two tests, each red with the old line restored:

  • website/src/test/ChatPage.foldAppFrame.test.tsx: after a fold, the pane is hidden to 0x0 and shown again, and the app iframe stays the same node, never in the shell column.
  • website/src/test/panelInlineHost.resize.test.tsx, with the real useIsMobile: a desktop pane first mounted hidden keeps the shell host, hidden and on its first reveal, and a desktop pane hidden after it was shown keeps it too.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Nov 19, 2026
@jeeshofone

jeeshofone commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor Author

Rebased onto current main after a conflict in navRail.tsx, with no content change: main's usage-state line is kept, with foldCompactRail beside it, and the commit's own added and removed lines are unchanged. The First Principles draft-RFC block stays the maintainers' call on #33463.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fork Pull request from a fork (external contributor) readiness: action required A blocking check or review needs attention

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants