Fix npm package boundary verification

[mrnicholasbcarter-code]

Summary

• Align README install examples and npm badge with the published package name.
• Make package verification run clean tarball install, ESM import, TypeScript export checks using the repo TypeScript compiler while preserving consumer cwd.
• Add npm publish dry-run gate, release notes artifact, pre-publish package verification, and workflow_dispatch version guard.

Closes #9

Evidence

• CI logs inspected: README Prettier failure, then consumer tsc resolution issue.
• npm view @verdict/node version --json: 404 not published
• npm view @bodanglin/verdict-node version --json: 0.1.0
• npm ci
• npm run verify:package: Verified 24 shipped files, clean ESM imports, and TypeScript declarations
• npm run format:check
• npm run build
• npm run lint
• npm test: 3 suites, 156 tests passed
• npm pack --dry-run: 24 files, dist/ + README.md + LICENSE + CHANGELOG.md + package.json only
• git diff --check

🤖 Generated with Claude Code