ns-bridge

## Description <!-- Provide a brief description of the changes in this PR --> ### Related Issue <!-- Link to the Linear issue this PR addresses --> Closes: FORGE-XXX ### Type of Change <!-- Mark the relevant option with an 'x' --> - [ ] 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 not work as expected) - [ ] Documentation update - [ ] Code quality improvement (refactoring, formatting, type hints) - [ ] Performance improvement - [ ] Test coverage improvement ## Changes Made <!-- Describe the changes in detail. What was changed and why? --> - - - ## Testing <!-- Describe the tests you ran to verify your changes --> ### Test Coverage - [ ] All existing tests pass (`uv run pytest`) - [ ] New tests added for new functionality - [ ] Test coverage maintained or improved - [ ] Coverage report reviewed (`uv run pytest --cov`) ### Manual Testing <!-- Describe any manual testing performed --> - [ ] Tested with MCP Inspector (`uv run mcp dev src/ns_bridge/server.py`) - [ ] Tested with Claude Desktop - [ ] Verified with real NS API (if applicable) ### Example Usage <!-- If adding new functionality, provide example queries or usage --> ``` # Example: # "Find trains from Utrecht to Amsterdam" ``` ## Code Quality Checklist <!-- Ensure all quality checks pass before requesting review --> - [ ] Code follows project style guidelines - [ ] Code formatted with Black (`uv run black src/ tests/`) - [ ] Linting passes with Ruff (`uv run ruff check --fix src/ tests/`) - [ ] Type checking passes with MyPy (`uv run mypy src/`) - [ ] No security vulnerabilities introduced - [ ] Error handling is appropriate - [ ] Code is well-commented where necessary ## Documentation - [ ] README.md updated (if applicable) - [ ] QUICKSTART.md updated (if applicable) - [ ] Docstrings added/updated for new functions - [ ] Type hints added for all function signatures - [ ] CHANGELOG or PROJECT_STATUS updated (if applicable) ## Performance & Reliability <!-- Consider these aspects for production readiness --> - [ ] No performance regressions introduced - [ ] API calls are efficient (caching considered if applicable) - [ ] Rate limiting respected (if applicable) - [ ] Error messages are clear and helpful ## Breaking Changes <!-- If this PR introduces breaking changes, describe them and the migration path --> **None** / **Describe breaking changes here** ## Screenshots / Demo <!-- If applicable, add screenshots or demo GIFs showing the changes in action --> ## Additional Context <!-- Add any other context about the PR here --> --- ## Reviewer Notes <!-- For the reviewer: What should they pay special attention to? --> ### Areas of Focus - - ### Questions for Reviewer - -