ChaosFight: Rebalance bank layouts to cut cross-bank calls

## Summary\nInvestigate bank/module placement to minimize cross-bank calls, especially cases where functions in the same bank are still invoked via cross-bank pathways (effective far call to same bank). Current layout may be forcing unnecessary bank switches and blowing CPU time.\n\n## Requirements\n- Audit existing bank map to catalog cross-bank call sites and their call frequency\n- Identify hotspots where same-bank routines are invoked as if they were in other banks\n- Propose alternative bank layouts or module shuffles that cluster frequently interacting code together\n- Evaluate trade-offs against art/data placement and size constraints\n- Provide implementation plan for restructuring without regressions\n\n## Acceptance Criteria\n- Documented analysis of current cross-bank call graph with counts\n- Recommended re-layout strategy with estimated savings\n- Risk assessment covering bank overflow, asset coupling, and build impacts\n- Implementation steps scheduled for a future milestone\n\n## Notes\n- Exploratory/planning issue for later; leave open until scheduled.