# Copilot Instructions

## Project Guidelines
- The codebase uses a MEP (Method Event Property) model with standard Hub functions where forms often act as singleton-like object models; interpreter is single-threaded and enforces singleton behavior. Persistent form-level variables should be treated as stateful, unlike Hub local temporaries.
- Use a single underscore prefix ('_') instead of 'popped' for stack-derived scratch variable names to improve visual readability. In stack pop/push modules, avoid the 'Stack' prefix in scratch names; prefer concise underscore-prefixed object-noun names based on context.
- Always verify Lancer.vbproj compile includes before editing; treat non-included VB files and Girex/legacy unretired artifacts as out of scope and do not process them.
- Only modify files that are included in Lancer.vbproj; treat non-included VB files as retired artifacts and avoid refactoring them.
- When editing VB functions that return by assigning the function name (e.g., `DoBase = False`), keep those assignments inside the function body and do not move them out during refactoring.