feat: publish the scoped npm prerelease @daichunghy/patchgate@0.1.0-beta.5

[daichunghy]

Summary

The maintainer authorized npm publication on 2026-09-06. Because the unscoped
patchgate npm name belongs to a different project, the package is published
as the scoped prerelease:

• package.json: name @daichunghy/patchgate, version 0.1.0-beta.5 (matching
  the current public Action pre-release), private: false.
• EVALUATOR_VERSION moves to 0.1.0-beta.5 so receipts and the CLI
  --version identify the exact evaluator prerelease (schema does not pin the
  version; determinism tests are self-consistent).
• check:release-candidate and check:release-guide now enforce the authorized
  scoped beta state instead of the private dev state.
• Status wording updated in README, getting-started, PROJECT_CONSTITUTION,
  AGENTS.md, the receipt contract, and the 2026-09-06 campaign record.
• The unscoped-name warnings (npx patchgate is a different project) are kept.

Verification

• npm run verify passes locally on this tree (lint, typecheck, fixtures,
  security, GitHub integration, build, bundle, consumer fixture, release
  checks, CLI smoke, dist verification).

After merge the package will be published to the beta dist-tag. Prerelease
publication is not a v0.1 claim and not adoption evidence.

Maintainer decision merge; not independent-review evidence.