chore(docs): untrack project-local design notes (dev → main)

.gitignore

@@ -40,6 +40,9 @@ tsconfig.tsbuildinfo
 # OpenSpec artifacts (local-only, not tracked)
 /openspec/
 
+# Local project thought and design notes (never commit)
+/docs/
+
 # hooks file
 .opencode/hooks.json
 
@@ -48,4 +51,4 @@ tsconfig.tsbuildinfo
 .claude
 .opencode/commands/
 .opencode/skills
-.qoder
+.qoder

.opencode/workflows/GRAPH-ENGINEERING.md

@@ -1,18 +1,8 @@
 # Graph Engineering workflow catalog
 
-These workflows adapt the useful execution patterns from
-[codejunkie99/graph-engineering](https://github.com/codejunkie99/graph-engineering)
-to GraphAgent's durable YAML runtime. The source repository is MIT-licensed; its
-copyright and license are available in the linked repository. The YAML files here
-are project-specific adaptations, not verbatim copies.
-
-The adaptations were cross-checked against the executable examples in
-[GraphARC](https://github.com/CodeGraphContext/GraphARC), Anthropic's
-[workflow patterns](https://www.anthropic.com/engineering/building-effective-agents)
-and [multi-agent production notes](https://www.anthropic.com/engineering/multi-agent-research-system),
-plus Google's controlled study on
-[when agent teams help or hurt](https://research.google/blog/towards-a-science-of-scaling-agent-systems-when-and-why-agent-systems-work/).
-No Python or framework runtime was copied.
+GraphAgent treats these workflows as durable, executable reference topologies.
+The parent agent selects the closest shape, injects the current task, and derives
+the actual DAG while preserving its protected fail-closed gates.
 
 ## Reference graphs
 
@@ -46,6 +36,6 @@ DAG-module lanes unless that module is the real target.
 | `LOOP` | Pause, add a fresh local correction/review wave with new node IDs, resume | Reason, minimal `loop_scope`, acceptance condition, `stop_reason` |
 | `BLOCKED` | Stop and report; do not reinterpret as advisory success | Missing evidence/decision, unresolved contradiction, no progress, or a reached cap |
 
-These graphs copy topology ideas, not framework code or the upstream repository's
-nine disconnected knowledge-graph prompts. The full source comparison and license
-notes are in [`docs/graph-engineering-template-research.md`](../../docs/graph-engineering-template-research.md).
+These graphs are project-authored execution contracts, not framework-specific
+examples. Their value lies in enforceable edges, evidence gates, bounded local
+loops, and explicit parent-agent disposal rules.

README.md

@@ -27,7 +27,7 @@ Our graph-engineering doctrine is operational:
 4. **Iteration is a bounded local graph rewrite.** `PASS` finalizes, `LOOP` adds a new correction/review wave through pause → replan → resume, and `BLOCKED` stops with evidence. Completed nodes never form a hidden cycle.
 5. **Reality outranks self-report.** State is event-sourced, recovery follows durable evidence, tests and code settle claims, and humans retain pause/step/cancel/replan authority where mistakes are expensive.
 
-The repository ships three opinionated reference graphs: design decision deep-dive, parallel project delivery, and deep review of an existing subsystem. `/dag-flow` selects the closest shape from the request, injects the current task, and derives the actual DAG while preserving its fail-closed gates. See the [Graph Engineering workflow catalog](./.opencode/workflows/GRAPH-ENGINEERING.md). The designs adapt useful patterns from the MIT-licensed [graph-engineering](https://github.com/codejunkie99/graph-engineering) project to this runtime's stronger execution, recovery, and control contracts.
+The repository ships three opinionated reference graphs: design decision deep-dive, parallel project delivery, and deep review of an existing subsystem. `/dag-flow` selects the closest shape from the request, injects the current task, and derives the actual DAG while preserving its fail-closed gates. See the [Graph Engineering workflow catalog](./.opencode/workflows/GRAPH-ENGINEERING.md).
 
 ## Why a DAG
 
@@ -248,9 +248,8 @@ Exact file boundaries are listed in [`NOTICE`](./NOTICE). The AGPL covers the DA
 ## Docs
 
 - [Saved workflow authoring guide](./packages/core/src/plugin/skill/create-dag-workflow.md) — the `create-dag-workflow` skill body
-- [Graph Engineering workflow catalog](./.opencode/workflows/GRAPH-ENGINEERING.md) and [source research](./docs/graph-engineering-template-research.md) — reusable shapes, evidence, and migration choices
+- [Graph Engineering workflow catalog](./.opencode/workflows/GRAPH-ENGINEERING.md) — reference topologies and adaptation contracts
 - [`.opencode/workflows/change-review.yaml`](./.opencode/workflows/change-review.yaml) — compact change review, startable as `change-review`
-- [`docs/harness-dag.md`](./docs/harness-dag.md) — deep-mode admission & review lifecycle
 - [`.opencode/dag-prompts`](./.opencode/dag-prompts) — built-in node prompt templates
 - [`AGENTS.md`](./AGENTS.md) — contribution & development guide
 

README.zh.md

@@ -24,7 +24,7 @@ GraphAgent 是本项目对外的产品名；仓库以 **OpenCode-GraphAgent** 
 4. **迭代是有界的局部改图。** `PASS` 才能定稿，`LOOP` 通过 pause → replan → resume 增加新的修正与复审波次，`BLOCKED` 带证据停止；终态节点不会被伪装成环。
 5. **代码和测试说了算。** 状态变更写入事件，崩溃恢复只认持久化证据。到了代价高的边界，人可以 pause、step、cancel 或 replan。
 
-仓库已经附带三类强约束参考图：设计决策深挖、并行项目落地、已完成子系统深度 Review。`/dag-flow` 会先按需求选择最接近的中高规模样板，注入本次任务，再派生实际 DAG；可以扩展和剪枝，但不能绕过 fail-closed 门禁。入口见 [Graph Engineering 工作流目录](./.opencode/workflows/GRAPH-ENGINEERING.md)。这些 YAML 把 MIT 许可的 [graph-engineering](https://github.com/codejunkie99/graph-engineering) 项目里有价值的模式，适配到了本项目更严格的执行、恢复和控制契约上。
+仓库已经附带三类强约束参考图：设计决策深挖、并行项目落地、已完成子系统深度 Review。`/dag-flow` 会先按需求选择最接近的中高规模样板，注入本次任务，再派生实际 DAG；可以扩展和剪枝，但不能绕过 fail-closed 门禁。入口见 [Graph Engineering 工作流目录](./.opencode/workflows/GRAPH-ENGINEERING.md)。
 
 ## 为什么是 DAG
 
@@ -222,9 +222,8 @@ bun dev serve        # headless API 服务（端口 4096）
 ## 文档
 
 - [存盘工作流编写指南](./packages/core/src/plugin/skill/create-dag-workflow.md) —— `create-dag-workflow` skill 正文
-- [Graph Engineering 工作流目录](./.opencode/workflows/GRAPH-ENGINEERING.md)和[来源调研](./docs/graph-engineering-template-research.md) —— 可复用样板、证据与迁移取舍
+- [Graph Engineering 工作流目录](./.opencode/workflows/GRAPH-ENGINEERING.md) —— 参考拓扑与自适应协议
 - [`.opencode/workflows/change-review.yaml`](./.opencode/workflows/change-review.yaml) —— 轻量变更审查图，按 `change-review` 启动
-- [`docs/harness-dag.md`](./docs/harness-dag.md) —— deep 模式准入与审查生命周期
 - [`.opencode/dag-prompts`](./.opencode/dag-prompts) —— 内置节点 prompt 模板
 - [`AGENTS.md`](./AGENTS.md) —— 贡献与开发指南