Why: cleanup, component synchronization, receipt recording and credential handling could contradict the documented development boundaries. Evidence: SELF 75 isolated governance tests and source checks are captured in .task/feature-governance-reliability.md; combination and CI verification follow. Impact: hardens local task and CI tooling, aligns policy and component documentation, and adds continuous regression tests without changing product behavior. Refs: .task/feature-governance-reliability.md; policy/governance.md; policy/platform-admission.md
19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
# Agent-System-Dev 项目事实
|
||
|
||
- 用途:开发集成父仓(gitlink 权威);非分发单元。
|
||
- 组合:modules/{core,backend,frontend,ui,documents} + deps/{development-guidelines,agent-native,agent-squad,agent-intent,agent-command,error-code-system,logging-system}。
|
||
- 部署:非容器;Releases 仓从本仓固定提交导出版本。
|
||
|
||
## 验证
|
||
|
||
`make test` 先核对子模块工作树与固定指针,再运行治理脚本、公开边界、跨仓指针、库及各模块
|
||
测试。实际目标以根 Makefile 为准。`make test-governance` 可独立检查开发门禁,使用临时
|
||
真实仓库,不访问生产数据;操作与证据要求见 [开发门禁](policy/governance.md)。
|
||
|
||
`make build` 在 backend 模块内编译,replace 指向该模块自己的 `deps/`;
|
||
`scripts/check-pins.sh` 核对这些 gitlink 与 Dev 顶层指针,`make test-worktree` 另核对
|
||
真正被测的组件工作树。两者分别验证固定组合与实际检出,不能相互替代。
|
||
|
||
未加 go.work:工作区最小版本选择会抬高 backend 单独构建使用的部分 `golang.org/x` 版本。
|
||
发布消费方须从固定 Dev 提交递归物化后运行 `make build`,再核验制品与实际运行状态。
|