Build a Korean-Language Financial Terminal for U.S. and Korean Markets

Build a complete, runnable financial terminal for investors in U.S. stocks, with a Korean-language interface and support for Korean stocks and DART filings. Use the attached image as a visual reference for the terminal UI.

## Markets and data
- Support U.S. stocks, ETFs, indices, interest rates, commodities, foreign exchange, and Korean stocks.
- Include U.S. news, SEC filings, earnings, options, ETFs, and Korean DART filings.
- Provide real-time or near-real-time data where available. Document which APIs and API keys are needed.
- Never present fabricated numbers as real data. Clearly label data as unavailable, API-required, delayed, or otherwise limited.
- Allow logged-out visitors to view general market information using real data.

## News and AI
- Show U.S. news in its original language alongside a Korean translation.
- Provide a summary, sentiment, related tickers, and an importance rating for news.
- Make Google Gemini API or another AI API an optional integration for news features.
- Provide an AI assistant that can summarize and analyze securities, news, filings, charts, and portfolios in Korean. Allow Google Gemini API to be selected. If no AI API key is configured, provide a working local, rule-based summary fallback.

## Charts
- Include candlestick charts, volume, moving averages, Bollinger Bands, RSI, and MACD.
- Support the date ranges 1M, 3M, 6M, 1Y, 2Y, 5Y, and 10Y, and the intervals 1D, 1W, and 1M.
- Changing the date range or interval must load and display the corresponding chart data.
- Provide an enlarged view for portfolio charts.

## Portfolio
- After login, let users view their own portfolio.
- Provide an integration structure for broker APIs, including Alpaca, Interactive Brokers, and Korea Investment & Securities Open API.
- Show holdings, market value, profit and loss, allocation, sector allocation, country allocation, currency allocation, estimated dividends, and whether rebalancing may be needed.
- Let users manually enter and edit portfolio holdings.

## Login and personalization
- Logged-out users can browse general market data and news.
- Logged-in users can save and access their portfolio, watchlists, API keys, AI settings, layout, alerts, and default securities.
- Persist settings separately for each user.
- Document safe handling of sensitive API keys and relevant security precautions.

## UI and interaction
- Follow the attached reference image's dense financial-terminal style.
- Place global navigation, a command input, an AI button, and an index strip across the top.
- Use example global menu items Markets, Portfolio, Research, Tools, and AI. Include internal tabs such as Market, Monitor, Charts, News, Portfolio, Options, Orders, and AI.
- Make each tab switch to its corresponding screen.
- Let users drag and drop panels and resize individual panels and the left, center, and right columns.
- Save layouts per user. Prevent content from being clipped by using suitable panel scrolling and responsive layout behavior.

## Orders and trading safety
- Keep real-money order execution safely separated from other features.
- Default to paper trading. Enable real broker orders only through an explicit setting.
- Clearly distinguish live trading from paper trading throughout the UI so they cannot be confused.

## Deployment and documentation
- Support local execution and production deployment. Provide Docker and docker-compose files and an example environment-variable file.
- Document production deployment, HTTPS, authentication, sessions, and API-key security.
- Include a README covering setup, deployment, required API keys, data providers and their limitations, Google Gemini API configuration, broker API integrations, authentication and security design, layout customization, and the policy for distinguishing mock data from real data.

## Performance and delivery requirements
- Keep initial loading fast: show quick market data first and load news, filings, AI, and portfolio data in the background.
- Clearly distinguish real data, delayed data, API limits, and unavailable data. Never make missing data look like real figures.
- Before delivering the complete project as a ZIP, run it, test it directly, and fix any errors.
- Deliver the complete runnable project ZIP, local setup instructions, production deployment instructions, API-key setup documentation, data-source and limitation documentation, and the personalized portfolio and settings features. The terminal UI must support a dense layout with draggable and resizable panels.