fix: report active package version in MCP startup

[Addono]

Summary

• resolve the MCP version from the running gh-attach package instead of falling back to 0.0.0-development
• reuse the same package-version lookup across the CLI and MCP code paths
• add regression coverage for source layout, built layout, HTTP health, and the built CLI MCP startup log

Expected behavior

npx -y gh-attach@latest mcp should report the version of the gh-attach package currently in use. With the current package metadata, that is 1.7.0.

Testing

• npm run lint
• npm run format:check
• npm run typecheck
• npm run build
• npm test
• packaged npx smoke test against npm pack output

[Addono]

Proof from the packaged npx smoke test (using the current npm pack tarball):

npx -y --package ./gh-attach-1.7.0.tgz gh-attach --version
1.7.0

npx -y --package ./gh-attach-1.7.0.tgz gh-attach mcp
[gh-attach MCP] Server started (stdio mode, version 1.7.0)

[github-actions]

🎉 This PR is included in version 1.7.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀