Build the catalogue: categories, search and product pages

You are a senior full-stack developer working inside my Next.js (App Router), TypeScript, Tailwind and Drizzle project for "Thread & Needle", a fashion e-commerce store selling women's and men's clothing, shoes and accessories to customers in United States. Prices are in USD. I am not a programmer, so explain technical words briefly.

Goal: build the public catalogue, reading real data from the local Postgres database shop_local using the tables and seed data from Episode 6. Do not build the cart, accounts or checkout yet.

Plan first: inspect the current database schema and seed data, then show me your plan (routes, tables you will add or change, filters, and how URLs will look) and wait for my OK before changing anything. If the schema is missing something the catalogue needs (categories, products, variants such as size or color, stock, image slots), propose the change as a drizzle-kit migration, never a manual edit.

Tasks, after I approve:
1. Create a branch named feature/catalogue.
2. Make sure the data model has: categories (with slug and parent), products (slug, name, description, price in whole minor units, status active or draft, created date), variants (option values, stock, optional price), and image records that hold a public id and alt text for later (Episode 9 fills them). Add database indexes for slug, category and status. Extend the seed so there are at least 12 products across 3 categories, including one out of stock item and one draft item that must never show.
3. Build routes: shop (all products), shop by category, product detail by slug, and search. Use readable URLs.
4. Listing pages: product grid using the Episode 7 components, sorting (newest, price low to high, price high to low), filters (category, price range, in stock, plus one or two filters that suit women's and men's clothing, shoes and accessories), and pagination. Keep filter state in the URL so pages can be shared and bookmarked.
5. Search: a search box in the header and a results page. Use parameterized queries only, escape special characters, and show a friendly empty state with suggestions.
6. Product page: gallery slots with a placeholder image, name, price, description, variant picker, stock message (in stock, low stock, sold out), and a disabled Add to cart button with a note that the cart arrives in Episode 10. Return a proper 404 for unknown or draft products.
7. SEO: generateMetadata for every page with a unique title, description, canonical URL based on threadandneedle.com and Open Graph tags; JSON-LD structured data for Product (name, description, image, offers with price, currency and availability) and BreadcrumbList; a heading structure with one h1.

Security rules:
- Validate every query parameter with Zod and ignore or reject bad values; never trust the URL.
- Only status active products are ever returned to the public.
- When writing JSON-LD into the page, escape the less-than character so product text cannot break out of the script tag.
- Do not log or print any database URL or secret.

Verify by running these yourself and showing the results: type check, lint, production build, and a script or test that loads the main pages and confirms that the draft product is absent, the sold-out product is labeled, a bad filter value does not crash the page, and the JSON-LD parses as valid JSON.

Commit in small steps with clear messages, push the branch and open a pull request.

Report back in this format:
1. What you did.
2. What I should check myself (URLs to open).
3. Anything that needs my decision.

Review the prompt, then copy it. Never paste real passwords or API keys into a chat.