Skip to content

docs: record v0.2.0 release proof #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
VrtxOmega merged 1 commit into from
Jul 19, 2026
Merged

docs: record v0.2.0 release proof #15

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ The output is a maintainer queue, not a vibe score: labels, repair checklists, r

## Status

PCF v0.1.3 is published on [npm](https://www.npmjs.com/package/premature-contribution-firewall/v/0.1.3) and as a [GitHub release](https://github.com/VrtxOmega/premature-contribution-firewall/releases/tag/v0.1.3). It adds impact-first serious candidate scouting, the AI-assisted contribution posture gate, and stricter authority boundaries for repository context, overlap checks, lane evidence, repro claims, and MCP framing. The recommended adoption path remains read-only first: run the GitHub Action or MCP smoke path, read one artifact, and decide whether it is useful before enabling anything else.
PCF v0.2.0 is published on [npm](https://www.npmjs.com/package/premature-contribution-firewall/v/0.2.0) and as a [GitHub release](https://github.com/VrtxOmega/premature-contribution-firewall/releases/tag/v0.2.0). It adds the offline contribution lifecycle and salvage gate while preserving the impact-first serious scout, AI-assisted contribution posture gate, and fail-closed authority boundaries. The recommended adoption path remains read-only first: run one command, inspect one artifact, and decide whether it is useful before enabling anything else.

Try it in one command, no install:

Expand All @@ -27,7 +27,7 @@ npx premature-contribution-firewall preflight your-pr-draft.json

Current public state:

- Published on npm: [`premature-contribution-firewall`](https://www.npmjs.com/package/premature-contribution-firewall) with `pcf` CLI (`evaluate`, `queue`, `preflight`, `setup`) and the `pcf-mcp` stdio server bin.
- Published on npm: [`premature-contribution-firewall`](https://www.npmjs.com/package/premature-contribution-firewall) with the `pcf` CLI, including `lifecycle`, and the `pcf-mcp` stdio server bin.
- Published on the GitHub Marketplace as a read-only Action with two modes: `workflow_dispatch` queue artifact and `pull_request` PR gate (step-summary verdict, optional `fail-on` blocking, no GitHub writes).
- MCP server: `pcf-mcp` / `npm run mcp` exposes default-safe agent tools for scout, policy, repro, diff-shape, lane status/resume, evidence drafts, fixed local lane storage, and registry-readiness self-audit. The release gate verifies `npm pack` includes the bin before publish. See [docs/MCP.md](docs/MCP.md).
- Contributor preflight: `pcf preflight` checks a draft PR or patch before submission, with a stable exit-code contract for hooks and CI.
Expand Down
6 changes: 3 additions & 3 deletions docs/LAUNCH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ The package is npx-ready: `bin` exposes `pcf`, `premature-contribution-firewall`
Publish from `.github/workflows/npm-publish.yml`; do not create or paste a reusable npm token. The workflow verifies the requested version is unpublished, runs every proof gate, checks package contents, and uses GitHub OIDC trusted publishing.

```bash
VERSION=0.1.3
VERSION=0.2.0
gh workflow run npm-publish.yml --ref main -f version="$VERSION" -f dry-run=true
# Inspect and require a successful dry-run workflow before continuing.
gh workflow run npm-publish.yml --ref main -f version="$VERSION" -f dry-run=false
Expand All @@ -34,7 +34,7 @@ Notes:
npx premature-contribution-firewall@latest --help
npx premature-contribution-firewall@latest evaluate fixtures/pr-ready.json
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
| npx -y -p premature-contribution-firewall@latest pcf-mcp
| npm exec --yes --package=premature-contribution-firewall@latest -- pcf-mcp
npm view premature-contribution-firewall version bin
```

Expand All @@ -52,7 +52,7 @@ OPERATOR steps for each new Action release:
3. On the release page, check "Publish this Action to the GitHub Marketplace".
4. Category: "Continuous integration" + "Code review". The `branding` block (filter icon, blue) is already in `action.yml`.

Current release: [`v0.1.3`](https://github.com/VrtxOmega/premature-contribution-firewall/releases/tag/v0.1.3), published from npm `gitHead` `b2bd5e4083045d69f4f5a2dab13527ae393bebfa`.
Current release: [`v0.2.0`](https://github.com/VrtxOmega/premature-contribution-firewall/releases/tag/v0.2.0), published from npm `gitHead` `8739108af4055c9ac72b033a7da4df770aa43272`.

## 3. PR Gate Rollout Guidance (what to tell adopters)

Expand Down