Best possible solution:

Land this focused Feishu QR print-path fix after normal maintainer and CI gates; keep the broader Feishu startup-timeout work tracked separately.

Do we have a high-confidence way to reproduce the issue?

Yes, from source inspection: current main routes Feishu scan setup through printQrCode(), which calls the full terminal QR renderer, and the contributor's before screenshot shows the oversized/wrapped terminal output. I did not run the live Feishu login flow in this read-only review.

Is this the best way to solve the issue?

Yes. The PR uses the existing OpenClaw compact QR renderer on the narrow Feishu print path, avoids the old upstream qrcode small-mode bug, and adds focused Feishu coverage without adding config or a new API.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against e5123e44b0f5.

Label changes:

• add proof: sufficient: Contributor real behavior proof is sufficient. The PR body now includes GitHub-hosted before/after terminal screenshots showing the oversized full QR and the compact after-fix printQrCode output.
• add proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The PR body now includes GitHub-hosted before/after terminal screenshots showing the oversized full QR and the compact after-fix printQrCode output.
• add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The PR body now includes GitHub-hosted before/after terminal screenshots showing the oversized full QR and the compact after-fix printQrCode output.
• remove rating: 🦪 silver shellfish: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.
• remove status: 📣 needs proof: Current PR status label is status: 👀 ready for maintainer look.

Label justifications:

• P2: This is a normal Feishu channel login usability bug with a narrow fix and limited blast radius.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The PR body now includes GitHub-hosted before/after terminal screenshots showing the oversized full QR and the compact after-fix printQrCode output.
• proof: sufficient: Contributor real behavior proof is sufficient. The PR body now includes GitHub-hosted before/after terminal screenshots showing the oversized full QR and the compact after-fix printQrCode output.
• proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The PR body now includes GitHub-hosted before/after terminal screenshots showing the oversized full QR and the compact after-fix printQrCode output.

PR surface:

Source 0, Tests +18. Total +18 across 2 files.

What I checked:

• Current main Feishu QR path: Current main's printQrCode() still calls renderQrTerminal(url) without compact mode, so the PR addresses behavior that remains present on main. (extensions/feishu/src/app-registration.ts:268, e5123e44b0f5)
• Runtime entry point: The Feishu scan-to-create setup flow calls printQrCode(begin.qrUrl) after prompting users to scan the QR code, so the changed helper is on the channel login/setup path. (extensions/feishu/src/setup-surface.ts:287, e5123e44b0f5)
• Shared compact renderer contract: renderQrTerminal(..., { small: true }) uses OpenClaw's own compact block renderer from qrcode.create(text).modules, not upstream qrcode terminal small mode. (src/media/qr-terminal.ts:48, e5123e44b0f5)
• Sibling compact usage: WhatsApp login/session already use the same compact QR option, which supports this as a consistent QR login display fix rather than a one-off renderer. (extensions/whatsapp/src/session.ts:124, e5123e44b0f5)
• Compact renderer regression coverage: The existing real-runtime QR test asserts compact output is narrower than full output and decodes back to the same QR matrix; the PR adds Feishu-specific coverage for passing { small: true }. (src/media/qr-terminal.render.test.ts:72, e5123e44b0f5)
• Dependency contract checked: Pinned qrcode v1.5.4 routes options.small to a separate terminal-small renderer; OpenClaw's compact path avoids that dependency path by calling create() directly.

Likely related people:

• mazhe-nerd: Merged Feishu scan-to-create onboarding added app-registration.ts, including the QR print path this PR changes. (role: introduced behavior; confidence: high; commits: 9e2ac8a1cb9a; files: extensions/feishu/src/app-registration.ts, extensions/feishu/src/setup-surface.ts)
• neeravmakwana: Authored the merged shared QR default change that switched Feishu away from compact output while fixing the upstream small-mode ANSI bug. (role: shared QR renderer contributor; confidence: high; commits: 0ac483787813; files: src/media/qr-terminal.ts, extensions/feishu/src/app-registration.ts)
• liorb-mountapps: Authored the later matrix-backed compact renderer and WhatsApp compact QR usage that this PR reuses for Feishu. (role: compact renderer contributor; confidence: high; commits: ff700e582385, 492105db5a36; files: src/media/qr-terminal.ts, src/media/qr-terminal.render.test.ts, extensions/whatsapp/src/session.ts)
• steipete: Recently maintained Feishu app-registration tests and merged the shared QR default fix affecting this path. (role: recent area contributor; confidence: medium; commits: b9d7dd4a84b2, 0ac483787813; files: extensions/feishu/src/app-registration.ts, extensions/feishu/src/app-registration.test.ts, src/media/qr-terminal.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.