chore: release v1.3.2 and require version bumps per issue

CLAUDE.md

@@ -48,3 +48,32 @@ Commits and PRs carry no AI attribution — no `Co-Authored-By: Claude` trailer,
 `🤖 Generated with [Claude Code]` footer, no "AI-generated" notes in code comments or
 PR bodies. The human running the session is the sole author; write commit messages in
 their voice, describing the change rather than what produced it.
+
+## Resolving an issue
+
+Issues are tracked in
+[openscan-explorer/explorer](https://github.com/openscan-explorer/explorer/issues):
+`issue-402-trim-build-info` resolves explorer#402. Every resolved issue ends with
+the two steps below, without waiting to be asked. No hook enforces them.
+
+**Bump the plugin version** whenever the branch changes anything under
+[packages/plugin/](packages/plugin/). Set `version` in
+[packages/plugin/package.json](packages/plugin/package.json) one step past upstream
+`main`: minor for `feat`, major for a breaking change, patch for anything else.
+Commit it last and on its own, with the bare version as the subject (`v1.3.2`,
+exempt from the format check). One bump per branch; if `main` reaches that version
+first, rebase and bump again. Merging to `main` publishes to npm, and `pnpm publish`
+skips an already-published version without failing, so an unbumped merge ships
+nothing while CI stays green.
+
+**Open a pull request** for the issue:
+
+```bash
+pnpm build && pnpm test && pnpm lint
+git push -u origin <branch>
+gh pr create --repo openscan-explorer/hardhat-plugin --base main --head MatiasOS:<branch>
+```
+
+Title it like a commit subject. Open the body with
+`Fixes openscan-explorer/explorer#<n>`, or `Part of` when work on the issue remains
+outside this repo. Leave the merge to a maintainer, since merging publishes.

CONTRIBUTING.md

@@ -76,6 +76,11 @@ pnpm build && pnpm test && pnpm lint
 pnpm test:hooks   # only if you changed .githooks/
 ```
 
+A change under [packages/plugin/](packages/plugin/) also bumps `version` in its
+`package.json` (minor for `feat`, major for a breaking change, patch
+otherwise) in a final commit whose subject is the bare version (`v1.3.2`).
+Merging to `main` publishes to npm, and an unchanged version publishes nothing.
+
 Push your branch to your fork and open the PR against
 `openscan-explorer/hardhat-plugin`, base `main`:
 

packages/plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openscan/hardhat-plugin",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "Hardhat 3 plugin to use openscan explorer",
   "license": "MIT",
   "type": "module",