Let me first understand the full codebase before building the My Page.

Now I have the full picture. I need to:

1. Update SiteHeader and MarketDetailHeader to use proper Link elements for navigation (including /mypage)
2. Create the /mypage route with the user profile page
3. Split the profile page into components: profile section, attribute management, and active bets

Let me build the My Page now.

Now update the MarketDetailHeader to also link to /mypage:

Now create the user data module:

Now create the profile section component:

Now create the attribute management component:

Now create the active bets component:

Now create the main My Page client component:

Now create the route page:

Now I need to make sure the SiteHeader (used on the homepage) no longer requires "use client" since it uses Link components. Let me check -- actually the SiteHeader no longer has useState since I removed it, so it doesn't need "use client". Let me verify:

Good -- SiteHeader is now a pure server component with just Link elements and no client-side state. Now let me also check the MarketDetailHeader still works since it uses useState:

The MarketDetailHeader still has useState for activeNav which is now unnecessary since it uses Link for navigation. Let me clean it up to be consistent:

The My Page is now complete. I created the /mypage route with four new components: ProfileSection displays the user name, truncated wallet address, balance (with a green flash animation on charge), and weight score in two stat cards. AttributeManagement renders the attribute list with type badges, weight multipliers, verified dates, and delete buttons, plus an inline add form with type dropdown, label input, and auto-calculated weight preview. ActiveBets shows the user's prediction cards with market title, outcome pick, stats row (amount/weight/effective), probability bar, and status badge. All state flows through the parent MyPage component which handles charge (+5000 JPYC), attribute CRUD with weight recalculation, and the flash animation.

Now I have a clear picture of the codebase. This is a complex page with many interactive sections, so I'll break it into focused components. Let me create the admin data module first, then the components, and finally the page route.

Now let me create the main admin dashboard component that ties everything together:

Now create the page route:

The admin dashboard is now live at /admin. It starts with a minimal login gate (any non-empty password works), then reveals a two-tab dashboard: the Markets Management tab shows all 6 markets in a table with status badges, close/resolve actions, and a collapsible create form with dynamic outcomes (2-8), live preview card, and validation; the Resolve/Payout tab lets you select a closed market, pick the correct outcome via radio cards, view a full payout simulation with per-bettor breakdown table and pool distribution bar, then double-click confirm (with a 3-second red "are you sure?" safety) which stamps the panel as resolved. State persists across tab switches, and the "Go to resolve" link on closed markets auto-navigates to tab 2 with the market pre-selected.