Problem with recommending startTransition in design system event handlers?

we generally recommend to bake useTransition into the design system components of your app
https://reactjs.org/docs/concurrent-mode-patterns.html#baking-transitions-into-the-design-system

 // Button component in design system event handler:

  function handleClick() {
    startTransition(() => {
      onClick();
    });
  }

Couldn't this lead to the problem mentioned later?

Try typing into the input now. Something’s wrong! The input is updating very slowly
https://reactjs.org/docs/concurrent-mode-patterns.html#splitting-high-and-low-priority-state

The answer to this problem is to split the state in two parts: a “high priority” part that updates immediately, and a “low priority” part that may wait for a transition.

Solution:

function handleChange(e) {
  const value = e.target.value;
  
  // Outside the transition (urgent)
  setQuery(value);

  startTransition(() => {
    // Inside the transition (may be delayed)
    setResource(fetchTranslation(value));
  });
}

If your design system components wrap all their event handlers in startTransition then how would you make a setState call in your handler run outside of a transition?

Concurrent Mode Patterns のリンクされたセクションを確認し、トランジションをデザインシステムのコンポーネントに組み込む方法と、高優先度と低優先度の state を分離する方法を調べてください。issue のイベントハンドラーの例を出発点として使用します。完了条件は、デザインシステムのハンドラーがコールバックを startTransition でラップすべきかどうか、および緊急の更新をトランジションの外部に残す方法をドキュメントで明確に説明していることです。