pi-cohort 2.0.1 → 3.0.1

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [3.0.1] - 2026-07-04
+
+Tagged releases now get GitHub Release notes automatically, sourced from the CHANGELOG rather than an LLM or external API.
+
+### Added
+- **`release.yml` posts release notes.** A new `release-notes` job (`needs: publish`, `contents: write`) extracts the CHANGELOG section matching the pushed tag with `awk` and publishes it as the GitHub Release body via `gh release create` (falling back to `gh release edit`). No LLM or API key; only `github.token`.
+
+## [3.0.0] - 2026-07-02
+
+Completes the `pi-subagents` -> `pi-cohort` rename by rebranding the last user-facing identifiers that still carried the old name.
+
+### Changed
+- **BREAKING:** Renamed the `/subagents-doctor` slash command to `/cohort-doctor`. The old name is gone; update any muscle-memory or scripted invocations.
+- **BREAKING:** Moved the extension config file from `<PI_CODING_AGENT_DIR>/extensions/subagent/config.json` to `<PI_CODING_AGENT_DIR>/extensions/pi-cohort/config.json`, aligning it with where `pi install npm:pi-cohort` places the extension. An existing `extensions/subagent/config.json` is no longer read; move it to the new path. The same rename applies to the default intercom-bridge settings dir and the documented `instructionFile` relative-path root.
+- Rebranded the internal async widget and grand-total status keys (`subagent-async` -> `pi-cohort-async`, `subagents-grand-total` -> `pi-cohort-grand-total`). No user action required.
+
 ## [2.0.1] - 2026-07-02
 
 ### Fixed

package/README.md

@@ -188,7 +188,7 @@ Show me the current async runs.
 If something feels misconfigured, run:
 
 ```text
-/subagents-doctor
+/cohort-doctor
 ```
 
 or ask:
@@ -257,7 +257,7 @@ If a child appears stalled, needs-attention notices can show up in the parent se
 If messages do not show up, run:
 
 ```text
-/subagents-doctor
+/cohort-doctor
 ```
 
 For normal use, you do not need to configure anything. Advanced users can tune the bridge with `intercomBridge` in the configuration section below.
@@ -284,7 +284,7 @@ Skip this section until you want exact syntax.
 | `/chain agent1 "task1" -> agent2 "task2"` | Run agents in sequence |
 | `/parallel agent1 "task1" -> agent2 "task2"` | Run agents in parallel |
 | `/run-chain <chainName> -- <task>` | Launch a saved `.chain.md` or `.chain.json` workflow |
-| `/subagents-doctor` | Show read-only setup diagnostics |
+| `/cohort-doctor` | Show read-only setup diagnostics |
 
 Commands validate agent names locally, support tab completion, and send results back into the conversation.
 
@@ -394,7 +394,7 @@ Agent locations, lowest to highest priority:
 
 | Scope | Path |
 |-------|------|
-| Builtin | `<agent-dir>/extensions/subagent/agents/` |
+| Builtin | `<agent-dir>/extensions/pi-cohort/agents/` |
 | User (global) | `~/.agents/*.md` |
 | User (pi profile) | `<PI_CODING_AGENT_DIR>/agents/*.md` |
 | Project (legacy) * | `<level>/.agents/*.md` |
@@ -947,7 +947,7 @@ After a worktree parallel step completes, per-agent diff stats are appended to t
 
 ## Configuration
 
-`pi-cohort` reads optional JSON config from `<PI_CODING_AGENT_DIR>/extensions/subagent/config.json`.
+`pi-cohort` reads optional JSON config from `<PI_CODING_AGENT_DIR>/extensions/pi-cohort/config.json`.
 
 ### `PI_CODING_AGENT_DIR`
 
@@ -1031,7 +1031,7 @@ Controls whether subagents receive runtime intercom coordination instructions an
 Fields:
 
 - `mode`: default `always`; use `fork-only` to inject only for forked runs, or `off` to disable the bridge.
-- `instructionFile`: optional Markdown template replacing the default bridge instructions. `{orchestratorTarget}` is interpolated. Relative paths resolve from `~/.pi/agent/extensions/subagent/`.
+- `instructionFile`: optional Markdown template replacing the default bridge instructions. `{orchestratorTarget}` is interpolated. Relative paths resolve from `~/.pi/agent/extensions/pi-cohort/`.
 
 Bridge activation also requires `pi-intercom` to be installed and enabled through `pi install npm:pi-intercom` or a legacy local extension checkout, a targetable current session name or fallback alias, and `pi-intercom` in any explicit agent `extensions` allowlist.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-cohort",
-  "version": "2.0.1",
+  "version": "3.0.1",
   "description": "Delegate Pi work to focused child agents: code review, scouting, implementation, parallel audits, saved chains, and background jobs.",
   "author": "Jacek Juraszek",
   "license": "MIT",
@@ -34,10 +34,11 @@
     "CHANGELOG.md"
   ],
   "scripts": {
+    "check:agents-core": "node scripts/check-agents-core.mjs",
     "test": "npm run test:unit",
     "test:unit": "node --experimental-strip-types --test test/unit/*.test.ts",
     "test:integration": "node --experimental-transform-types --import ./test/support/register-loader.mjs --test test/integration/*.test.ts",
-    "test:all": "npm run test:unit && npm run test:integration"
+    "test:all": "npm run check:agents-core && npm run test:unit && npm run test:integration"
   },
   "pi": {
     "extensions": [

package/skills/pi-cohort/SKILL.md

@@ -33,7 +33,7 @@ Humans often use the slash-command layer instead:
 - `/chain` — launch a chain of steps
 - `/parallel` — launch top-level parallel tasks
 - `/run-chain` — launch a saved `.chain.md` or `.chain.json` workflow
-- `/subagents-doctor` — diagnose setup, discovery, async paths, and intercom bridge state
+- `/cohort-doctor` — diagnose setup, discovery, async paths, and intercom bridge state
 
 Prefer the tool when you are writing agent logic. Prefer the slash commands when
 you are guiding a human through an interactive flow.
@@ -349,7 +349,7 @@ Use diagnostics when setup or child startup looks wrong:
 subagent({ action: "doctor" })
 ```
 
-Humans can use `/subagents-doctor` for the same read-only report. It checks runtime paths, discovery counts, async support, current session context, and intercom bridge state.
+Humans can use `/cohort-doctor` for the same read-only report. It checks runtime paths, discovery counts, async support, current session context, and intercom bridge state.
 
 ### Subagent control
 
@@ -497,7 +497,7 @@ Or inspects unresolved asks first:
 intercom({ action: "pending" })
 ```
 
-If intercom messages do not show up, run `subagent({ action: "doctor" })` or `/subagents-doctor`.
+If intercom messages do not show up, run `subagent({ action: "doctor" })` or `/cohort-doctor`.
 
 ## Management Mode
 

package/src/extension/config.ts

@@ -4,13 +4,13 @@ import type { ExtensionConfig } from "../shared/types.ts";
 import { getAgentDir } from "../shared/utils.ts";
 
 export function loadConfig(): ExtensionConfig {
-	const configPath = path.join(getAgentDir(), "extensions", "subagent", "config.json");
+	const configPath = path.join(getAgentDir(), "extensions", "pi-cohort", "config.json");
 	try {
 		if (fs.existsSync(configPath)) {
 			return JSON.parse(fs.readFileSync(configPath, "utf-8")) as ExtensionConfig;
 		}
 	} catch (error) {
-		console.error(`Failed to load subagent config from '${configPath}':`, error);
+		console.error(`Failed to load pi-cohort config from '${configPath}':`, error);
 	}
 	return {};
 }

package/src/extension/index.ts

@@ -8,7 +8,7 @@
  * Modes: single (agent + task), parallel (tasks[]), chain (chain[] with {previous})
  * Toggle: async parameter (default: false, configurable via config.json)
  *
- * Config file: ~/.pi/agent/extensions/subagent/config.json
+ * Config file: ~/.pi/agent/extensions/pi-cohort/config.json
  *   { "asyncByDefault": true, "forceTopLevelAsync": true, "maxSubagentDepth": 1, "showRosterOnStart": true, "intercomBridge": { "mode": "always", "instructionFile": "./intercom-bridge.md" }, "worktreeSetupHook": "./scripts/setup-worktree.mjs" }
  */
 

package/src/intercom/intercom-bridge.ts

@@ -22,7 +22,7 @@ function defaultIntercomConfigPath(agentDir = defaultAgentDir()): string {
 }
 
 function defaultSubagentConfigDir(agentDir = defaultAgentDir()): string {
-	return path.join(agentDir, "extensions", "subagent");
+	return path.join(agentDir, "extensions", "pi-cohort");
 }
 
 const DEFAULT_INTERCOM_TARGET_PREFIX = "subagent-chat";

package/src/shared/types.ts

@@ -929,8 +929,8 @@ export const RESULTS_DIR = path.join(TEMP_ROOT_DIR, "async-subagent-results");
 export const ASYNC_DIR = path.join(TEMP_ROOT_DIR, "async-subagent-runs");
 export const CHAIN_RUNS_DIR = path.join(TEMP_ROOT_DIR, "chain-runs");
 export const TEMP_ARTIFACTS_DIR = path.join(TEMP_ROOT_DIR, "artifacts");
-export const WIDGET_KEY = "subagent-async";
-export const GRAND_TOTAL_STATUS_KEY = "subagents-grand-total";
+export const WIDGET_KEY = "pi-cohort-async";
+export const GRAND_TOTAL_STATUS_KEY = "pi-cohort-grand-total";
 export const SLASH_RESULT_TYPE = "subagent-slash-result";
 export const SLASH_SUBAGENT_REQUEST_EVENT = "subagent:slash:request";
 export const SLASH_SUBAGENT_STARTED_EVENT = "subagent:slash:started";

package/src/slash/slash-commands.ts

@@ -557,8 +557,8 @@ export function registerSlashCommands(
 	});
 
 
-	pi.registerCommand("subagents-doctor", {
-		description: "Show subagent diagnostics",
+	pi.registerCommand("cohort-doctor", {
+		description: "Show pi-cohort diagnostics",
 		handler: async (_args, ctx) => {
 			await runSlashSubagent(pi, ctx, { action: "doctor" });
 		},