pi-crew 0.11.20 → 0.11.21

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-crew",
-	"version": "0.11.20",
+	"version": "0.11.21",
 	"description": "Pi extension for coordinated AI teams, workflows, worktrees, and async task orchestration",
 	"author": "baphuongna",
 	"license": "MIT",

package/skills/real-test-pi-crew/SKILL.md

@@ -1256,6 +1256,27 @@ When a tier fails, the recovery is usually quick. Match the symptom to the cause
 | `team action='schedule' interval=<ms>` always says `Invalid schedule "<N>ms". Use "5m", …` | handle-schedule builds `${interval}ms`; both interval parsers lacked an `ms` unit — every numeric interval died. Fixed 2026-09-21 | The suggested "5m" formats only work via `cron`/`once` params, not `interval` (interval is schema-typed as a plain ms number) |
 | Runs keep appearing under one scheduled job; children of YOUR pi process; machine thrashing | **Interval ≥ 2^31-1 ms (≥24.8 days) overflowed the Node timer to a 1ms hot loop** (fixed 2026-09-22 — clamped hops). Check `.crew/audit/prune.jsonl` for interleaved auto-prunes. Contain: remove job, then `pkill -f '[b]ackground-runner.ts --cwd <root>'` | Any new timer scheduling must clamp below MAX_TIMER_DELAY_MS — grep for `setInterval(`/`setTimeout(` with computed delays |
 
+## Release gate — battery → push → GitHub Actions GREEN → publish (canonical, 2026-10-14)
+
+Local `npm run ci` là LINUX-ONLY — không thay được matrix 3-OS của GitHub Actions.
+Live-proven 2026-10-14: **0.11.19 và 0.11.20 đều publish khi CI GitHub ĐỎ** (local ci + pre-push
+hook xanh hết) — windows fail do child-env thiếu `SYSTEMROOT` (node con không khởi tạo Winsock được,
+stdout rỗng); macOS fail do transient ECONNREFUSED khiến accepting-probe 1 lần coi holder SỐNG là
+corpse → xóa file socket + rebind (STEAL lock) — fix bằng 3-strike takeover (`process-lock.ts`).
+
+**Quy trình BẮT BUỘC cho mọi release (theo thứ tự, không bỏ bước):**
+
+1. Cập nhật skill (wave entry) + CHANGELOG heading cho version sắp release — commit.
+2. Chạy battery theo decision table (đủ tier cho paths đổi) — xanh hết.
+3. `npm version patch` (tạo release commit + tag).
+4. `git push origin main --follow-tags` — pre-push hook tự chạy full unit local.
+5. **`gh run watch <runId> --exit-status` (hoặc poll `gh run list`) — CHỜ matrix 3-OS XANH TOÀN BỘ.**
+   CI đỏ ⇒ KHÔNG publish — fix, push lại, chờ lại. (Check nhanh fail: `gh run view <id>` +
+   `gh api repos/<o>/<r>/actions/jobs/<jobId>//logs` — KHÔNG grep "not ok" mù: tên test có thể
+   chứa literal "not ok" ("malformed JSON is not ok with a message") — grep kèm assertion block.)
+6. CHỈ KHI xanh: `npm publish` → poll `npm view <pkg> dist-tags.latest` → `gh release create`.
+7. Post-release: knowledge.md entry SHIPPED + dọn branch/scratch.
+
 ## Performance budget (per-tier soft limits)
 
 | Tier | Soft limit | Hard limit | What happens over hard limit |

package/src/state/coordination/process-lock.ts

@@ -105,8 +105,20 @@ function socketAddress(name: string): SocketAddress {
 	return { address: fileSocketAddress(key), file: true };
 }
 
-/** True when a live server accepts connections on `address` (leftover-corpse probe). */
-function accepting(address: string): Promise<boolean> {
+/**
+ * Probe whether a live server accepts connections on `address` (leftover-corpse
+ * check). A single refusal is NOT trusted on file-socket platforms: macOS can
+ * return ECONNREFUSED transiently against a LIVE listener (e.g. a momentarily
+ * full listen backlog under load — live-caught in CI 2026-10-14: a foreign
+ * child flipped a held lock to "corpse", DELETED the live socket file and
+ * rebound, stealing the lock). We require TAKEOVER_REFUSALS consecutive
+ * refusals, spaced TAKEOVER_RETRY_MS apart, before declaring a corpse.
+ */
+const TAKEOVER_REFUSALS = 3;
+const TAKEOVER_RETRY_MS = 150;
+
+/** One connect-probe: true = somebody accepts; false = refused (corpse-ish). */
+function acceptingOnce(address: string): Promise<boolean> {
 	return new Promise((resolve) => {
 		const socket = net.connect(address);
 		socket.unref();
@@ -121,6 +133,14 @@ function accepting(address: string): Promise<boolean> {
 	});
 }
 
+async function accepting(address: string): Promise<boolean> {
+	for (let attempt = 0; attempt < TAKEOVER_REFUSALS; attempt++) {
+		if (attempt > 0) await new Promise((r) => setTimeout(r, TAKEOVER_RETRY_MS));
+		if (await acceptingOnce(address)) return true;
+	}
+	return false;
+}
+
 /**
  * Acquire the process lock for `name`. Resolves with a handle once THIS process
  * owns the kernel socket; rejects with {@link ProcessLockHeldError}