@akagilnc/pi-workflow-roles 0.1.2512 → 0.1.2514

package/README.md

@@ -13,6 +13,22 @@ export PATH="$HOME/.pi/agent/npm/node_modules/.bin:$PATH"
 
 Update with `pi update npm:@akagilnc/pi-workflow-roles`—never a second global `npm install -g`. Inspect with `ak-role roles` and `ak-role help <role>`; set per-seat model defaults with `ak-role config set <seat> <provider/model[:thinking]>` (callable seats plus automatic `gatekeeper` / `inspector` / `navigator`); clear a Gate officer override with `ak-role config unset <gatekeeper|inspector|notary>`; set or clear a persistent labor engine (callable roles) with `ak-role config set-engine <seat> <name>` / `ak-role config unset-engine <seat>`.
 
+### Test channel (`next`)
+
+Family / dogfood installs use the same package under dist-tag `next`, on a dedicated `HOME` so the test surface never shares AK config, ledger, book, or `PI_CODING_AGENT_DIR` with the host install. Do not mount or copy host credentials into the test home; do not use a book/worktree as a stand-in for install isolation. No second global npm.
+
+```bash
+export HOME=/path/to/test-home          # dedicated test HOME
+export PI_CODING_AGENT_DIR="$HOME/.pi/agent"
+export PATH="$PI_CODING_AGENT_DIR/npm/node_modules/.bin:$PATH"
+```
+
+- **First install of next**: `pi install npm:@akagilnc/pi-workflow-roles@next` → `ak-role roles` runs; installed version looks like `0.1.<count>-next.<shortsha>`.
+- **Advance to a newer next**: `pi update npm:@akagilnc/pi-workflow-roles@next` → `<shortsha>` becomes the new CI `head_sha` prefix (7 chars).
+- **Same-version reinstall / restore**: rerun the first-install command → idempotent; version unchanged (stamp path that only moves the dist-tag when the version is already on the registry).
+
+Publish routing (Actions, not local stamp): successful `ci` push on `main` → `latest`; successful `ci` push on an allowlisted non-main branch (see `.github/workflows/ci.yml` `push.branches`) → `next`. PR completions and failed CI never publish.
+
 ## Reading results
 
 `ak-role` is the only supported way to call the package. Every run writes its complete Terminal result to stdout—read or redirect it there, never scrape Pi session files:

package/README.zh-CN.md

@@ -13,6 +13,22 @@ export PATH="$HOME/.pi/agent/npm/node_modules/.bin:$PATH"
 
 更新用 `pi update npm:@akagilnc/pi-workflow-roles`——勿另起全局 `npm install -g`。查看能力：`ak-role roles`、`ak-role help <role>`；设席位模型默认：`ak-role config set <seat> <provider/model[:thinking]>`（可调用席位，以及自动出席的 `gatekeeper`／`inspector`／`navigator`）；清除门下省官钉：`ak-role config unset <gatekeeper|inspector|notary>`；设或清持久劳务引擎（可调用角色）：`ak-role config set-engine <seat> <name>` / `ak-role config unset-engine <seat>`。
 
+### 测试通道（`next`）
+
+家族／dogfood 安装面复用同一包，经 dist-tag `next` 取得；测试面自有 `HOME`，其下的 AK config／ledger／book 与 `PI_CODING_AGENT_DIR` 一并独立，不与宿主已装包共享。测试面不挂载、不复制宿主凭据；不以 book／worktree 冒充安装隔离。不装第二份全局 npm。
+
+```bash
+export HOME=/path/to/test-home          # 测试面自有 HOME
+export PI_CODING_AGENT_DIR="$HOME/.pi/agent"
+export PATH="$PI_CODING_AGENT_DIR/npm/node_modules/.bin:$PATH"
+```
+
+- **首次装 next**：`pi install npm:@akagilnc/pi-workflow-roles@next` → `ak-role roles` 可跑；装到的版本形如 `0.1.<count>-next.<shortsha>`。
+- **推进到新 next**：`pi update npm:@akagilnc/pi-workflow-roles@next` → 版本号里的 `<shortsha>` 变为新 CI `head_sha` 的前 7 位。
+- **同版本重装／恢复**：重跑首次安装命令 → 幂等，版本不变（对应 stamp「版本已在 registry 则只移 dist-tag」路径）。
+
+发布路由（Actions 真入口，非本地 stamp）：`ci` 在 `main` 上成功 push → `latest`；`ci` 在 allowlist 非 main 分支上成功 push（见 `.github/workflows/ci.yml` 的 `push.branches`）→ `next`。PR completion 与失败 CI 不发布。
+
 ## 读结果
 
 `ak-role` 是唯一受支持的调用方式。每次运行的完整 Terminal 结果写在 stdout——从那里读或正常重定向，不要刮 Pi session 文件：

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akagilnc/pi-workflow-roles",
-  "version": "0.1.2512",
+  "version": "0.1.2514",
   "description": "Soul-bound workflow roles for Pi",
   "type": "module",
   "license": "Apache-2.0",