docs: add consolidated dev URL reference and migrate /shop to /storefront

- Add Development URL Quick Reference section to url-routing overview
  with all login URLs, entry points, and full examples
- Replace /shop/ path segments with /storefront/ across 50 docs files
- Update file references: shop_pages.py → storefront_pages.py,
  templates/shop/ → templates/storefront/, api/v1/shop/ → api/v1/storefront/
- Preserve domain references (orion.shop) and /store/ staff dashboard paths
- Archive docs left unchanged (historical)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/features/store-landing-pages.md

@@ -4,7 +4,7 @@ Complete guide to creating custom landing pages for store storefronts.
 
 ## Overview
 
-Each store can have a custom landing page at their root URL with different design templates. This landing page serves as the store's homepage, separate from the e-commerce shop section.
+Each store can have a custom landing page at their root URL with different design templates. This landing page serves as the store's homepage, separate from the e-commerce storefront section.
 
 ### URL Structure
 
@@ -14,10 +14,10 @@ Root Landing Page:
 - Subdomain:       https://orion.platform.com/      → Landing Page
 - Path-based:      http://localhost:8000/stores/orion/ → Landing Page
 
-E-commerce Shop:
-- Custom Domain:   https://customdomain.com/shop/      → Shop Homepage
-- Subdomain:       https://orion.platform.com/shop/ → Shop Homepage
-- Path-based:      http://localhost:8000/stores/orion/shop/ → Shop Homepage
+E-commerce Storefront:
+- Custom Domain:   https://customdomain.com/storefront/      → Storefront Homepage
+- Subdomain:       https://orion.platform.com/storefront/ → Storefront Homepage
+- Path-based:      http://localhost:8000/storefront/orion/ → Storefront Homepage
 ```
 
 ## Features
@@ -25,7 +25,7 @@ E-commerce Shop:
 ✅ **Multiple Templates**: Choose from 4 different landing page designs
 ✅ **CMS-Powered**: Content managed through ContentPage model
 ✅ **Per-Store Customization**: Each store can have unique design
-✅ **Auto-Fallback**: Redirects to shop if no landing page exists
+✅ **Auto-Fallback**: Redirects to storefront if no landing page exists
 ✅ **Theme-Aware**: Uses store's theme colors and branding
 
 ## Available Templates
@@ -112,7 +112,7 @@ Set `is_published=True` to make the landing page live.
 If no landing page exists:
 1. System checks for `slug="landing"`
 2. If not found, checks for `slug="home"`
-3. If neither exists, **redirects to `/shop/`**
+3. If neither exists, **redirects to `/storefront/`**
 
 This ensures stores always have a working homepage even without a landing page.
 
@@ -169,7 +169,7 @@ ADD COLUMN template VARCHAR(50) NOT NULL DEFAULT 'default';
 
 ### Get Landing Page
 ```http
-GET /api/v1/shop/content-pages/landing
+GET /api/v1/storefront/content-pages/landing
 Referer: https://orion.platform.com/
 
 Response:
@@ -195,7 +195,7 @@ Response:
 ### Test Fallback
 1. Delete or unpublish landing page
 2. Access store root URL
-3. Should redirect to `/shop/`
+3. Should redirect to `/storefront/`
 
 ## Customization Guide
 
@@ -206,9 +206,9 @@ Response:
    app/templates/store/landing-{name}.html
    ```
 
-2. Extend shop base:
+2. Extend storefront base:
    ```jinja2
-   {% extends "shop/base.html" %}
+   {% extends "storefront/base.html" %}
    ```
 
 3. Use template variables as needed
@@ -238,7 +238,7 @@ Edit directly and changes apply immediately (no rebuild needed).
 
 2. **Keep Content Concise**: Landing pages should be scannable
 
-3. **Strong CTAs**: Always link to `/shop/` for e-commerce
+3. **Strong CTAs**: Always link to `/storefront/` for e-commerce
 
 4. **Use Theme Colors**: Templates automatically use store theme