[paralax034]

改动 / Changes

• Incrementally highlight streaming code blocks in CodeBlock.vue by splitting stable highlighted prefixes from the active tail and skipping grid collapse transitions/unmounting collapsed DOM nodes on large code blocks.
• Mark parsed Markdown AST blocks/nodes with markRaw in markdown.ts and memoize rendered VNodes in MarkdownBlock.ts.
• Scope ChatTurn.vue :has() selectors to direct .actions-container children, replace full-subtree :has(.ms-code-block .code-header.sticky) matching with a reactive has-code class, read the latest batch entry (entries.at(-1)) in IntersectionObserver and ResizeObserver, and apply contain: layout style to prevent UI freezes on menu/action clicks and fast scrolling.
• Preserve systemInstruction when resetting to /prompts/new_chat, allow saving prompts with system instructions before the first turn, and persist system instruction presets in promptdb (GET/PUT /api/prompts/system-instructions) so presets stay synced across the desktop window and browsers.

验证 / Verification

• cd web && npm run lint && npm run format:check && npm run build
• go vet ./...
• go test -mod=readonly ./cmd/... ./internal/...

[paralax034]

While working on this, I also noticed that many models (like Gemini 3.x Flash with thinking enabled) hide sampling parameters (Temperature, Top P, Top K) in the Run Settings panel.

In a follow-up PR, would you be interested in adding:

1. Sliders for Top P (0.0–1.0) and Top K (1–128) under Advanced settings (matching existing M3 UI slider styles).
2. An optional sampling presets selector (e.g. Deterministic Code, Balanced, Creative, etc.) that calibrates Temp/TopP/TopK together?

Like

[paralax034]

Update

[paralax034]

Fix formatting

[paralax034]

While working on this, I also noticed that many models (like Gemini 3.x Flash with thinking enabled) hide sampling parameters (Temperature, Top P, Top K) in the Run Settings panel.

In a follow-up PR, would you be interested in adding:

1. Sliders for Top P (0.0–1.0) and Top K (1–128) under Advanced settings (matching existing M3 UI slider styles).
2. An optional sampling presets selector (e.g. Deterministic Code, Balanced, Creative, etc.) that calibrates Temp/TopP/TopK together?

@Mag1cFall , do you think this aligns with the project's design and architectural style? If so, I’d be happy to create a separate PR for this!