@akagilnc/pi-workflow-roles 0.1.5063 → 0.1.5068

package/THIRD_PARTY_NOTICES.md

@@ -9,23 +9,12 @@ license authority. Do not treat them as dual-licensing the package.
 Upstream provenance: [mattpocock/skills](https://github.com/mattpocock/skills).
 
 `ak-role setup` installs the following skills from that upstream repository
-into the user's machine Skill directory. The repository retains historical
-snapshots under `resources/methods/` until after release, but they are not
-included in the npm package.
-
-- `tdd` — historical repository snapshot from upstream
-  `skills/engineering/tdd` at commit `8b36d4fb2635b3c21998dcd8144439c9e5ba7302`
-  (tag `v1.2.2`) (#109)
-- `diagnosing-bugs` — historical repository snapshot from
-  upstream `skills/engineering/diagnosing-bugs` at the same commit/tag, with
-  package adaptation `fixer-boundary-no-external-skill-chain` so the Fixer
-  method cannot automatically launch architecture Grill or other role-external
-  Skill chains (#110)
-- `resolving-merge-conflicts` — historical repository snapshot from
-  upstream `skills/engineering/resolving-merge-conflicts` at the same commit/tag, with
-  package adaptation `merger-merge-only-escalate-new-intent` so Merger stays merge-only,
-  escalates new intent/authority instead of guessing, and does not inherit upstream
-  unconditional-resolution or rebase workflow (#114)
+into the user's machine Skill directory. Neither the repository nor the npm
+package carries copies of them.
+
+- `tdd`
+- `diagnosing-bugs`
+- `resolving-merge-conflicts`
 
 The complete upstream MIT license text follows.
 
@@ -55,8 +44,7 @@ SOFTWARE.
 
 ## First-party method (not third-party)
 
-- `ak-cross-m-review` — historical repository snapshot under `resources/methods/ak-cross-m-review/`
-  from [Akagilnc/ak-cross-m-review](https://github.com/Akagilnc/ak-cross-m-review)
-  commit `57b10e2cea9ff008e2b36b98b55610e58cdfd512` (VERSION `0.5.2.0`, MIT,
-  Copyright (c) 2026 Akagi). `packageAdaptation` = `verbatim-upstream`. This is
-  first-party material owned by the same author line, not a third-party skill.
+- `ak-cross-m-review` — `ak-role setup` installs it from
+  [Akagilnc/ak-cross-m-review](https://github.com/Akagilnc/ak-cross-m-review)
+  (MIT, Copyright (c) 2026 Akagi). This is first-party material owned by the
+  same author line, not a third-party skill.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akagilnc/pi-workflow-roles",
-  "version": "0.1.5063",
+  "version": "0.1.5068",
   "description": "Soul-bound workflow roles for Pi",
   "type": "module",
   "license": "Apache-2.0",
@@ -36,8 +36,6 @@
     "schemas",
     "packets",
     "resources",
-    "!resources/methods",
-    "!resources/methods/**",
     "README.md",
     "LICENSE",
     "THIRD_PARTY_NOTICES.md",

package/resources/836-deleted-machine-instruction-inventory.md

@@ -9,7 +9,7 @@
 | `compliance-transport.ts` `AUDITOR_DOSSIER_PROMPT` | `本 run 卷宗已就绪。` | 改为台院同形路径指针。 |
 | `doctor-role.ts` case catalog | `provenance: "由留存 session 字节推导，封入受理回执。"` | 删。catalog 只留 cost 与证据指针。 |
 | `collector-role.ts` bounceInfrastructure | `请省略该字段后重新提交。` | 代码打回推翻自报已删。 |
-| `reviewer-role.ts` output description | `Standards/Spec 评审腿由 runtime 以取证子会话代跑…` | #836 改为「本席自调 code-review skill」。#917 后随包方法为 `ak-cross-m-review`；`resources/methods/code-review/` 已删，现役指针见 `resources/methods/ak-cross-m-review/SKILL.md`。 |
+| `reviewer-role.ts` output description | `Standards/Spec 评审腿由 runtime 以取证子会话代跑…` | #836 改为「本席自调 code-review skill」。#917 后方法为 `ak-cross-m-review`；#1043 起不再随包，由 `ak-role setup` 从 Akagilnc/ak-cross-m-review 装入机器 `~/.agents/skills`。 |
 | `run-lifecycle.ts` A4.1 | `[ak-role:resume-continue]` | 生产码不再含此字面量。结算只跳过空轮与引擎指针续跑。 |
 | `run-lifecycle.ts` A4.2 | `重新读 <path>` | 前轮已删改写。 |
 | `submission-correctable-error.ts` A4.5 | `终局交卷并非本轮唯一工具调用。` | 删。Pi/ACP `deliverSubmissionRejection` 不再注入该句。 |

package/souls/countersign.md

@@ -22,11 +22,11 @@
 对于修复票，判断根因是什么、证据在哪；对于新功能设计票，判断设计是不是合理，是不是陛下想要的方向。以及因果链本身站不站得住。
 此步不成立即封驳，不必再走后三步。
 
-**三、相抵** 票面，相关票与在飞分支与法源有无抵触。
+**三、相抵** 票面，相关票与在飞分支与法源有无抵触。票面自相抵同为相抵。
 
 **四、缺失** 法源要求的，票面有没有漏：适用法只查两类：票面与某条 ADR 决定相抵的，和把某条决定留给别的票承接的，票面须写明该条与「由 #x 承接」；这两类之外的 ADR 没引不算缺失，不得为此封驳；验收面须覆盖票面每条主张；票面里每一条行为都须答得出《送庭前三问》第一问——由哪条接缝、哪条 run 担它：起、停、续、终、接各归谁没写的行为，即缺失；前置产物、决定、答复须在；承重主张的源头不存在、不支持、已过时，同为缺失。缺失列表在能力范围内一次扫完，尽量避免因缺失导致多轮往返。
 
-**五、擅加** 票面有没有超出法源的机制、约束、验收、术语。
+**五、擅加** 票面有没有超出法源的机制、约束、验收、术语。票面按类各定一套行为或文案的，就是在要分类机制；陛下没点名要的，上呈，附单一做法。
 
 各步取证按《审法·取证授权》：工具与方式不受限，读码、开卷、传召、下探针皆可；不得删除、覆写或移动 worktree 与临时目录之外的既存路径（《审法·取证边界》）。交付时候清理回原样
 

package/souls/ticket-law.md

@@ -4,7 +4,7 @@
 
 * 陛下要什么——先用一两句写出他真正要的结果；后附撑这个读法的原话，逐字，带 uuid；源卷没有 id 的，给起居录里的来源标识。他的质问——他在问这张票、这条约束凭什么存在——要用事实或法源答到他问的那个点上，不是答字面；答不到的票不送庭，上呈。没有原话的票，写它出自哪张父票（授权在父票的对话里，给 uuid），或现状违反了哪条法源。
 * 现象——现在看得见的错是什么；一个能复现、能开卷核的实例就够。新造的东西没有现象，写要造什么。
-* 目的——改完以后看得见的行为是什么。
+* 目的——改完以后看得见的行为是什么。一句；不按现象实例逐个定行为或文案，实例只作验收样本。
 * 怎么验——从真实入口走一遍，看见什么算对；覆盖票面每条主张。
 * 适用法——`docs/adr/...md` 路径，一行一条，不必复述其决定。只有本票与它某条决定相抵、或把某条决定留给别的票承接时，才在那一行写明是哪一条。