@agwab/pi-workflow 0.1.0 → 0.1.1

package/docs/usage.md

@@ -576,30 +576,3 @@ for those tools. Object-form custom tool `extensions` are merged with this
 built-in mapping and deduplicated for the subagent launch. Web calls can still
 fail when network access, provider credentials, browser state, or quota are
 unavailable; research workflows should report those limits instead of guessing.
-
-## Release checks
-
-This repository releases through GitHub Actions, following the same release shape as `@agwab/pi-subagent`:
-
-- scoped npm package name: `@agwab/pi-workflow`
-- `private: false`
-- `publishConfig.access: public`
-- Pi package manifest in `package.json`
-- README + `docs/usage.md`
-- manual `.github/workflows/publish.yml` dispatch with npm provenance
-
-Before publishing, maintainers should run the public checks and inspect the package surface:
-
-```bash
-npm run release:check
-```
-
-`npm run release:check` verifies package metadata, npm login, unpublished version, script syntax, typecheck, unit tests, e2e smoke, build, package contents, local-path/secret-like text, and `npm publish --dry-run`.
-
-After an approved release plan, dispatch the release automation instead of publishing locally:
-
-```bash
-npm run release:dispatch -- <version> --watch
-```
-
-See [`docs/release.md`](./release.md) for the maintainer release checklist, CI workflow, publish workflow, and post-release verification steps.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agwab/pi-workflow",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Workflow orchestration for Pi subagents.",
   "private": false,
   "type": "module",
@@ -12,7 +12,6 @@
     "workflows",
     "skills",
     "docs/usage.md",
-    "docs/release.md",
     "docs/assets/readme/logo.svg",
     "docs/assets/readme/stage-types.png",
     "docs/assets/readme/deep-research-flow.png",
@@ -48,7 +47,7 @@
     "validate": "npm run check:scripts && npm run typecheck && npm run test:unit",
     "test": "npm run test:unit",
     "test:build": "rm -rf .tmp/unit && tsc -p tsconfig.json --outDir .tmp/unit --noEmit false",
-    "test:unit": "npm run test:build && node --test test/unit/*.test.mjs",
+    "test:unit": "npm run build && npm run test:build && node --test test/unit/*.test.mjs",
     "e2e": "node test/e2e/run.mjs",
     "pack:dry": "npm pack --dry-run --json",
     "prepack": "npm run build",

package/docs/release.md

@@ -1,89 +0,0 @@
-# pi-workflow release process
-
-This repository releases `@agwab/pi-workflow` through the GitHub Actions **Publish** workflow. Local commands validate and dispatch the approved workflow; they should not replace the CI publish path.
-
-## Rules
-
-Do not publish, tag, push a release commit, or dispatch release automation until the exact release plan is approved. The plan must include:
-
-- target version
-- semver rationale
-- changelog/release notes
-- validation to run
-- publish target (`@agwab/pi-workflow` on npm)
-- downstream dependency/lockfile impact, especially bundled `@agwab/pi-subagent` and `pi-web-access`
-
-Version bumps are release-task-only. The Publish workflow runs `npm version <target>` and pushes the release commit/tag after validation.
-
-## Local validation
-
-Run the full release gate before asking for final approval:
-
-```bash
-npm run release:check
-```
-
-`release:check` verifies package metadata, npm login, unpublished version, script syntax, typecheck, unit tests, e2e smoke, build, package contents, local-path/secret-like text, and `npm publish --dry-run`.
-
-For normal CI-style validation without npm login or unpublished-version checks, run:
-
-```bash
-npm run validate
-npm run e2e
-npm run pack:dry
-```
-
-## Dispatching a release
-
-After approval and after `main` is clean and pushed:
-
-```bash
-npm run release:dispatch -- <version> --watch
-```
-
-The dispatch script checks that:
-
-- the current branch is `main`
-- the working tree is clean
-- `HEAD` matches `origin/main`
-- the target version is semver-like
-
-Then it dispatches `.github/workflows/publish.yml` with `version=<version>`.
-
-## GitHub Actions
-
-### CI
-
-`.github/workflows/ci.yml` runs on pull requests and pushes to `main`:
-
-1. `npm ci --legacy-peer-deps`
-2. `npm run validate`
-3. `npm run e2e`
-4. `npm run pack:dry`
-
-### Publish
-
-`.github/workflows/publish.yml` is manual-only (`workflow_dispatch`) and only runs on `main`. It:
-
-1. installs dependencies with npm
-2. configures the GitHub Actions bot git author
-3. runs `npm version <target>` if needed and creates `v<target>`
-4. checks whether `@agwab/pi-workflow@<target>` already exists on npm
-5. runs `npm run release:check` for unpublished versions
-6. runs validation-only checks for already-published versions
-7. publishes to npm with provenance when needed
-8. pushes the release commit and tag when needed
-9. creates a GitHub release when missing
-
-## Post-release verification
-
-After the workflow completes, verify and report:
-
-```bash
-npm view @agwab/pi-workflow@<version> version
-gh release view v<version>
-git fetch origin --tags
-git rev-parse v<version>
-```
-
-Also report the GitHub Actions run URL and any skipped steps, such as publish skipped because the npm version already existed.