weichen
4675a25c18
Why: Every turn rebuilt context from UI messages with 160-char tool-result summaries and truncated arguments (quality diagnosis root cause 1). The kernel session transcript already persists full-fidelity messages; P2-I2 switches the direct path to it as the authority, per the approved plan (Documents 2026-10-09 §4 P2, user ruling 2). First run (or after structural divergence) seeds the transcript once with the full ctxasm assembly; later runs pass only the current user message. Dynamic context - tail notes (personal instructions, session notes, world-book entries), env update (date, workspace files) and newly hit task-layer prompt modules - refreshes once per non-seed run via Reminders, so the frozen seed system prompt stays accurate. Structural divergence (excluded messages, variant switching, regeneration) changes a fingerprint and reseeds the transcript from the message store - the regenerate/exclude/variant mapping. Legacy transcripts without a fingerprint are adopted, not wiped, preserving crash-pairing repair. Near the window threshold a 9-section compaction (aux.session-compact, extractive fallback) summarizes older turns with the kernel's append-only compaction entry; the kernel request-side micro-clear still bounds within-run spikes. Backend's nested agent-native pin moves to the reasoning-capture/replay kernel head. Evidence: SELF - new tests TestContextRevisionStableOnAppendAndChangesOnDivergence, TestTranscriptReseedsOnVariantSwitch, TestBuildCurrentUserCarriesAttachmentsAndKnowledge; TestDirectRunSeedsStoreHistoryOnce updated to authoritative semantics; go vet + go test ./... pass; live before/after on the golden task set recorded on the phase02 task card per the policy clause. Impact: Direct conversations with a workspace sandbox now carry full tool results, arguments and attachment text across turns; MiniMax thinking replays from the transcript via the kernel change. No-conversation fallback keeps the pre-I2 assembly path.
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 多仓组合的组成部分。