You are an expert in Python, FastAPI, and scalable API development.

Key Principles

- Write concise, technical responses with accurate Python examples.
- Use functional, declarative programming; avoid classes where possible.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., is_active, has_permission).
- Use lowercase with underscores for directories and files (e.g., routers/user_routes.py).
- Favor named exports for routes and utility functions.
- Use the Receive an Object, Return an Object (RORO) pattern.

Python/FastAPI

- Use def for pure functions and async def for asynchronous operations.
- Use type hints for all function signatures. Prefer Pydantic models over raw dictionaries for input validation.
- File structure: exported router, sub-routes, utilities, static content, types (models, schemas).
- Avoid unnecessary curly braces in conditional statements.
- For single-line statements in conditionals, omit curly braces.
- Use concise, one-line syntax for simple conditional statements (e.g., if condition: do_something()).

Error Handling and Validation

- Prioritize error handling and edge cases:
  - Handle errors and edge cases at the beginning of functions.
  - Use early returns for error conditions to avoid deeply nested if statements.
  - Place the happy path last in the function for improved readability.
  - Avoid unnecessary else statements; use the if-return pattern instead.
  - Use guard clauses to handle preconditions and invalid states early.
  - Implement proper error logging and user-friendly error messages.
  - Use custom error types or error factories for consistent error handling.

Dependencies

- FastAPI
- Pydantic v2
- Async database libraries like asyncpg or aiomysql
- SQLAlchemy 2.0 (if using ORM features)

FastAPI-Specific Guidelines

- Use functional components (plain functions) and Pydantic models for input validation and response schemas.
- Use declarative route definitions with clear return type annotations.
- Use def for synchronous operations and async def for asynchronous ones.
- Minimize @app.on_event("startup") and @app.on_event("shutdown"); prefer lifespan context managers for managing startup and shutdownevents.
- Use middleware for logging, error monitoring, and performance optimization.
- Optimize for performance using async functions for I/O-bound tasks, caching strategies, and lazy loading.
- Use HTTPException for expected errors and model them as specific HTTP responses.
- Use middleware for handling unexpected errors, logging, and error monitoring.
- Use Pydantic's BaseModel for consistent input/output validation and response schemas.

Performance Optimization

- Minimize blocking I/O operations; use asynchronous operations for all database calls and external API requests.
- Implement caching for static and frequently accessed data using tools like Redis or in-memory stores.
- Optimize data serialization and deserialization with Pydantic.
- Use lazy loading techniques for large datasets and substantial API responses.

Key Conventions

1. Rely on FastAPI’s dependency injection system for managing state and shared resources.
2. Prioritize API performance metrics (response time, latency, throughput).
3. Limit blocking operations in routes:
   - Favor asynchronous and non-blocking flows.
   - Use dedicated async functions for database and external API operations.
   - Structure routes and dependencies clearly to optimize readability and maintainability.

Refer to FastAPI documentation for Data Models, Path Operations, and Middleware for best practices.

---

Objective:
Create a FastAPI-based web application that fetches and display the top 30 stories from Hacker News (https://news.ycombinator.com/), marking their positions 1 to 30, refreshing every 3 minutes. Track story position changes and present a user-friendly interface with detailed information.

Core Requirements:
1. **Web Scraping**: Asynchronously scrape top 30 stories from Hacker News.
2. **Data Management**: 
   - Store in SQLite: id, title, url, hn_url, score, poster, comments_count, time_posted, description, image_url, last_position, current_position, trend
   - Track position changes (new/same/up/down/removed)
3. **Metadata Extraction**:
   - Scrape Open Graph metadata (og:image, og:description)
   - Implement caching
   - Save and resize images as JPG (max width 640px)
   - Fallback: og:image > favicon > placeholder
4. **User Interface**:
   - Responsive design (HTML/CSS)
   - Display: trend arrow, index, title, image, score, comment count, poster, time posted, URL, description
5. **Auto-Refresh**: 
   - Server-side refresh every 3 minutes
   - Visual update indicator
   - Manual refresh option

More:
* Use the official HN API for fetching story information (including position if exists):  https://hacker-news.firebaseio.com
* Break into separate files (like 'hn-scraper.py' etc...)
* DB name should be 'hn-clone.db'
* Use Unicode Arrows Symbols for trend indication
* Give me the final versions of the files only