fix: resolve context.js path + include it in npm package

[bhvbhushan]

Summary

Two bugs that made vibecop init --context completely broken in 0.4.1 and 0.4.2:

1. dist/context.js was never included in the npm package. The prepublishOnly script ran bun run build but not bun run build:context. The tarball shipped without it.

2. Path resolution fell back to user's CWD. When dist/context.js didn't exist in the package (because of bug feat: aiqt v0.1 — AI code quality linter with 7 detectors and 5 output formats #1), resolveContextScript() fell through to resolve("dist/context.js") which resolved against the user's project directory.

Result: hooks pointed to /Users/you/your-project/dist/context.js which doesn't exist.

Fix

1. Added build:context to prepublishOnly script
2. resolveContextScript() now tries ./context.js (sibling in dist/) first

Verified

$ npm pack && tar tzf vibecop-*.tgz | grep dist/
package/dist/cli.js
package/dist/context.js     ← now included

$ npm install ./vibecop-0.4.3.tgz && npx vibecop init --context
Hook path: node_modules/vibecop/dist/context.js  ← correct
File exists: YES

610 tests pass, type check clean, lint clean, both builds succeed.

🤖 Generated with Claude Code