[WIP] Instruction: 1. Carefully review the entire repository to understand module structure and dependencies. 2. Create a main.py file that serves as the unified entry point for the application. 3. Implement a shared config.py containing a Config cl...

[Copilot]

• Analyze repository structure and understand current codebase
• Identify hardcoded values and architectural issues
• Create main.py as unified entry point
• Implement config.py with Config class supporting JSON serialization
• Eliminate hardcoded values throughout codebase
• Add GUI with scrollable output field for runtime logs
• Implement session.log file logging with regeneration
• Refactor try_element_candidates function for efficient combined criteria
• Audit script for logical errors and broken function flows
• Create .test directory with comprehensive test cases
• Add README documentation for architectural decisions
• Validate GUI element bindings and add runtime assertions
• Implement clean install verification with requirements.txt
• Add development dependencies for linting/testing

Current State Analysis:

• Repository has two main Python files: copilot_ui_stress_test.py (639 lines) and copilot_ui_debug.py (386 lines)
• Some hardcoded configuration values exist in global variables
• No unified entry point or config management system
• No GUI currently - only console output
• try_element_candidates function uses sequential checking instead of combined criteria
• No dedicated test directory
• Good CI/CD pipeline already exists for Windows testing

Next Steps:

1. Create config.py with serializable Config class
2. Create main.py as entry point
3. Refactor hardcoded values to use config
4. Add GUI with logging output
5. Implement session.log logging
6. Optimize try_element_candidates function

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.