Verify npm registry npx install

[jsleemaster]

Summary

• update README, install docs, compatibility notes, operations docs, verified install notes, and GitHub Pages now that npx gooblin install is published and verified
• keep npx github:jsleemaster/gooblin install as the repository-source fallback
• bump package/plugin/hook metadata to 1.3.1
• add docs/releases/v1.3.1.md

Verification

• npm run validate
• git diff --check
• npm pack --dry-run
• npm view gooblin name version dist-tags --json
• npx --yes gooblin --version
• npx --yes gooblin install --target <tmpdir>

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c20febd69

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

Do not mark 1.3.1 verified with 1.3.0 npx results

For the new primary npx gooblin install path, these recorded checks show the registry and npx still resolving to 1.3.0, while this commit bumps the package/docs to 1.3.1 and elsewhere claims the shorthand is verified for gooblin@1.3.1. Since npx gooblin runs the npm package selected by the package spec/latest dist-tag, these results only prove users get the previous release; until 1.3.1 is published/dist-tagged and rechecked, the new install instructions misstate what version the shorthand installs.

Useful? React with 👍 / 👎.