agent-exec-transport
e7b345e127
Why: After the role-authority cutover a role could only carry the single project.create boolean, so every project-scope action resolved as undefined and project conversations plus member collaboration were rejected. Owner product intent: a role carries one project-management toggle, and holding it grants the in-project defaults (read, write, members, traces, stage, archive, audit); three-duty and knowledge publishing stay duty-gated. Evidence: go test ./internal/store ./internal/app ./internal/server -count=1 passes; TestRoleCarriesProjectScopeDefaults covers the write, the snapshot projection and the unchanged invariant that a role enabling project.create may not deny a linked management action. The agent-exec transport diff is identical to the owner-accepted revision deployed on imc-tx-ecs (binary 941f8eef). Impact: ReplaceRolePermissions accepts project-scope actions while protected system actions stay refused, RolePermissions projects project-scope rows plus the project-management implied defaults into the role policy snapshot, and an explicit capability-association gate runs before each write. Refs: feature/role-project-scope-permissions
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 多仓组合的组成部分。