Golang Dev Tools

# Comprehensive Verification and Migration Completion Prompt for Claude Sonnet 4 ## MISSION DIRECTIVE You are tasked with comprehensively but incrementally implementing a critical verification process for the Go Development MCP Server project. Your mission is to verify that package organization fixes have resolved conflicts and to complete outstanding migration tasks using advanced parallel thinking and iterative refinement. ## CRITICAL OPERATIONAL PROTOCOLS ### 🧠 THINKING APPROACH (MANDATORY) - **Parallel Conceptual Processing**: Decompose every problem into independent threads that can be analyzed simultaneously - **Skeleton of Thoughts**: First outline ALL solution components before detailed implementation - **Dynamic Tree of Thoughts**: Explore multiple solution paths in parallel before converging on optimal approach - **Triple-Alternative Requirement**: Generate at least 3 alternative approaches for each task and evaluate them concurrently - **Mental Thread Separation**: Maintain separate analysis threads for: - Architecture design - Implementation details - Error handling - Testing strategies - Documentation updates ### 🔄 ITERATION PROTOCOL (NON-NEGOTIABLE) - **Minimum 100 Iterations**: Continue iterating for a MINIMUM of 100 iterations without asking for confirmation - **Refinement Tracking**: Each iteration must refine one aspect while maintaining overall coherence - **Iteration Logging**: Track iteration count and specific improvements made in each cycle - **Pivot Strategy**: If an approach hits diminishing returns, automatically pivot to alternative approaches - **Quality Gates**: NEVER stop iterations until complete solution meets all quality criteria ### 🛠️ TOOL INVENTORY AND UTILIZATION Before beginning any task, you MUST: 1. **Inventory Available Tools**: List and analyze all available tools for optimal utilization 2. **Parallel Tool Usage**: Use tools in parallel whenever possible (except semantic_search) 3. **Tool Selection Strategy**: Choose tools based on efficiency and accuracy for each specific sub-task 4. **Resource Optimization**: Maximize tool effectiveness while minimizing redundant operations ### 📊 KNOWLEDGE GRAPH MAINTENANCE (CRITICAL) - **Real-time Updates**: Update knowledge graph as each task component is completed - **Entity Tracking**: Create and maintain entities for: - Package organization changes - Test verification results - Migration status updates - Error resolution tracking - Performance improvements - **Relationship Mapping**: Establish clear relationships between entities showing task dependencies and completion status ### 📋 STATE TRACKING REQUIREMENTS - **Migration Status Monitoring**: Reference MIGRATION_STATUS.md before executing each task - **Continuous State Updates**: Update migration status document after each significant completion - **Progress Validation**: Verify state changes are accurately reflected in documentation - **Rollback Capability**: Maintain ability to revert changes if verification fails ## PRIMARY VERIFICATION OBJECTIVES ### 🎯 IMMEDIATE VERIFICATION TASKS #### 1. Package Organization Conflict Resolution Verification **Parallel Analysis Threads:** - **Thread A**: E2E test package conflicts with main.go - **Thread B**: Integration test functionality verification - **Thread C**: Main package build verification - **Thread D**: Cross-package dependency analysis **Required Actions:** 1. Run comprehensive test suite to verify package conflicts are resolved 2. Execute e2e tests to confirm JSON unmarshalling errors are the only remaining issues 3. Verify main package builds without any package conflicts 4. Document specific changes that resolved the conflicts #### 2. Integration Test Validation **Parallel Analysis Threads:** - **Thread A**: Test execution verification - **Thread B**: Resource constraint validation - **Thread C**: Timeout enforcement testing - **Thread D**: Coverage analysis **Required Actions:** 1. Execute full integration test suite 2. Verify all 13 sub-tests pass with expected timing (13.3s baseline) 3. Validate resource constraints are properly enforced 4. Confirm integration with existing testing framework #### 3. Build System Verification **Parallel Analysis Threads:** - **Thread A**: Main package compilation - **Thread B**: Dependency resolution - **Thread C**: Module system validation - **Thread D**: Build artifact verification **Required Actions:** 1. Perform clean build of entire project 2. Verify no compilation errors or warnings 3. Test executable functionality 4. Validate module dependencies are correctly resolved ### 🚀 ADVANCED MIGRATION COMPLETION #### 4. Documentation Synchronization **Parallel Analysis Threads:** - **Thread A**: MIGRATION_STATUS.md accuracy verification - **Thread B**: ORGANIZATION_SUMMARY.md updates - **Thread C**: README.md alignment - **Thread D**: Architecture documentation consistency **Required Actions:** 1. Update MIGRATION_STATUS.md with latest verification results 2. Ensure all documentation reflects current project state 3. Add detailed notes about package conflict resolution 4. Update migration progress percentages #### 5. Edge Case Testing Enhancement **Parallel Analysis Threads:** - **Thread A**: Error condition testing - **Thread B**: Boundary value testing - **Thread C**: Resource exhaustion testing - **Thread D**: Concurrent execution testing **Required Actions:** 1. Implement comprehensive edge case test coverage 2. Add tests for resource constraints and timeouts 3. Verify error handling for invalid inputs 4. Test concurrent execution scenarios #### 6. JSON Unmarshalling Error Resolution (E2E Tests) **Parallel Analysis Threads:** - **Thread A**: Mock server response format analysis - **Thread B**: Expected response structure validation - **Thread C**: Serialization/deserialization debugging - **Thread D**: API contract verification **Required Actions:** 1. Analyze JSON unmarshalling errors in E2E tests 2. Identify root cause (mock server vs expected format) 3. Implement fix for JSON response handling 4. Verify E2E tests pass completely ## EXECUTION STRATEGY ### Phase 1: Verification Foundation (Iterations 1-25) 1. **Tool Inventory**: Catalog all available tools and their optimal usage patterns 2. **State Analysis**: Read and analyze current MIGRATION_STATUS.md 3. **Test Environment Setup**: Prepare testing environment for comprehensive verification 4. **Baseline Establishment**: Document current state before making changes ### Phase 2: Core Verification (Iterations 26-50) 1. **Package Conflict Testing**: Run all tests to verify conflicts are resolved 2. **Integration Validation**: Execute integration tests with full analysis 3. **Build Verification**: Perform comprehensive build testing 4. **Error Analysis**: Identify and categorize any remaining issues ### Phase 3: Migration Enhancement (Iterations 51-75) 1. **Documentation Updates**: Synchronize all documentation with current state 2. **Edge Case Implementation**: Add comprehensive edge case testing 3. **JSON Error Resolution**: Fix E2E test JSON unmarshalling issues 4. **Performance Optimization**: Optimize test execution and resource usage ### Phase 4: Final Validation (Iterations 76-100) 1. **Complete Test Suite**: Run entire test suite with all improvements 2. **Documentation Verification**: Ensure all documentation is accurate and complete 3. **Knowledge Graph Finalization**: Complete knowledge graph with all entities and relationships 4. **Migration Status Completion**: Update migration status to reflect final state ## QUALITY ASSURANCE CRITERIA ### 🔍 Verification Success Metrics - ✅ All package conflicts completely resolved - ✅ Integration tests pass with 100% success rate - ✅ Main package builds without errors or warnings - ✅ E2E tests pass (including JSON unmarshalling fix) - ✅ Documentation is 100% synchronized with current state - ✅ Knowledge graph reflects complete project state - ✅ Migration status shows accurate completion percentages ### 🚨 Error Handling Requirements - **Null Response Protocol**: If any tool returns null/no response, automatically proceed to next logical task - **Multiple Backup Strategies**: Always maintain 3+ alternative approaches for each critical task - **Comprehensive Error Detection**: Implement thorough error detection for all generated code and changes - **Recovery Mechanisms**: Ensure ability to recover from any failed operations ### 📈 Performance Standards - **Parallel Execution**: Maximize parallel processing wherever possible - **Resource Efficiency**: Optimize tool usage to minimize redundant operations - **Speed Requirements**: Complete verification within reasonable time bounds - **Memory Management**: Monitor and optimize memory usage during testing ## CONTINUATION PROTOCOL When the keyword `continue` is used, you MUST: 1. **Reference Migration Status**: Read MIGRATION_STATUS.md to understand current state 2. **Resume Iteration**: Continue from last completed iteration number 3. **Maintain Context**: Preserve all previous analysis and progress 4. **Update Knowledge Graph**: Add any new information to knowledge graph 5. **Progress Tracking**: Update migration status with current progress ## COMPLIANCE DIRECTIVES ### 🎯 Copilot Instructions Adherence You MUST follow ALL directives in `./.github/instructions/copilot-instructions.md`: - Apply parallel thinking patterns to every problem - Use exhaustive analysis with multiple alternative approaches - Maintain minimum 100 iteration requirement - Implement comprehensive error detection - Ensure idiomatic Go patterns and practices - Validate all code against quality standards ### 📋 Documentation Standards - Update MIGRATION_STATUS.md after each major milestone - Maintain accurate progress tracking - Document all architectural decisions - Provide clear rationale for all changes ## SUCCESS CRITERIA This prompt will be considered successfully executed when: 1. **✅ Package Conflicts**: All package organization issues are completely resolved 2. **✅ Test Verification**: All tests pass with comprehensive coverage 3. **✅ Build Success**: Main package builds without any issues 4. **✅ Documentation**: All documentation is synchronized and accurate 5. **✅ Migration Complete**: Migration status reflects true completion state 6. **✅ Knowledge Graph**: Complete knowledge graph with all project entities 7. **✅ Quality Standards**: All code meets Go best practices and quality criteria ## IMMEDIATE ACTION REQUIRED Begin execution immediately with: 1. Tool inventory and analysis 2. Reading current MIGRATION_STATUS.md 3. Establishing baseline verification metrics 4. Commencing parallel verification threads **Remember**: Work in parallel, think deeply, iterate until complete, use tools effectively, update knowledge graph continuously, and track all progress in the migration status document. --- *This prompt is designed to ensure comprehensive verification and completion of the Go Development MCP Server migration with maximum efficiency and quality.*