Aurora Poker Club / Automation debug
Syncing live data…AS
System · live device registry

Automation debug

Up to three isolated Pokerrrr2 clients, explicit role mapping, current screen evidence and bounded actions. The fixture path remains available as the regression baseline.

Mock mode · live devices are not enabled

Use only disposable accounts and play money. Install Pokerrrr2 and complete every account login manually; this cockpit never types passwords, OTPs or CAPTCHA responses.

FIXTURE SAFE

Role-to-device mapping

Independent AVD storage · one role at a time for controlled actions
0 / 3 connected

Owner / manager · latest screenshot

Select a role to inspect
Screenshot unavailableConnect an assigned device and install Pokerrrr2 to capture live evidence.

Current detection waiting

Connectionnot observed
Pokerrrr2 packagenot installed
App processstopped
ScreenUnknownScreen
Login statusunknown
Failures0

Bounded owner actions role: OWNER

Each action captures before/after evidence and stops after two attempts if verification is not exact.

Manual login handoff required

1
Install Pokerrrr2Use Google Play on each isolated emulator.
YOU
2
Sign in manuallyUse disposable accounts; keep password, OTP and CAPTCHA input in your hands.
YOU
3
Check loginAutomation reads the visible screen and reports confirmed / unknown.
ADB

Fixture regression baseline

Kept intact while live mapping is calibrated
HomeScreen · 97%
fixtures/pokerrrr2/home-screen.svg

Deterministic detector output remains available for offline UI tests and safe replay. Live results are never substituted with this fixture.

club-title: Aurora Poker Club · sync-status: Connected
Notifications · Telegram

Updates & commands

One server-side bot can deliver role-aware updates and reply to scoped commands.
SETUP NEEDED
Bot tokenNot configured
Manager chats0
Role mappings0
Webhook secretOptional

Configured update types: buy-in decisions · limit changes · sync results · automation health.

Setup stays manual: create the bot in BotFather, put its token and chat IDs in server-only .env.local, then restart the app. Nothing here displays or stores the token in browser state.