Files
deepseek-harness/snapshots/web/present-svg/ui.expected.md
T
_KermanandTianyi Cui fb79a944f5 refactor(llm): separate durable producer sources from request inputs
Give durable user context its producer-owned source kind instead of a generic plugin wrapper. The V3-to-V4 conversion preserves the frozen rename and collision rules, all own JSON metadata, event coordinates, and historical request-only kinds. Native catalog and JSONL admission retain source validation so unknown attribution can survive without its producer while malformed owned sources are refused.

Use an explicit user-only RequestUserInput for auxiliary LLM prompts that do not own durable message identity. Auto Review and compaction remove their request-only source registrations while retaining prompt content and freezing; provider serializers and projections keep the same wire data, assistant replay isolation, image ordering, and tool correlation. Session writes, Agent delivery, and recorded title requests continue to require identified durable messages.

Bind the saved compatibility policy only to user sources and qualify tmux location attribution without weakening fixed system, model, or tool semantics. Rebuild the current inventory and unpublished V4 acknowledgement on the actual tool-role parent, preserving its rationale and all accepted historical records. The catalog format version records tooling metadata; Session remains V4. Developer-role policy and activation belong to their own feature.

The latest-master Messages adapter, serialization, request-input typing, EpochHeader reservation, and attribution checks pass 103 tests across five files. The retained V3 Messages input-history snapshot passes through the source profile; Host/Client typechecks and all 41 documentation gates pass. The generated comparison records four changed roots and 447 unchanged type fingerprints. Latest-master ARIA changes are retained, with producer source labels applied independently; new Messages fixtures retain their producer names as declared source kinds and use the fixed system-message helper; recorded Session generations are unchanged by this regrouping.

Co-authored-by: Tianyi Cui <[email protected]>
2026-09-18 19:07:12 +08:00

2.2 KiB

  • button "系统提示词"
  • text: 简单画一个 SVG 表示冯诺依曼架构, 保存为 von-neumann.svg {{clock}}
  • button "复制"
  • button "2 次工具调用 · 1 条消息" [expanded]
  • button "上下文注入 runtime-context"
  • button "思考 The user wants a simple SVG diagram of the von Neumann architecture, saved as von-neumann.svg. Let me create a clean SVG showing CPU (control unit, ALU), memory, input, and output with bidirectional data/control buses."
  • paragraph: 我来创建一个冯诺依曼架构的 SVG 示意图。
  • button "写入 von-neumann.svg +83 -0":
    • text: 写入
    • button "von-neumann.svg"
    • text: +83 -0
  • button "思考 The file is created. Let me present it as a deliverable."
  • button "交付文件 已交付 von-neumann.svg"
  • paragraph:
    • text: 已创建
    • code:
      • button "在侧边栏打开 von-neumann.svg": von-neumann.svg
    • text: ,一个简洁的冯诺依曼架构示意图,包含:
  • list:
    • listitem:
      • strong: CPU(中央处理器)
      • text: :内含控制单元 CU、算术逻辑单元 ALU 和寄存器组
    • listitem:
      • strong: 内存储器 Memory
      • text: :标注"指令和数据统一存放"(存储程序思想)
    • listitem:
      • strong: 输入设备 / 输出设备
      • text: :分别用绿色和粉色表示数据流向
    • listitem:
      • strong: 总线连接
      • text: :CPU 与内存间的地址总线,以及 CPU 与 I/O 设备间的数据/控制线,箭头标明数据流向
  • paragraph: 下方附一行核心思想说明:指令与数据以二进制统一存储在存储器中。用浏览器打开该 SVG 文件即可查看。
  • button "在侧边栏查看本轮改动": 已编辑 1 个文件 +83 -0
  • list:
    • listitem:
      • button "查看 von-neumann.svg 的改动": von-neumann.svg +83 -0
  • text: 此主机没有可用的桌面,无法使用外部程序打开文件或文件夹;文件仍可在侧边栏预览
  • button "在侧边栏预览 von-neumann.svg"
  • text: von-neumann.svg 冯诺依曼架构示意图 SVG
  • button "在侧边栏打开 von-neumann.svg": 打开
  • button "von-neumann.svg 的更多文件操作" [disabled]
  • button "复制"
  • button "好的回答"
  • button "有问题的回答"
  • button "在新对话中分支"
  • button "用量 32K tok"
  • text: {{clock}}