SQUEEK – CRITICAL BACKEND FIX + MOBILE CONTROL UPDATE

PRIORITY 1: FIX SUPABASE COMPLETELY

Do not assume Supabase is connected just because the code contains integration logic.

1. Inspect the entire repository, environment configuration, previous implementation and available project history to locate the existing Supabase project.
2. Do not create a new Supabase project before checking whether the existing project can be recovered.
3. Identify and configure the actual Supabase Project URL and Publishable Key using the correct environment variables.
4. Never expose service_role keys, database passwords or private wallet keys in frontend code.
5. Execute migration 004_lifetime_persistence.sql against the correct production database.
6. Implement secure wallet-signature authentication and one persistent player profile per wallet.
7. Permanently synchronize SQK, inventory, game progress and Lifetime Score.
8. Restore player data when reconnecting the same wallet, including on another device.
9. Implement an accurate global Lifetime Top 100 leaderboard using Supabase data.
10. Guest players can continue playing without a wallet, with guest data stored locally.

IMPORTANT: If the existing Supabase project or credentials cannot be located, clearly identify exactly what is missing and request the required information. Do not fabricate credentials or report a successful connection without testing it.

PRIORITY 2: MOBILE GAME CONTROLS

Left side – Movement

• Remove the fixed circular joystick completely.
• Implement touch-anywhere movement on the left half of the game screen.
• Allow players to touch and drag freely to control movement.
• No requirement to keep the finger inside a fixed joystick circle.

Right side – Combat

• Increase Attack and Jump button sizes slightly.
• Increase the distance between Attack and Jump to prevent accidental presses.
• Keep both buttons comfortable for thumb operation.
• Preserve all existing combat functionality and weapon selection controls.

FINAL VERIFICATION

Before marking the task complete:

• Verify actual Supabase connection.
• Verify production database migrations.
• Test wallet authentication and player data restoration.
• Test score persistence after refresh and reconnecting.
• Verify global Top 100 using real database records.
• Test mobile controls on different screen sizes.
• Run build and type checks.

Provide a clear report separating completed tasks, failed tasks and tasks requiring user input.

Do not claim completion based only on successful builds or simulated data.

MANDATORY SUPABASE RECOVERY REQUIREMENT

Do not stop after inspecting the code or identifying missing configuration.

Your responsibility is to achieve a fully operational Supabase integration.

Follow this sequence:

1. Diagnose the current Supabase integration and identify every missing component.
2. Check whether you have access to the existing Supabase project and database.
3. If credentials or permissions are missing, explicitly request only the information or access required from the user.
4. Once access is available, configure the connection, execute pending migrations, configure database security (RLS), and implement the required persistence logic.
5. Run real database read/write tests.
6. Test that Lifetime Score survives page refresh, logout, wallet reconnection and device changes.
7. Verify that the leaderboard displays actual database records.

Do not mark Supabase as completed until all critical tests pass.

If blocked, report the exact blocker, its cause, and the specific action required from the user. Continue implementation as soon as the blocker is resolved.