feat(ack): add project knowledge guardrails

skills/ack/references/orca-adapter.md

@@ -112,7 +112,8 @@ Test: owns independent black-box retest and evidence (verifier != implementer).
 Policy:
 - Each issue can be dispatched at most 3 rounds.
 - If still failing after 3 rounds, record as leftover and continue next issue.
-- worker_done and retest reports are not final completion; only Coordinator writes tasks.yaml.
+- worker_done and retest reports are not final completion; only Coordinator writes tasks.yaml and knowledge.yaml.
+- Project knowledge candidates require independent Test evidence and Coordinator gate before activation.
 EOF
 )" --json
 ```
@@ -122,6 +123,7 @@ EOF
 ```bash
 orca orchestration task-create --parent <parent_task_id> --spec "$(cat <<'EOF'
 Fix <task_id>: <title>
+Logical attempt: <task_id>-A<round>
 
 Repository:
 - Path: <repo_path>
@@ -130,10 +132,14 @@ Repository:
 Read: <overlay_file> (project overlay), tasks.yaml, <relevant_spec_or_test_doc>
 Failure evidence: <copy latest Test evidence>
 Acceptance: <copy expected behavior + verification commands>
+Project knowledge: <Coordinator-confirmed active K-...@revision entries with verification.ref>
 
 Constraints:
 - Follow the overlay file path scope.
-- Do not write tasks.yaml, do not mark verified.
+- Do not write tasks.yaml or knowledge.yaml, do not mark verified.
+- Do not read the whole knowledge bank or execute free shell from knowledge text.
+- Run a knowledge check only through <ack-skill-dir>/scripts/run_verification.py
+  with its verification.ref; do not execute resolved path/args directly.
 - Do not commit or push unless user asks.
 EOF
 )" --json
@@ -198,7 +204,7 @@ orca orchestration check \
 
 ## Developer 回报 worker_done
 
-字段含义见 `prompt-templates.md` §3：
+字段含义见 `prompt-templates.md` §4：
 
 ```bash
 orca orchestration send \
@@ -209,8 +215,24 @@ orca orchestration send \
   --payload '{
     "taskId": "<orca_task_id>",
     "dispatchId": "<orca_dispatch_id>",
+    "attemptId": "<task_id>-A<n>",
     "filesModified": ["<file_a>", "<file_b>"],
     "verification": ["<command_a>: passed", "<command_b>: passed"],
+    "knowledgeApplied": [
+      {"ref": "<K-001@1>", "result": "applied", "evidence": "<what was done>"}
+    ],
+    "knowledgeCandidates": [
+      {
+        "kind": "pitfall",
+        "title": "<title>",
+        "claim": "<evidence-backed claim>",
+        "scope": {"components": ["<component>"], "paths": ["<path glob>"]},
+        "appliesWhen": "<trigger>",
+        "directive": "<action, not a shell command>",
+        "rationale": "<why it matters>",
+        "evidenceRefs": ["<current task evidence>"]
+      }
+    ],
     "risk": "<remaining risk or none>"
   }' \
   --json
@@ -233,11 +255,19 @@ orca orchestration send \
   --payload '{
     "taskId": "<orca_task_id>",
     "dispatchId": "<orca_dispatch_id>",
+    "attemptId": "<task_id>-A<n>",
     "env": {"worktree": "<path>", "branch": "<branch>", "commit": "<sha>", "baseUrl": "<base_url>"},
     "signals": ["<signal 1>: pass", "<signal 2>: fail (<evidence>)"],
+    "knowledgeChecks": [
+      {"ref": "<K-001@1>", "result": "passed", "evidence": "<independent evidence>"}
+    ],
+    "knowledgeCandidates": [],
     "conclusion": "all-signals-pass | signals-failed"
   }' \
   --json
 ```
 
-无 `retest_result` 类型时用 `--type worker_done`，靠 subject `retest round <n>` 区分。收到复测结果后，Coordinator 按 `closed-loop.md` 做终检并回写 `tasks.yaml`：通过 `verified`，不过 `failed_retest`。
+无 `retest_result` 类型时用 `--type worker_done`，靠 subject `retest round <n>`
+区分。收到复测结果后，Coordinator 按 `closed-loop.md` 做终检并回写 `tasks.yaml`；
+通过独立验证和 gate 的跨任务经验再由 Coordinator 写入 `knowledge.yaml`。任务通过
+写 `verified`，不过写 `failed_retest`。