HackerNews MCP Server

## Description <!--- Describe your changes in detail --> ## Type of Change <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (non-breaking change which adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change) - [ ] 📚 Documentation update - [ ] 🎨 Style/Code quality improvement - [ ] 🔧 Refactoring (no functional changes) - [ ] 🧪 Tests (adding or updating tests) - [ ] 🔒 Security enhancement - [ ] 🚀 Performance improvement - [ ] 🛠️ Build/CI improvement ## Changes Made <!--- List the specific changes you made --> ### Code Changes - ### Tests Added/Updated - ### Documentation Updated - ## Testing <!--- Please describe the tests that you ran to verify your changes --> ### Test Results ```bash # Paste test output here ``` ### Manual Testing - [ ] Tested in VS Code with GitHub Copilot - [ ] Tested in Claude Desktop - [ ] Tested with MCP Inspector - [ ] Verified all existing functionality still works ## Quality Gates <!--- Ensure all quality gates pass --> - [ ] `npm run lint` passes - [ ] `npm run check` passes - [ ] `npm test` passes - [ ] `npm run test:coverage` passes (≥80% coverage) - [ ] `npm audit` passes - [ ] Constitution compliance checklist completed ## Screenshots (if applicable) <!--- Add screenshots to help explain your changes --> ## Additional Notes <!--- Anything else reviewers should know --> ## Checklist - [ ] My code follows the project's style guidelines - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules