# GEMINI.md - UtiVerse Project Context & Rules

## CRITICAL: DUAL API BRIDGE SYNCHRONIZATION RULE

Whenever changes are made to the KALASI'U API Bridge (`kalasiu_bridge.php`), **both** of the following locations MUST be updated simultaneously:

1. **Local Bridge**: `c:\laragon\www\booking\public\kalasiu_bridge.php`
2. **Production Bridge**: `c:\laragon\www\landing mts\admin-mtssapo\public\kalasiu_bridge.php`

### Deployment Memory & Protocol
- **Deployment**: User uses GitHub Actions for deployment across projects.
- **Node.js Production (cPanel)**: After code is pushed to GitHub, GitHub Actions builds and uploads via FTP. Remind the user to restart the Node.js application in cPanel **after** the GitHub Actions workflow run completes.
- **Composer / Vendor Exclusion**: The `vendor/` folder is excluded from automatic FTP deployment. Remind user to run `composer install --no-dev --optimize-autoloader` manually in cPanel when dependencies change.

## UtiPlay and Pick A Side work

For every UtiPlay, Duel Rasi, Pick A Side, game-session, live-command, or game-report task, read and follow `@.agents/rules/utiplay-backend-contract.md` before editing. Also read the Pick A Side PRD and latest checkpoint in `C:\laragon\www\UtiPlay` when that game is in scope.

Keep all unrelated changes out of the commit. Do not push, deploy, migrate production, or mutate production data unless the user explicitly requests that action.