create-principles-disciple 1.126.2 → 1.127.0

package/plugin/dist/templates/langs/en/skills/pd-cli-operator/SKILL.md

@@ -10,15 +10,22 @@ Use the `pd` CLI as the supported operator surface. Do not modify PD state files
 
 ## Runtime V2 Pain Diagnosis
 
-Manual pain diagnosis:
+Manual pain diagnosis (bind a recorded session so diagnosis carries real
+trajectory evidence):
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- Without `--session` the record is an honest unbound Owner report: no
+  trajectory evidence, candidates likely gated (`needs_evidence`) by the
+  admission threshold — the CLI output warns about this.
+- `--session <id>` is validated up front; a missing session fails with
+  `session_not_found` before anything is written.
+
 Success requires:
 - `status` is `succeeded`
-- `candidateIds` is non-empty
-- `ledgerEntryIds` is non-empty
+- candidates are ADMITTED, not merely generated: check `admissionResults` /
+  `candidateOutcomes` for `admitted` decisions and non-empty `ledgerEntryIds`
 
 Forbidden:
 - Do not write `.state/.pain_flag`.

package/plugin/dist/templates/langs/en/skills/pd-pain-signal/SKILL.md

@@ -1,22 +1,50 @@
 ---
 name: pd-pain-signal
-description: Manually trigger a Principles Disciple Runtime V2 pain diagnosis. Use this when the user reports the agent is stuck, looping, unresponsive, or asks to record/trigger a pain signal. Mandatory path: use `pd pain record`; never write `.state/.pain_flag` and never use legacy write_pain_flag tooling.
+description: Manually trigger a Principles Disciple Runtime V2 pain diagnosis. Use this when the user reports the agent is stuck, looping, unresponsive, or asks to record/trigger a pain signal. In an OpenClaw session, direct the Owner to the /pd-pain command (it binds the real session automatically). From outside a session, use `pd pain record --session <id>`. Never write `.state/.pain_flag` and never use legacy write_pain_flag tooling.
 disable-model-invocation: false
 ---
 
 # Pain Signal (Runtime V2)
 
-Manual pain diagnosis must enter Runtime V2 through the CLI:
+Session evidence is what makes a pain diagnosable. A pain recorded without a
+session carries no trajectory evidence, its candidates score below the
+admission threshold (0.5) and are gated as `needs_evidence` — the Owner's
+report is stored, but nothing is internalized.
+
+## In an OpenClaw session (preferred)
+
+Ask the Owner to run the host command in the conversation where the pain
+occurred:
+
+```text
+/pd-pain <describe the issue>
+```
+
+`/pd-pain` receives the authenticated current session from OpenClaw and
+submits the session's trajectory evidence automatically. You cannot obtain a
+trusted session ID yourself (none is injected into tool executions); never
+guess, scan, or pick the "latest" session.
+
+## Outside a session (CLI)
+
+Bind an explicitly known session id recorded in this workspace:
 
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- `--session <id>` is validated against the workspace trajectory: a missing
+  session fails with `session_not_found` before anything is written.
+- Recording without `--session` is allowed as an unbound Owner report, but it
+  attaches no evidence and its candidates will likely be gated
+  (`needs_evidence`) by the admission gate — the CLI output says so explicitly.
+
 ## Forbidden
 
 - Do not write `.state/.pain_flag` directly.
 - Do not use `write_file`, shell redirection, `Set-Content`, `Out-File`, `node -e`, or any other file-writing method to create `.state/.pain_flag`.
 - Do not use `write_pain_flag`. That was a legacy path.
+- Do not guess, scan for, or infer a session ID. Use `/pd-pain` or an id the Owner provides.
 
 ## Verify
 
@@ -27,4 +55,8 @@ pd candidate list --workspace "<workspace>" --json
 pd runtime flow show --workspace "<workspace>" --json
 ```
 
-Success requires non-empty `candidateIds` and `ledgerEntryIds`.
+Success requires admitted candidates, not merely generated ones: check
+`admissionResults` for `admitted` decisions and non-empty `ledgerEntryIds`.
+Candidates reported as `needs_evidence` or `deferred` were NOT internalized —
+if all candidates are gated, re-record with `/pd-pain` or `--session` so the
+diagnosis carries real trajectory evidence.

package/plugin/dist/templates/langs/en/skills/pd-runtime-v2/SKILL.md

@@ -18,8 +18,11 @@ Automatic:
 
 Manual:
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
+`--session` binds the report to a recorded session (validated up front) so
+diagnosis carries real trajectory evidence; without it the record is an
+unbound Owner report with no evidence and candidates will likely be gated.
 
 Forbidden:
 - Do not write `.state/.pain_flag`.

package/plugin/dist/templates/langs/zh/skills/pd-cli-operator/SKILL.md

@@ -10,15 +10,20 @@ disable-model-invocation: false
 
 ## Runtime V2 痛苦诊断
 
-手动痛苦诊断：
+手动痛苦诊断（绑定已记录的会话，让诊断携带真实轨迹证据）：
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- 不带 `--session` 的记录是诚实的 unbound Owner 报告：没有轨迹证据，
+  候选大概率被准入阈值拦为 `needs_evidence` —— CLI 输出会明确警告。
+- `--session <id>` 会先校验；会话不存在时以 `session_not_found` 失败，
+  不会写入任何内容。
+
 成功标准：
 - `status` 是 `succeeded`
-- `candidateIds` 非空
-- `ledgerEntryIds` 非空
+- 候选被**准入**而非仅被生成：检查 `admissionResults` /
+  `candidateOutcomes` 中的 `admitted` 决策和 `ledgerEntryIds` 非空
 
 禁止：
 - 不要写 `.state/.pain_flag`。

package/plugin/dist/templates/langs/zh/skills/pd-pain-signal/SKILL.md

@@ -1,22 +1,47 @@
 ---
 name: pd-pain-signal
-description: 手动触发 Principles Disciple Runtime V2 痛苦诊断。用户报告 agent 卡住、循环、无响应，或要求记录/触发痛苦信号时使用。强制路径：使用 `pd pain record`；禁止写 `.state/.pain_flag`，禁止使用 legacy write_pain_flag 工具。
+description: 手动触发 Principles Disciple Runtime V2 痛苦诊断。用户报告 agent 卡住、循环、无响应，或要求记录/触发痛苦信号时使用。在 OpenClaw 会话中，引导 Owner 使用 /pd-pain 命令（自动绑定真实会话）。在会话外使用 `pd pain record --session <id>`。禁止写 `.state/.pain_flag`，禁止使用 legacy write_pain_flag 工具。
 disable-model-invocation: false
 ---
 
 # Pain Signal（Runtime V2）
 
-手动痛苦诊断必须通过 CLI 进入 Runtime V2：
+会话证据决定一条痛苦能否被诊断。未绑定会话的记录不携带任何轨迹证据，
+候选 confidence 低于准入阈值（0.5），全部被 admission gate 拦为
+`needs_evidence` —— Owner 的报告被保存，但不会进入内化。
+
+## 在 OpenClaw 会话中（首选）
+
+请 Owner 在发生问题的对话中运行主机命令：
+
+```text
+/pd-pain <描述问题>
+```
+
+`/pd-pain` 从 OpenClaw 取得经过认证的当前会话，并自动提交该会话的轨迹
+证据。你自己无法取得可信的会话 ID（工具执行环境不会注入）；禁止猜测、
+扫描或挑选"最新"会话。
+
+## 在会话外（CLI）
+
+绑定一个明确已知、本工作区已记录的会话 ID：
 
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- `--session <id>` 会先对工作区轨迹做校验：会话不存在时以
+  `session_not_found` 失败，不会写入任何内容。
+- 不带 `--session` 的记录是允许的 unbound Owner 报告，但不附带证据，
+  候选大概率被 admission gate 拦为 `needs_evidence` —— CLI 输出会明确
+  提示这一点。
+
 ## 禁止
 
 - 不要直接写 `.state/.pain_flag`。
 - 不要用 `write_file`、shell 重定向、`Set-Content`、`Out-File`、`node -e` 或任何文件写入方式创建 `.state/.pain_flag`。
 - 不要使用 `write_pain_flag`。这是 legacy 路径。
+- 不要猜测、扫描或推断会话 ID。使用 `/pd-pain`，或使用 Owner 明确提供的 ID。
 
 ## 验证
 
@@ -27,4 +52,7 @@ pd candidate list --workspace "<workspace>" --json
 pd runtime flow show --workspace "<workspace>" --json
 ```
 
-成功标准是 `candidateIds` 和 `ledgerEntryIds` 都非空。
+成功标准是候选被**准入**（admitted），而不只是被生成：检查
+`admissionResults` 中的 `admitted` 决策和 `ledgerEntryIds` 非空。
+`needs_evidence` 或 `deferred` 的候选没有被内化 —— 若全部候选被拦截，
+请用 `/pd-pain` 或 `--session` 重新记录，让诊断携带真实轨迹证据。

package/plugin/dist/templates/langs/zh/skills/pd-runtime-v2/SKILL.md

@@ -18,8 +18,10 @@ disable-model-invocation: false
 
 手动入口：
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
+`--session` 把报告绑定到已记录的会话（先校验），让诊断携带真实轨迹
+证据；不带它则是无证据的 unbound Owner 报告，候选大概率被拦。
 
 禁止入口：
 - 不要写 `.state/.pain_flag`。

package/plugin/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "principles-disciple",
   "name": "Principles Disciple",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
-  "version": "1.226.0",
+  "version": "1.227.0",
   "activation": {
     "onStartup": true,
     "onCapabilities": [

package/plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "principles-disciple",
-  "version": "1.226.0",
+  "version": "1.227.0",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
   "type": "module",
   "main": "./dist/index.js",

package/plugin/templates/langs/en/skills/pd-cli-operator/SKILL.md

@@ -10,15 +10,22 @@ Use the `pd` CLI as the supported operator surface. Do not modify PD state files
 
 ## Runtime V2 Pain Diagnosis
 
-Manual pain diagnosis:
+Manual pain diagnosis (bind a recorded session so diagnosis carries real
+trajectory evidence):
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- Without `--session` the record is an honest unbound Owner report: no
+  trajectory evidence, candidates likely gated (`needs_evidence`) by the
+  admission threshold — the CLI output warns about this.
+- `--session <id>` is validated up front; a missing session fails with
+  `session_not_found` before anything is written.
+
 Success requires:
 - `status` is `succeeded`
-- `candidateIds` is non-empty
-- `ledgerEntryIds` is non-empty
+- candidates are ADMITTED, not merely generated: check `admissionResults` /
+  `candidateOutcomes` for `admitted` decisions and non-empty `ledgerEntryIds`
 
 Forbidden:
 - Do not write `.state/.pain_flag`.

package/plugin/templates/langs/en/skills/pd-pain-signal/SKILL.md

@@ -1,22 +1,50 @@
 ---
 name: pd-pain-signal
-description: Manually trigger a Principles Disciple Runtime V2 pain diagnosis. Use this when the user reports the agent is stuck, looping, unresponsive, or asks to record/trigger a pain signal. Mandatory path: use `pd pain record`; never write `.state/.pain_flag` and never use legacy write_pain_flag tooling.
+description: Manually trigger a Principles Disciple Runtime V2 pain diagnosis. Use this when the user reports the agent is stuck, looping, unresponsive, or asks to record/trigger a pain signal. In an OpenClaw session, direct the Owner to the /pd-pain command (it binds the real session automatically). From outside a session, use `pd pain record --session <id>`. Never write `.state/.pain_flag` and never use legacy write_pain_flag tooling.
 disable-model-invocation: false
 ---
 
 # Pain Signal (Runtime V2)
 
-Manual pain diagnosis must enter Runtime V2 through the CLI:
+Session evidence is what makes a pain diagnosable. A pain recorded without a
+session carries no trajectory evidence, its candidates score below the
+admission threshold (0.5) and are gated as `needs_evidence` — the Owner's
+report is stored, but nothing is internalized.
+
+## In an OpenClaw session (preferred)
+
+Ask the Owner to run the host command in the conversation where the pain
+occurred:
+
+```text
+/pd-pain <describe the issue>
+```
+
+`/pd-pain` receives the authenticated current session from OpenClaw and
+submits the session's trajectory evidence automatically. You cannot obtain a
+trusted session ID yourself (none is injected into tool executions); never
+guess, scan, or pick the "latest" session.
+
+## Outside a session (CLI)
+
+Bind an explicitly known session id recorded in this workspace:
 
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- `--session <id>` is validated against the workspace trajectory: a missing
+  session fails with `session_not_found` before anything is written.
+- Recording without `--session` is allowed as an unbound Owner report, but it
+  attaches no evidence and its candidates will likely be gated
+  (`needs_evidence`) by the admission gate — the CLI output says so explicitly.
+
 ## Forbidden
 
 - Do not write `.state/.pain_flag` directly.
 - Do not use `write_file`, shell redirection, `Set-Content`, `Out-File`, `node -e`, or any other file-writing method to create `.state/.pain_flag`.
 - Do not use `write_pain_flag`. That was a legacy path.
+- Do not guess, scan for, or infer a session ID. Use `/pd-pain` or an id the Owner provides.
 
 ## Verify
 
@@ -27,4 +55,8 @@ pd candidate list --workspace "<workspace>" --json
 pd runtime flow show --workspace "<workspace>" --json
 ```
 
-Success requires non-empty `candidateIds` and `ledgerEntryIds`.
+Success requires admitted candidates, not merely generated ones: check
+`admissionResults` for `admitted` decisions and non-empty `ledgerEntryIds`.
+Candidates reported as `needs_evidence` or `deferred` were NOT internalized —
+if all candidates are gated, re-record with `/pd-pain` or `--session` so the
+diagnosis carries real trajectory evidence.

package/plugin/templates/langs/en/skills/pd-runtime-v2/SKILL.md

@@ -18,8 +18,11 @@ Automatic:
 
 Manual:
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
+`--session` binds the report to a recorded session (validated up front) so
+diagnosis carries real trajectory evidence; without it the record is an
+unbound Owner report with no evidence and candidates will likely be gated.
 
 Forbidden:
 - Do not write `.state/.pain_flag`.

package/plugin/templates/langs/zh/skills/pd-cli-operator/SKILL.md

@@ -10,15 +10,20 @@ disable-model-invocation: false
 
 ## Runtime V2 痛苦诊断
 
-手动痛苦诊断：
+手动痛苦诊断（绑定已记录的会话，让诊断携带真实轨迹证据）：
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- 不带 `--session` 的记录是诚实的 unbound Owner 报告：没有轨迹证据，
+  候选大概率被准入阈值拦为 `needs_evidence` —— CLI 输出会明确警告。
+- `--session <id>` 会先校验；会话不存在时以 `session_not_found` 失败，
+  不会写入任何内容。
+
 成功标准：
 - `status` 是 `succeeded`
-- `candidateIds` 非空
-- `ledgerEntryIds` 非空
+- 候选被**准入**而非仅被生成：检查 `admissionResults` /
+  `candidateOutcomes` 中的 `admitted` 决策和 `ledgerEntryIds` 非空
 
 禁止：
 - 不要写 `.state/.pain_flag`。

package/plugin/templates/langs/zh/skills/pd-pain-signal/SKILL.md

@@ -1,22 +1,47 @@
 ---
 name: pd-pain-signal
-description: 手动触发 Principles Disciple Runtime V2 痛苦诊断。用户报告 agent 卡住、循环、无响应，或要求记录/触发痛苦信号时使用。强制路径：使用 `pd pain record`；禁止写 `.state/.pain_flag`，禁止使用 legacy write_pain_flag 工具。
+description: 手动触发 Principles Disciple Runtime V2 痛苦诊断。用户报告 agent 卡住、循环、无响应，或要求记录/触发痛苦信号时使用。在 OpenClaw 会话中，引导 Owner 使用 /pd-pain 命令（自动绑定真实会话）。在会话外使用 `pd pain record --session <id>`。禁止写 `.state/.pain_flag`，禁止使用 legacy write_pain_flag 工具。
 disable-model-invocation: false
 ---
 
 # Pain Signal（Runtime V2）
 
-手动痛苦诊断必须通过 CLI 进入 Runtime V2：
+会话证据决定一条痛苦能否被诊断。未绑定会话的记录不携带任何轨迹证据，
+候选 confidence 低于准入阈值（0.5），全部被 admission gate 拦为
+`needs_evidence` —— Owner 的报告被保存，但不会进入内化。
+
+## 在 OpenClaw 会话中（首选）
+
+请 Owner 在发生问题的对话中运行主机命令：
+
+```text
+/pd-pain <描述问题>
+```
+
+`/pd-pain` 从 OpenClaw 取得经过认证的当前会话，并自动提交该会话的轨迹
+证据。你自己无法取得可信的会话 ID（工具执行环境不会注入）；禁止猜测、
+扫描或挑选"最新"会话。
+
+## 在会话外（CLI）
+
+绑定一个明确已知、本工作区已记录的会话 ID：
 
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
 
+- `--session <id>` 会先对工作区轨迹做校验：会话不存在时以
+  `session_not_found` 失败，不会写入任何内容。
+- 不带 `--session` 的记录是允许的 unbound Owner 报告，但不附带证据，
+  候选大概率被 admission gate 拦为 `needs_evidence` —— CLI 输出会明确
+  提示这一点。
+
 ## 禁止
 
 - 不要直接写 `.state/.pain_flag`。
 - 不要用 `write_file`、shell 重定向、`Set-Content`、`Out-File`、`node -e` 或任何文件写入方式创建 `.state/.pain_flag`。
 - 不要使用 `write_pain_flag`。这是 legacy 路径。
+- 不要猜测、扫描或推断会话 ID。使用 `/pd-pain`，或使用 Owner 明确提供的 ID。
 
 ## 验证
 
@@ -27,4 +52,7 @@ pd candidate list --workspace "<workspace>" --json
 pd runtime flow show --workspace "<workspace>" --json
 ```
 
-成功标准是 `candidateIds` 和 `ledgerEntryIds` 都非空。
+成功标准是候选被**准入**（admitted），而不只是被生成：检查
+`admissionResults` 中的 `admitted` 决策和 `ledgerEntryIds` 非空。
+`needs_evidence` 或 `deferred` 的候选没有被内化 —— 若全部候选被拦截，
+请用 `/pd-pain` 或 `--session` 重新记录，让诊断携带真实轨迹证据。

package/plugin/templates/langs/zh/skills/pd-runtime-v2/SKILL.md

@@ -18,8 +18,10 @@ disable-model-invocation: false
 
 手动入口：
 ```bash
-pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --json
+pd pain record --reason "<reason>" --score <0-100> --workspace "<workspace>" --session "<session-id>" --json
 ```
+`--session` 把报告绑定到已记录的会话（先校验），让诊断携带真实轨迹
+证据；不带它则是无证据的 unbound Owner 报告，候选大概率被拦。
 
 禁止入口：
 - 不要写 `.state/.pain_flag`。