Start AdminDash and create the first organization

You are starting the TabTin administration console and creating the first usable Organization and administrator for my product. Follow the current backend contract; do not bypass normal initialization by editing business tables directly.

Before you begin

Read AGENTS.md, docs/agent/setup.md, apps/admindash, and apps/tabtin_django. Confirm the current Django API, database, and AdminDash startup commands and ports. Inspect existing accounts, organizations, and data to avoid duplicates. Never expose phone numbers, email addresses, tokens, or passwords in logs or the final report.

Work to complete

1. Start or verify the Django backend, then start the AdminDash development client.
2. Identify the current authentication flow and administrator eligibility rules. Use an approved initialization path to create or promote the requested account.
3. Create the first Organization through the product API or admin interface and establish an explicit owner.
4. Confirm that the default Workspace, memberships, and required built-in resources are created according to the current product model.
5. Do not create a permanent authorization bypass or write test credentials into the repository.

Verification

Sign in to AdminDash as the administrator and verify access to the Organization, members, and basic runtime status. Then verify the permission boundary with an ordinary member. Enter the Organization through Electron or the product entry point and confirm that Organization selection, Workspace access, and base resources work. If initialization uses background jobs, wait for completion and inspect their logs.

Final report

Give the console address, objects initialized, secure initialization method, administrator and member verification results, and production authentication or audit work still required. Omit all real credentials and do not commit changes unless I ask.