chore: prepare v0.2.0 release

[VrtxOmega]

Summary

• bump premature-contribution-firewall from 0.1.3 to 0.2.0 for the new backward-compatible lifecycle command
• add the v0.2.0 changelog with the classifier, evidence boundary, and package-surface non-claims
• align both documented GitHub Action examples with the release version, as required by the repository consistency gate

Release boundary

0.2.0 is not represented as published in this PR. After merge, publication will run from main through the existing manual GitHub OIDC workflow with proof gates, unpublished-version verification, package inspection, and npm provenance. The existing local npm token is rejected and will not be reused or replaced.

Validation

• npm run ci:gates — 274/274 tests, 77/77 benchmark cases, 29/29 adversarial cases, and maintainer demo passed
• npm run mcp:smoke — passed, including the no-public-write-tool assertion
• npm pack --dry-run --json — premature-contribution-firewall@0.2.0, 80 entries, lifecycle engine and fixture included, all three bins preserved
• npm view premature-contribution-firewall@0.2.0 version — confirmed unpublished (E404)
• git diff --check — passed

Scope

Four release-only files are changed: package version, changelog, and the two documentation surfaces coupled to the package version. There are no source, dependency, lockfile, workflow, or generated-file changes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2fca392109

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep examples on a resolvable action ref

Until the manual post-merge release steps create v0.2.0, this ref does not exist: the commit explicitly records premature-contribution-firewall@0.2.0 as unpublished, and .github/workflows/npm-publish.yml publishes to npm but creates neither a Git tag nor a GitHub release. Consequently, maintainers copying either updated Action example after this lands get a GitHub Actions resolution failure rather than the queue workflow. Keep the examples on v0.1.3 until the tag is created, or make tag creation atomic with the release.

Useful? React with 👍 / 👎.