docs(readme): publish the refreshed README to npm

[loveneeshdhir]

What this does

npmjs.com shows the README from the published package, so the README merged in #4 and #6 only
reaches npm with a new release. Those commits were all docs:, which correctly does not release,
so npm still shows the 0.4.0 README.

This PR adds one empty commit, docs(readme): publish the refreshed README to npm, to trigger a
patch release under the docs(readme) rule from #5.

How to merge

• Needs ci: fix releases, stop hardcoding the release author, and make samc621 code owner #5 on main too. ci: fix releases, stop hardcoding the release author, and make samc621 code owner #5 adds the docs(readme) release rule and fixes the release-notes
  step that would otherwise fail. The order does not matter: semantic-release checks every commit
  since v0.4.0 with the config on main at the time, so the release runs when the second of the
  two PRs merges.
• Use "Create a merge commit". The commit is empty, so squash or rebase merging may drop it
  and then nothing releases.

What 0.4.1 will contain

• The refreshed README on npmjs.com. The demo recording renders there, because npm rewrites
  relative image paths to raw.githubusercontent.com/agenttrailhq/guard/HEAD/….
• 2c602b7 ("Update the vendored rule-matching engine"), which has been on main since 0.4.0 but
  was never released.
• The release step bumps the version in package.json, src/core/version.ts and
  plugin.json, rebuilds the hook bundles, updates CHANGELOG.md, tags v0.4.1, and publishes
  to npm through trusted publishing.

🤖 Generated with Claude Code

[github-actions]

🎉 This PR is included in version 0.4.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀