feat(ui): 发送周期下限 10ms + 草稿态编辑修复

[Gyanano]

改动

• 周期下限 100ms → 10ms（Step 4 事件推送后接收通路能跟上；速率预警仍会拦截超物理容量的配置）
• 修复编辑体验：原实现每次击键都 Math.max(100, ...) 钳制，输入「50」时第一个数字「5」直接被弹成 100。改为草稿态编辑：聚焦后自由输入，失焦/Enter 才提交并钳制到 [10, 60000]，Escape 放弃

验证

• tsc --noEmit 通过；有头应用人工验证编辑/提交/取消行为正常

---

Note

Low Risk
UI-only changes to scheduled-send timing bounds and input behavior in SendPanel; no auth, persistence, or wire-protocol changes.

Overview
Scheduled send cycle in SendPanel now allows a 10ms minimum (was 100ms), with step 10 on the interval field. The lower bound reflects that the RX path can keep up; existing rate warning logic still blocks configs that exceed ~90% of line capacity.

Interval input editing no longer clamps on every keystroke (which made typing values like 50 jump to the minimum). While focused, the field uses an intervalDraft string; digits-only typing commits on blur or Enter (clamped to [10, 60000], invalid/empty drafts keep the current interval), and Escape discards the draft. If scheduled sending is already running, a committed interval change still restarts the timer with the new value.

^{Reviewed by Cursor Bugbot for commit a8786ff. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6e15920c-ca2e-4fe1-826c-865e7f2fa2f7)