@llblab/pi-actors 0.14.1 → 0.14.2

package/BACKLOG.md

@@ -20,7 +20,7 @@ Continue progressive component/pipeline expansion in small validated slices; rea
 
 - Add another task-first high-level pipeline candidate from the design map.
   - Priority: Medium.
-  - Status: `pipeline-release-readiness`, `pipeline-repo-health`, `pipeline-async-run-ops`, `pipeline-docs-maintenance`, `pipeline-media-library`, and `pipeline-artifact-bundle` landed. `pipeline-media-library` required playlist output-mode parameterization, then reused playlist and artifact-report cells. `pipeline-artifact-bundle` reused artifact-write, artifact-manifest, validation, manifest-write, and actor-message cells.
+  - Status: `pipeline-release-readiness`, `pipeline-repo-health`, `pipeline-async-run-ops`, `pipeline-docs-maintenance`, `pipeline-media-library`, and `pipeline-artifact-bundle` landed. `pipeline-release-readiness` now includes package-summary evidence before validation/review. `pipeline-media-library` required playlist output-mode parameterization, then reused playlist and artifact-report cells. `pipeline-artifact-bundle` reused artifact-write, artifact-manifest, validation, manifest-write, and actor-message cells.
   - Scope: Reassess `docs/task-first-recipes.md` for the next high-value task cell, then implement only the minimum missing cells needed for that task.
   - Exit: Another task-first pipeline lands with docs, package validation, and a note about which missing atoms/utilities it required.
 

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.14.2: Release Readiness Package Evidence
+
+- `[Recipe Library]` Added `utility-package-summary` evidence to `pipeline-release-readiness` between changelog extraction and validation. Impact: release readiness reports can consider package metadata and package contents summary without adding publish automation.
+- `[Docs]` Updated task-first and recipe-library docs to describe the enriched release-readiness pipeline. Impact: the documented task-first candidate map now matches the implemented recipe composition.
+
 ## 0.14.1: Backlog Vocabulary Reconciliation
 
 - `[Docs]` Reconciled backlog status text after the message-only inspection release. Impact: project context no longer claims `inspect view=events` is retained and describes operations snapshots as actor-message tails instead of event tails.

package/docs/recipe-library.md

@@ -69,7 +69,7 @@ inspect target=run:docs-review view=tail
 Pipeline recipes demonstrate second-order composition:
 
 - `recipes/subagent-review-coordinator.json`: Lens reviewers → verifier → merger → judge → normalizer.
-- `recipes/pipeline-release-readiness.json`: Task-first release cell: changelog section → validation → release review → artifact report.
+- `recipes/pipeline-release-readiness.json`: Task-first release cell: changelog section → package summary → validation → release review → artifact report.
 - `recipes/pipeline-repo-health.json`: Task-first repository-health cell: git status/log → docs index → validation → normalized artifact report.
 - `recipes/pipeline-async-run-ops.json`: Task-first async-run operations cell: run summary → actor-message tail → normalized operations report → artifact report.
 - `recipes/pipeline-review-readiness.json`: Release/readiness gate over selected lenses.

package/docs/task-first-recipes.md

@@ -49,7 +49,7 @@ Existing seeds:
 
 Implemented seed:
 
-- `pipeline-release-readiness`: changelog section → validation wrapper → release review coordinator → artifact report.
+- `pipeline-release-readiness`: changelog section → package summary → validation wrapper → release review coordinator → artifact report.
 
 ### Repository Health Cell
 
@@ -226,7 +226,7 @@ Prefer adding a high-level recipe when at least three cells already exist and th
 
 Good next candidates for the standard library after the first task-first wave:
 
-1. Package/release metadata enrichment: use `utility-package-summary` with changelog and validation cells to make release-readiness reports more evidence-rich without adding publish automation.
+1. Package/release metadata enrichment: implemented in `pipeline-release-readiness` by adding `utility-package-summary` between changelog extraction and validation, making release-readiness reports more evidence-rich without adding publish automation.
 2. Artifact packaging and manifesting: implemented as `pipeline-artifact-bundle`, which composes optional validation, `pipeline-artifact-write`, `utility-artifact-manifest`, deterministic manifest writing, and an actor-message handoff when the caller explicitly requests filesystem writes.
 3. Async run cleanup planning: extend async-run operations with stale-run classification and recommended `message`, `cancel`, or `kill` controls, keeping actual control execution operator-gated.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-actors",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "private": false,
   "description": "Actor runtime and orchestrator for agent-managed local processes",
   "type": "module",

package/recipes/pipeline-release-readiness.json

@@ -3,6 +3,7 @@
   "async": true,
   "imports": {
     "changelog": "utility-changelog-section.json",
+    "package": "utility-package-summary.json",
     "validation": "utility-validation-wrapper.json",
     "review": "subagent-review-coordinator.json",
     "artifact": "pipeline-artifact-report.json"
@@ -10,6 +11,7 @@
   "args": [
     "scope:path",
     "version:string",
+    "package_json:path",
     "validation_command:string",
     "artifact_path:path",
     "lenses:array",
@@ -22,6 +24,7 @@
   "defaults": {
     "scope": ".",
     "version": "0.7.1",
+    "package_json": "{scope}/package.json",
     "validation_command": "npm run validate",
     "artifact_path": "./release-readiness.md",
     "lenses": [
@@ -48,6 +51,13 @@
         "version": "{version}"
       }
     },
+    {
+      "name": "package",
+      "values": {
+        "package_json": "{package_json}",
+        "repo": "{scope}"
+      }
+    },
     {
       "name": "validation",
       "values": {
@@ -58,7 +68,7 @@
     {
       "name": "review",
       "values": {
-        "scope": "Release scope {scope} for version {version}. Use changelog and validation output from stdin.",
+        "scope": "Release scope {scope} for version {version}. Use changelog, package summary, and validation output from stdin.",
         "lenses": "{lenses}",
         "claim": "Version {version} is ready for release or the remaining blockers are explicitly identified.",
         "reviewer_model": "{reviewer_model}",