chore: prepare v0.14.0-beta.1 npm release

[SetraTheXX]

Summary

• prepare package and Codex plugin version 0.14.0-beta.1
• update npm-facing README, install guide, validation status, and release notes
• allow patch prerelease identifiers and require explicit public scoped publishing metadata

Validation

• npm run check
• npm run pack:dry-run
• npm publish --dry-run --access public --tag beta
• git diff --check
• private-path tracking check

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 51a1dbacea

ℹ️ 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]

Pin prerelease publication to the beta dist-tag

When a maintainer publishes this prepared prerelease without repeating --tag beta, this metadata supplies only the access setting. The npm publish documentation specifies tag with “Default: latest” and says that it is the tag added by npm publish; npm 11.4.2 additionally rejects a prerelease when no non-default tag is configured. Depending on the npm version, a plain publish can therefore fail or move latest, while every new installation example requires @beta. Add "tag": "beta" to publishConfig so the package itself enforces the intended release channel.

Useful? React with 👍 / 👎.