pi-cohort 3.0.0 → 3.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +18 -0
  2. package/README.md +11 -1
  3. package/package.json +9 -3
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # Changelog
2
2
 
3
+ ## [3.0.2] - 2026-07-05
4
+
5
+ Branding, funding, and gallery preview. No behavior change.
6
+
7
+ ### Added
8
+ - **Logo + pi.dev gallery preview.** Repo-root `pi-cohort.png` (640x640), shown in the README and wired as `pi.image` for the pi.dev catalog.
9
+ - **Buy Me a Coffee funding.** `funding` in `package.json`, `.github/FUNDING.yml`, and a README badge.
10
+
11
+ ### Changed
12
+ - README polish; dropped a stale "in this fork" self-reference.
13
+
14
+ ## [3.0.1] - 2026-07-04
15
+
16
+ Tagged releases now get GitHub Release notes automatically, sourced from the CHANGELOG rather than an LLM or external API.
17
+
18
+ ### Added
19
+ - **`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`.
20
+
3
21
  ## [3.0.0] - 2026-07-02
4
22
 
5
23
  Completes the `pi-subagents` -> `pi-cohort` rename by rebranding the last user-facing identifiers that still carried the old name.
package/README.md CHANGED
@@ -1,5 +1,11 @@
1
+ <p align="center">
2
+ <img src="https://raw.githubusercontent.com/jjuraszek/pi-cohort/main/pi-cohort.png" alt="pi-cohort" width="180">
3
+ </p>
4
+
1
5
  # pi-cohort
2
6
 
7
+ [![Buy Me A Coffee](https://img.shields.io/badge/Buy%20Me%20A%20Coffee-donate-yellow?logo=buymeacoffee&logoColor=black)](https://buymeacoffee.com/jjurasszek)
8
+
3
9
  `pi-cohort` lets Pi delegate work to focused child agents. Use it for code review, scouting, implementation, parallel audits, saved workflows, background jobs, and anything else that benefits from a second or third set of model eyes.
4
10
 
5
11
  ## Installation
@@ -553,7 +559,7 @@ Chains are reusable workflows stored separately from agent files. Use `.chain.md
553
559
 
554
560
  \* Aggregated across every level from cwd to the git root; nearest wins.
555
561
 
556
- Chain roots are read **flat** (top-level `*.chain.md` / `*.chain.json` only), matching agent discovery in this fork; nested subdirectories are not scanned. Project chains aggregate `<level>/.pi/chains` across the same git-root walk as agents, nearest level wins. If both `.chain.md` and `.chain.json` define the same parsed runtime chain name in the same scope, `.chain.json` wins. If user and project scopes define the same parsed runtime chain name, the project chain wins. Chains support the same optional `package` frontmatter as agents; `name: review-flow` plus `package: code-analysis` runs as `code-analysis.review-flow` (the package comes from frontmatter, not the directory).
562
+ Chain roots are read **flat** (top-level `*.chain.md` / `*.chain.json` only), matching agent discovery in pi-cohort; nested subdirectories are not scanned. Project chains aggregate `<level>/.pi/chains` across the same git-root walk as agents, nearest level wins. If both `.chain.md` and `.chain.json` define the same parsed runtime chain name in the same scope, `.chain.json` wins. If user and project scopes define the same parsed runtime chain name, the project chain wins. Chains support the same optional `package` frontmatter as agents; `name: review-flow` plus `package: code-analysis` runs as `code-analysis.review-flow` (the package comes from frontmatter, not the directory).
557
563
 
558
564
  Example:
559
565
 
@@ -1212,3 +1218,7 @@ The main runtime files are:
1212
1218
  | `src/intercom/intercom-bridge.ts` | Runtime intercom bridge instructions and diagnostics. |
1213
1219
  | `src/extension/schemas.ts` / `src/shared/types.ts` | Tool schemas, shared types, and event constants. |
1214
1220
  | `test/unit/` / `test/integration/` | Unit and loader-based integration tests. |
1221
+
1222
+ ## Support
1223
+
1224
+ If `pi-cohort` is useful, consider [buying me a coffee](https://buymeacoffee.com/jjurasszek).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-cohort",
3
- "version": "3.0.0",
3
+ "version": "3.0.2",
4
4
  "description": "Delegate Pi work to focused child agents: code review, scouting, implementation, parallel audits, saved chains, and background jobs.",
5
5
  "author": "Jacek Juraszek",
6
6
  "license": "MIT",
@@ -34,10 +34,11 @@
34
34
  "CHANGELOG.md"
35
35
  ],
36
36
  "scripts": {
37
+ "check:agents-core": "node scripts/check-agents-core.mjs",
37
38
  "test": "npm run test:unit",
38
39
  "test:unit": "node --experimental-strip-types --test test/unit/*.test.ts",
39
40
  "test:integration": "node --experimental-transform-types --import ./test/support/register-loader.mjs --test test/integration/*.test.ts",
40
- "test:all": "npm run test:unit && npm run test:integration"
41
+ "test:all": "npm run check:agents-core && npm run test:unit && npm run test:integration"
41
42
  },
42
43
  "pi": {
43
44
  "extensions": [
@@ -48,7 +49,12 @@
48
49
  ],
49
50
  "prompts": [
50
51
  "./prompts"
51
- ]
52
+ ],
53
+ "image": "https://raw.githubusercontent.com/jjuraszek/pi-cohort/main/pi-cohort.png"
54
+ },
55
+ "funding": {
56
+ "type": "buymeacoffee",
57
+ "url": "https://buymeacoffee.com/jjurasszek"
52
58
  },
53
59
  "peerDependencies": {
54
60
  "@earendil-works/pi-agent-core": "*",