Lumino

## Summary Brief description of the changes in this PR. ## Related Issue Fixes #(issue number) ## Type of Change - [ ] Bug fix (non-breaking change that fixes an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] New MCP tool (adds a new tool to the server) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [ ] Refactoring (no functional changes) ## Changes Made - - - ## New MCP Tool Checklist (if applicable) If this PR adds a new MCP tool, ensure you followed the [Spec-Driven Development](docs/LUMINO_MCP_TOOL_DEVELOPMENT_GUIDE.md) process: - [ ] Stage 1: Functional Specification created and reviewed - [ ] Stage 2: Implementation Specification created and reviewed - [ ] Stage 3: Code follows the implementation spec - [ ] Tool is read-only (no cluster modifications) - [ ] Tool has comprehensive docstring with Args and Returns - [ ] Tool handles exceptions gracefully - [ ] Tool added to README.md tool list ## Testing Describe how you tested your changes: - [ ] Tested locally with MCP client - [ ] Tested with Kubernetes cluster - [ ] Added/updated unit tests - [ ] All existing tests pass ## Checklist - [ ] My code follows the project's code style - [ ] I have performed a self-review of my code - [ ] I have commented my code where necessary - [ ] I have updated the documentation accordingly - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged ## Screenshots (if applicable) Add screenshots to help explain your changes. ## Additional Notes Any additional information that reviewers should know.