0408a032c15f3bf56f095dfe82e0653e50583eb6
Why: the project access and lifecycle units (U1 role narrowing to a single project-access boolean, U2 creator authority, U3 member history, U4 project work states) were implemented and pushed on this line but never landed on Backend main, so Dev's pinned Backend does not contain them. Evidence: merge is conflict-free against current origin/main; full vet-and-test runs on the merge commit. Impact: Backend only. RDM side is delivered separately. Refs: Dev PR #634.
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 多仓组合的组成部分。
Description
对话系统后端:会话与流式管道、智能体运行时与画像、工具/上下文/文档解析/检索/设置管理、插件宿主(组合 Agent-Native/Squad/Intent);依赖 Agent-System-Core 契约,默认单二进制非容器部署。
25 MiB
Languages
Go
98.5%
Python
1.4%