weichenandCursor
2880b58b7b
Why: deliverable prompts already tell the model to generate Office files with run_python and register them, but the executors were never registered, so calls missed the registry and fell back to text-only write_artifact. Evidence: go test ./... — 19 packages ok, including echo/script-retention, empty-script and runtime.exec gate, process-group timeout, python ZIP magic, and ExecuteTool backfill of register_artifact after run_python. Scripts stay under the session .agent/ directory; bash/python3 are resolved to absolute paths; timeout kills the process group. Impact: models can execute workspace scripts and register binary deliverables. runtime.exec=false still fail-closes the whole family. Office extensions now get real MIME types so binary bytes are not indexed as text. Refs: task feature/exec-interpreters Co-authored-by: Cursor <cursoragent@cursor.com>
Agent-System-Backend
对话系统后端：Go 模块化单体，默认构建为单二进制（go:embed 内嵌前端与嵌入式 SQLite 存储）。组合 Agent-Native / Agent-Squad / Agent-Intent 生态，依赖 agent-system-core 契约。
契约与架构见 Agent-System-Documents 设计方案与架构文档；开发规范见 development-guidelines（Dev 仓 development/guidelines）。本仓为 Agent-System 多仓组合的组成部分。