Skip to content

fix(mobile): make the phone-connect QR code scannable by phone cameras - #14205

Merged
iamwhatever merged 1 commit into
kirodotdev:mainfrom
unstablebrainiac:fix/phone-connect-qr-scannable
Sep 26, 2026
Merged

iamwhatever merged 1 commit into
kirodotdev:mainfrom
unstablebrainiac:fix/phone-connect-qr-scannable

Conversation

@unstablebrainiac

@unstablebrainiac unstablebrainiac commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

The phone-connect QR code shows on screen, but a phone camera does not pick it up (#13510). The code is drawn far below its real size. The server encodes it at 8px per module, and both places that show it squeeze that 648px image into a fixed box: 176px in the connect dialog, 180px on the Overview page's phone access card. Each module ends up about 2px wide and blurred.

Why it matters

Scanning this code is how a user opens Kiro Crew on a phone over the tailnet. When the camera cannot read it, the feature does not work, and the fallback is moving a link that carries a live session token to the phone by hand.

What changed (motivation → approach → change)

A phone camera can now read the phone-connect QR code. Both surfaces show it at its natural size, and every module (one black or white square) is a whole number of screen pixels.

Before After
Code width, connect dialog 176px (a 648px PNG, scaled to 27% with smoothing) 324px (the PNG's own size)
Code width, Overview card 164px inside its 180px frame (scaled to 25% with smoothing) 324px (the PNG's own size)
One module on screen about 2 CSS px, blurred 4 CSS px, sharp (8 device px on a 2x screen)

An access URL carries a signed token, so its code runs to about 80 modules. At 8px per module that is about twice the dialog's width, and any fixed box smaller than the image rescales it by a fractional factor.

tailnet_mobile.py now asks the shared encoder in qr.py for 4px modules, through a new keyword-only box_size whose default stays 8. MobileConnectModal.tsx and TailnetMobileCard.tsx, the two places that show this code, drop their fixed sizes and show the PNG as it is. Pixelated scaling keeps the upscale on a high-density screen sharp, and max-w-full only shrinks a code wider than its container. The encoder keeps its 2-module quiet zone: the white padding both surfaces draw around the code brings the light margin to at least 4 modules.

This fixes the phone-connect code only. Two other panels still draw a QR code into a fixed 180px box: the WeChat login panel (WeixinPanel.tsx) and the WhatsApp pairing panel (WhatsAppPanel.tsx). Both still read in the same camera model, WeChat down to P = 0.5 and WhatsApp to 0.7, so they are left as they are.

Backwards compatibility

Compatible: render_qr_data_uri gains a keyword-only box_size whose default leaves every other caller's output byte-identical, the WeChat login code included.

Tests

  • test/test_qr.py (new): box_size sets whole pixels per module; the default output is unchanged for other callers; the mobile module size is 4px, and a realistic access URL at that size fits the dialog's 370px QR box unscaled.
  • test/test_tailnet_mobile.py: the QR handler asks the encoder for the mobile module size.
  • website/src/components/MobileConnectModal.test.tsx and website/src/components/TailnetMobileCard.test.tsx: the QR image has no fixed width or height and carries max-w-full and pixelated scaling.

Each one fails with its production change reverted: the encoder and handler tests fail without the box_size keyword, and each component test fails against main's fixed-size image.

Manual verification

Rendered the real MobileConnectModal and TailnetMobileCard in Chromium, with the tailnet endpoints stubbed and the encoder's PNG for a 373-character access URL, at 2x and 1x in both themes. On main, the dialog draws the 648px PNG at 176px and the card at 164px, both with image-rendering: auto. With this change, both draw the 324px PNG at 324px, pixelated.

Then decoded the rendered codes with ZXing (zxing-cpp 2.2.0) through a simple camera model: shrink the 2x screenshot to P camera pixels per CSS pixel with area resampling, add a slight blur, decode, and find the smallest P that still gives back the exact URL.

Code Main This PR
Connect dialog 0.85 0.45
Overview card 0.8 0.45

Both phone-connect surfaces now read at about half the camera resolution, which means from roughly twice as far away.

Two edge cases, measured the same way. At a 390px-wide window the dialog is narrower than the code, so max-w-full shrinks it to 281px: it stays free of gray pixels and still decodes down to P = 0.45. At 320px the code shrinks to 218px and its white frame still fits inside the dialog, with no horizontal scrolling. At 2x, drawing the code with image-rendering: auto instead leaves 22% of its pixels gray; pixelated leaves none.

The images no longer carry a fixed width and height, so their box comes from the PNG itself. Chromium resolves a data: PNG's size before the first frame that paints it: in 80 insertions of a 324px code at 1x and 2x, some made inside an animation-frame callback just before a paint, the first painted box was always the full 324px, so the controls below the code do not jump.

Not verified: a scan with a physical phone, and that first-frame check in Firefox and Safari; this environment can run neither.

Screenshots / video

Connect dialog on main: the 648px code squeezed into a 176px box.

Connect dialog on main, dark theme, with a small QR code

Connect dialog with this change: the code at its natural 324px.

Connect dialog with this change, dark theme, with a large sharp QR code

Overview card on main, then with this change:

Overview phone access card on main, dark theme, with a small QR code

Overview phone access card with this change, dark theme, with a large sharp QR code

Light theme: connect dialog and Overview card

Connect dialog with this change, light theme

Overview phone access card with this change, light theme

Related Issues

Fixes #13510

Pattern harvest

Rule candidate: review-prompt
Pattern: a machine-read image (QR code, barcode) drawn into a fixed box at a fractional scale of its natural size

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

@unstablebrainiac
unstablebrainiac requested review from a team and chenmingwei23 September 26, 2026 10:48
@github-actions github-actions Bot added fork Pull request from a fork (external contributor) readiness: action required A blocking check or review needs attention labels Sep 26, 2026
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author

Intent: Make the phone-connect QR code readable by a phone camera on both surfaces that show it, the connect dialog and the Overview phone access card, by drawing it at its natural size with whole-pixel modules and the spec's 4-module quiet zone.
Not a goal: Changing what the code encodes, the sign-in token or its lifetime, or the WeChat panel's layout.

@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 Sep 26, 2026
@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Fable 5, fork) — ✅ PASS

Design-level review of 907fb9eba4a0cefd92fe86a19e31e274735bcc47 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Verify the code still lays out without a jump in Firefox/Safari — the removed width/height first-paint check is Chromium-only.

[DESIGN-REVIEWED] 907fb9e

@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Fable 5, fork) — 🟡 CONCERNS

UX-level review of 907fb9eba4a0cefd92fe86a19e31e274735bcc47 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

No first-time reader has seen the resized QR surfaces — this lane's cap; screenshots otherwise cover both surfaces, both themes, before and after.

Watch

  • The narrow-window state is claimed, not shown: max-w-full re-shrinks the code fractionally below ~370px (PR: "shrinks it to 281px"), the exact defect class this PR fixes; decodability was measured (P = 0.45) but no still shows it. Rare (narrow windows only) × task failure if wrong × persistent. Fix: commit the 390px screenshot alongside the others.
  • Dropping fixed width/height makes first-paint layout depend on data:-URI sizing, verified in Chromium only (PR: "Not verified … in Firefox and Safari"); if it resolves late there, the Copy link/New code controls jump as the code paints. Fix: a human spot-check in one of the two before merge.

[UX-REVIEWED] 907fb9e

@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

GPT 5.6 Review (fork) — ✅ no blocking findings

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

Review details

FINDING -- website/src/components/MobileConnectModal.tsx:242 -- "max-w-full" resolves against the shrink-wrapped frame, so the 344px QR frame overflows a 288px dialog at 320px -> Fix: replace it with max-w-[calc(90vw-70px)] (origin: validation)
[GPT-REVIEWED] 907fb9e

@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Fable 5, fork) — 🟡 CONCERNS

Premise-level review of 907fb9eba4a0cefd92fe86a19e31e274735bcc47 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/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

The "fixed box at fractional scale" pattern this PR itself harvests survives at 2 counted siblings: the WeChat and WhatsApp pairing panels.

Not justified as shipped

  • Item 1 — symptom-level (point patch): "Pattern harvest: a machine-read image (QR code, barcode) drawn into a fixed box at a fractional scale of its natural size" — grep for fixed-size QR <img>s finds 4 sites on base; this fixes 2 and leaves website/src/pages/settings/WeixinPanel.tsx:273 (the shared encoder's 8px-module PNG squeezed into 180px) and website/src/pages/settings/WhatsAppPanel.tsx:761 (segno scale=6 PNG into 180px), and the description never says they are left.
    Subtraction: delete the fixed width={180} height={180} at those two sites the same way this PR did, if their codes exceed 180px natural — or defer, scoped in the description.
    Clears when: the two sibling panels drop their fixed boxes, or the description names phone-connect as this fix's level and lists the two panels as left.

What this change ships

Inventory (7 items) — 6 justified

Intent: let a user open Kiro Crew on a phone by scanning the phone-connect QR, which a camera cannot currently read — a FIX (#13510; new tests fail on base).

  1. Connect-dialog QR shows full-size (324px) and sharp, not squeezed to 176px — symptom-level (point patch: 2 counted pattern siblings unfixed)
  2. Overview-card QR shows full-size, not squeezed into 180px — justified
  3. Both QRs upscale pixelated on high-density screens instead of smoothed — justified
  4. QR shrinks only when wider than its container (narrow windows) — justified
  5. Encoder gains keyword-only box_size, default 8, other callers byte-identical — justified
  6. Phone-connect handler encodes at 4px modules so the code fits unscaled — justified
  7. Six before/after screenshots committed under temp-screenshots/ — justified (documented fork-contributor convention, .gitignore:114-121)

[FIRST-PRINCIPLES-REVIEWED] 907fb9e

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=4a5b00c665f7 rebutted: the WeChat login code draws about a tenth smaller

The 4-module quiet zone is the spec minimum and the point of the shared change. The WeChat panel's own 8px white padding is under 2 modules, so that code sat below spec before.
The panel layout does not change: the image keeps its fixed 180px box, so each module draws about a tenth smaller and nothing else moves.
Decode parity was measured on real Chromium renders of the WeChat code with the panel's img styling (180px box, 8px white padding) at 1x and 2x: ZXing reads both, and the camera-model floor is unchanged at P = 0.5.
Before/after renders of that code go into the description with the next push.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=14b6740c7114 rebutted: no blind first-time read on a fork PR

This is the fork lane's own limitation, not a gap in the change: the blind read does not run for a fork head, and nothing in the diff can change that.
The before/after screenshots of both changed surfaces are in the description. Pushing the branch to this repository would run the blind read if a maintainer wants one.

@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5 Review (fork) — ✅ no blocking findings

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

Review details

Nothing blocks; one advisory — removing the fixed 176px makes the connect-dialog QR overflow at phone widths, because max-w-full has no definite containing block there.

FINDING — website/src/components/MobileConnectModal.tsx:242 — className="block max-w-full h-auto [image-rendering:pixelated]" sits inside <div className="bg-white p-2.5 rounded-lg leading-none">, which is a non-stretched flex item of flex flex-col items-center, so its width is fit-content; the img's cyclic percentage max-width is treated as none while computing that, the wrapper sizes to the PNG's intrinsic 324px + 20px padding = 344px, and max-w-full then resolves against 344px and shrinks nothing — at a 390px viewport the dialog is min(440, 90vw) = 351px with a 301px content box, so the centred code hangs ~21px off each side (the dialog's overflow-y-auto forces overflow-x: auto, and the left overflow is unreachable), where width={176} always fit; the threshold is any viewport below ~438px, which includes both widths the repo targets → Fix: add max-w-full to the bg-white p-2.5 wrapper on line 232 so the img's percentage resolves against a definite width.

[OPUS-REVIEWED] 907fb9e

@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 Sep 26, 2026
@unstablebrainiac
unstablebrainiac force-pushed the fix/phone-connect-qr-scannable branch from ddefe71 to 7e59915 Compare September 26, 2026 15:52
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author

Rebased onto main 7b2da39c5 (the #14150 fix from #14138); CI re-running.

This revision also removes the unused data-testid on the dialog's QR image (First Principles) and adds the WeChat login code's before/after renders to the description (UX).

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=e949ae6bf262 fixed: the unused data-testid is removed

Removed data-testid="mobile-connect-qr-image" from the QR <img> in MobileConnectModal.tsx in 7e599154b.
Nothing read it: the modal test finds the image by its alt text, and main never had the attribute.

@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 Sep 26, 2026
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author

Both triage comments on #13510 name the 2-module border as one of two mechanisms, alongside the fixed box. The second gives the verifiable fix as "restore _QR_BORDER to the spec minimum of 4", notes that the WeChat handshake shares this encoder, and asks for a regression check that the symbol still decodes at the displayed size.
That check is in the description: the WeChat code, rendered in its panel's own fixed 180px box, decodes at P = 0.5 on main and with this change, and the panel layout does not move.
The old comment justified 2 by keeping the image compact enough to sit in a card without scaling; this PR stops squeezing the defect's code into fixed boxes, so that reason is gone. A per-caller border would keep one code below the spec minimum on purpose.

@unstablebrainiac
unstablebrainiac force-pushed the fix/phone-connect-qr-scannable branch from 7e59915 to f0d0702 Compare September 26, 2026 16:30
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=3b2c82500c13 fixed: light-theme Overview card screenshot added

Added after-card-light.png in f0d070212: the Overview card with this change in light theme at 2x, in the description's light-theme section beside the dialog's light shot.
It comes from the same capture run and fixture as after-card-dark.png, and the card's code has not changed since that run.

@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 Sep 26, 2026
@unstablebrainiac
unstablebrainiac force-pushed the fix/phone-connect-qr-scannable branch from f0d0702 to c070932 Compare September 26, 2026 17:21
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author

Rebased onto main 1354188fe; CI re-running. Every review lane on f0d070212 failed with a GitHub API rate limit for the installation before producing a verdict, so this push re-runs them. The change itself is identical.

@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Sep 26, 2026
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=949703d98e8c needs-a-decision: a phone scan before merge

Same gap as the previous head: this PR was prepared without a phone, so a physical scan is the one check it does not have.
The camera-model sweep in the description's Manual verification section is the evidence it rests on, measured on the real dialog and card renders.
Question for the maintainer: is that enough, or will you scan the dialog and the Overview card with a phone before merge?
The after screenshots encode a synthetic access URL, so scanning one off the screen at full size is a quick check without running the branch.

@unstablebrainiac
unstablebrainiac force-pushed the fix/phone-connect-qr-scannable branch from c223565 to 2dba1f3 Compare September 26, 2026 19:45
@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 Sep 26, 2026
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=c0af3ac5684e fixed: the quiet-zone change is dropped

_QR_BORDER is 2 again in 2dba1f3, as on main, and its quiet-zone test is removed, so the WeChat login code renders exactly as on main.
The narrow window you named was measured first, on the real dialog at 2x with only the border changed: in a 390px window, where the code shrinks to 281px, the 2-module code decodes down to P = 0.45 and the 4-module code only to 0.55. At full size neither was clearly better: the 4-module code reached 0.45 against 0.50, but failed at 0.55 and 0.65, where the 2-module code decodes.
Both surfaces already pad the code with white (the dialog 10px, the card 8px), so the light margin around the 2-module code is still at least 4 modules.
The description's screenshots and decode table are regenerated with the 2-module code: the dialog decodes down to 0.45 against main's 0.85, the Overview card to 0.45 against 0.8.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=f6f4ac7ba0bb fixed: the comment says when a module is exactly 4 CSS pixels

In 2dba1f3 the MOBILE_QR_BOX_SIZE comment says the dialog and the Overview card show the code at its natural size when the container is wide enough, so each module is exactly 4 CSS pixels there.
It also says max-w-full scales the image down in a narrower container, the 390px case this finding measured.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=c83d6d6d0abb fixed: the shared quiet zone is back to 2, so the WeChat code is unchanged

2dba1f3 drops the 2-to-4 quiet-zone change instead of compensating for it in the WeChat caller. _QR_BORDER is 2 again, so the WeChat login PNG, and the module pitch WeixinPanel.tsx draws it at, are what main renders.
weixin_qr.py and WeixinPanel.tsx are untouched.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=6390683832ec rebutted: both sibling codes still read in their 180px boxes, measured with this PR's decode procedure

Rendered each code with its panel's own <img> styling (180px box with p-2 under border-box sizing, so a 164px content box) at 2x in Chromium, then ran the ZXing camera sweep behind the description's table.
WeChat login code (an 89-character login URL, 41 modules at 8px): decodes down to P = 0.5, close to the fixed phone-connect surfaces' 0.45.
WhatsApp pairing code (segno 1.6.6 at scale=6, whatsmeow-shaped payloads of 195 to 265 characters, versions 9 and 10, 366 to 390px natural): decodes directly at 1x and 2x, and down to P = 0.7 for every payload.
Both read better than the phone-connect code this PR fixes did on main: 0.85 in the dialog, 0.8 in the card.
The intent scopes this change to the two surfaces that show the phone-connect code and leaves the WeChat panel's layout alone. The WhatsApp code comes from its own encoder, so drawing it at natural size would be a separate change with its own module size.

The connect dialog drew the server's QR PNG into a fixed 176px box, and
the Overview card drew the same code into a fixed 180px box. An access
URL carries a signed token, so its symbol runs to about 80 modules, and
those boxes squeezed each module to about 2px, smoothed at a fractional
scale. That is too small and soft for a phone camera.

The server now encodes the access code at 4px a module, and both
surfaces show the image at its natural size with pixelated scaling, so
every module is a whole number of screen pixels. The shared encoder's
default output is unchanged for its other callers.
@unstablebrainiac
unstablebrainiac force-pushed the fix/phone-connect-qr-scannable branch from 2dba1f3 to 907fb9e Compare September 26, 2026 20:36
@unstablebrainiac

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in files next to or imported by this PR's files since this head went green (4a12bc8 -> 47594b8: #14261's src/kiro_crew/cli.py and src/kiro_crew/dashboard/handlers/updates.py, and #12684's redaction work across src/kiro_crew/dashboard/ and src/kiro_crew/acp/); CI re-running. None of this PR's own files changed on main, and the change itself is identical (same patch-id).

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

Copy link
Copy Markdown
Contributor Author
  • span=0327c64bdd7f fixed: the description names the phone-connect code as this fix's level and lists the two sibling panels as left

What changed now ends with "This fixes the phone-connect code only." and names the WeChat login panel (WeixinPanel.tsx) and the WhatsApp pairing panel (WhatsAppPanel.tsx) as still drawing a QR code into a fixed 180px box.
It leaves both as they are because both still read in this PR's camera model: WeChat down to P = 0.5, and WhatsApp (segno at scale=6, 195- to 265-character pairing payloads) down to 0.7. The phone-connect code on main needed 0.85 in the dialog and 0.8 on the card.
The change is to the description only; there is no code change.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=4c48e701a90d rebutted: the narrow window was measured on the real dialog, and the code fits and still decodes

In Chromium at 2x, the dialog in a 390px window shows the code at 281px with no gray pixels, and the camera sweep decodes it down to P = 0.45, the same floor as the dialog at full width.
At 320px the code is 218px and its white frame still fits inside the dialog, with no horizontal scrolling. The description's Manual verification section now states both widths.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=06c9172a855c needs-a-decision: a first-paint check in Firefox or Safari

This environment runs Chromium only. There, a data: PNG's size resolves before the first frame that paints it: in 80 of 80 insertions a 324px code painted at full size, including insertions made inside an animation-frame callback just before a paint.
Question for the maintainer: will you spot-check the connect dialog in Firefox or Safari (open it, click Show QR code, watch whether the Copy link row jumps), or should this PR restore explicit dimensions, with the endpoint returning the image's size and both images setting width and height from it?

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=51c12bcf5a2d rebutted: the QR frame shrinks with the dialog and does not overflow at 320px

Measured on the real dialog in Chromium at 2x. At a 320px viewport the dialog is 288px wide with a content box of about 240px; the white QR frame renders 238px wide inside it and the code 218px, with no horizontal scrolling on the dialog or the page.
At 360px the frame is 274px in a 324px dialog, and at 390px it is 301px in a 351px dialog.
The frame is a fit-content flex item of an items-center column, and the image's percentage max-width lets that frame shrink below the image's natural width, so max-w-full resolves against the available width rather than a 344px frame.

@unstablebrainiac

Copy link
Copy Markdown
Contributor Author
  • span=fa65355c885a rebutted: the QR frame is not 344px at phone widths; it shrinks to the dialog's content box, measured

Measured on the real dialog in Chromium at 2x. At a 390px viewport the dialog is 351px wide with a 301px content box, and the white frame renders 301px wide with the code at 281px: nothing hangs off either side, and neither the dialog nor the page scrolls horizontally. At 320px the dialog is 288px, the frame 238px and the code 218px.
The frame's fit-content width takes the available width because the image's percentage max-width counts only toward its max-content size; for a replaced element it counts as zero in the min-content size, so the frame's min-content width is just its 20px of padding.
max-w-full therefore resolves against the available width, which is what the 281px and 218px renders show.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Sep 26, 2026
@iamwhatever
iamwhatever enabled auto-merge (squash) September 26, 2026 22:51
@iamwhatever
iamwhatever merged commit 1d53180 into kirodotdev:main Sep 26, 2026
107 checks passed
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Sep 26, 2026
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)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Phone connect QR code is not recognized by the phone camera

2 participants