fix(convert-chip): fix hooks order when toggling layout mode

[qiuwenbo1]

Summary

• Fixes Rendered fewer hooks than expected when switching layout between split / editor / preview.
• Moves if (layoutMode !== "split") return null to after useCallback and useEffect in ConvertChip.

Test plan

• pnpm dev, open the app
• Toggle layout: split → editor → preview → split; no hook errors in console
• Convert chip visible only in split mode
• ⌘/Ctrl+Enter still triggers convert when enabled

[lefarcen]

Heads-up: PRs #28 and #30 are also open against this same ConvertChip hook-order fix. All three touch src/components/convert-chip.tsx and move the layoutMode !== "split" guard below the hook calls for the “Rendered fewer hooks than expected” crash.

You, @chasel34, and @cszhouwei may want to compare approaches; the maintainer team will pick which one lands. Sharing so nobody's effort gets wasted.

[mrcfps]

Thanks for the hooks-order fix — I found one follow-up shortcut regression in editor-only mode; details are inline.

_{🔁 Powered by Looper · runner=reviewer · agent=opencode · An autonomous AI dev team for your GitHub repos.}

[mrcfps]

Keeping the hooks unconditional fixes the React crash, but moving this guard below the useEffect also leaves the global ⌘/Ctrl+Enter listener active when the chip is hidden in editor-only mode. EditorPane still renders AiPromptBar there (src/components/editor-pane.tsx:147), and that input already handles the same shortcut without stopping propagation (src/components/ai-prompt-bar.tsx:57-61), so a single keypress now both submits the draft and starts an HTML conversion from a hidden chip. That is a behavior regression from the pre-change flow. Please keep the hooks unconditional but gate the keydown effect itself on layoutMode === "split" (or ignore events coming from the prompt input / stop propagation there), and add a regression check for ⌘/Ctrl+Enter in editor mode.

_{🔁 Powered by Looper · runner=reviewer · agent=opencode · An autonomous AI dev team for your GitHub repos.}