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/development/error-rendering/html-error-rendering-flow-diagram.md

@@ -91,7 +91,7 @@
                                     │              │              │
                                     ▼              ▼              ▼
                           ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
-                          │    Admin    │ │   Store    │ │    Shop     │
+                          │    Admin    │ │   Store    │ │ Storefront  │
                           │    Error    │ │    Error    │ │    Error    │
                           │    Page     │ │    Page     │ │    Page     │
                           │             │ │             │ │  (Themed)   │
@@ -159,8 +159,8 @@ For a 404 error in ADMIN context:
 For a 429 error in SHOP context (not created yet):
 
 ```
-1. Check: app/templates/shop/errors/429.html        ✗ Missing
-2. Check: app/templates/shop/errors/generic.html    ✗ Missing
+1. Check: app/templates/storefront/errors/429.html        ✗ Missing
+2. Check: app/templates/storefront/errors/generic.html    ✗ Missing
 3. Check: app/templates/shared/429-fallback.html    ✗ Missing
 4. Check: app/templates/shared/generic-fallback.html ✓ EXISTS → USE THIS
 ```
@@ -189,7 +189,7 @@ For a 429 error in SHOP context (not created yet):
     │  error_code│ │            │    │  Location:   │
     │  message   │ │ Context-   │    │  /admin/login│
     │  status    │ │  aware     │    │  /store/login│
-    │  details   │ │  template  │    │  /shop/login │
+    │  details   │ │  template  │    │  /storefront/login │
     │ }          │ │            │    │              │
     └────────────┘ └────────────┘    └──────────────┘
 ```
@@ -213,12 +213,12 @@ Context: ADMIN
 Result:  HTML admin/errors/404.html
 ```
 
-### Scenario 3: Shop Page 500 Error
+### Scenario 3: Storefront Page 500 Error
 ```
 Request: GET /products/123 (on store1.platform.com)
          Accept: text/html
 Context: SHOP (store detected)
-Result:  HTML shop/errors/500.html (with store theme)
+Result:  HTML storefront/errors/500.html (with store theme)
 ```
 
 ### Scenario 4: Unauthorized Access to Admin
@@ -245,7 +245,7 @@ Result:  302 Redirect to /admin/login
     ┌──────────────┐      ┌──────────────┐
     │  Admin User  │      │  Other Users │
     │  (Context:   │      │  (Store,    │
-    │   ADMIN)     │      │   Shop)      │
+    │   ADMIN)     │      │   Storefront)│
     └──────┬───────┘      └──────┬───────┘
            │                     │
            ▼                     ▼
@@ -280,8 +280,8 @@ app/
 │   ├── store/
 │   │   └── errors/             # TODO: Store error pages
 │   │
-│   ├── shop/
-│   │   └── errors/             # TODO: Shop error pages (themed)
+│   ├── storefront/
+│   │   └── errors/             # TODO: Storefront error pages (themed)
 │   │
 │   └── shared/
 │       └── *-fallback.html     # Shared fallback error pages
@@ -303,13 +303,13 @@ middleware/
 ✅ **Professional**: Polished error pages matching area design
 ✅ **Flexible**: Fallback mechanism ensures errors always render
 ✅ **Secure**: Debug info only shown to admins
-✅ **Themed**: Shop errors can use store branding (Phase 3)
+✅ **Themed**: Storefront errors can use store branding (Phase 3)
 
 ---
 
 This flow ensures that:
 1. API calls ALWAYS get JSON responses
 2. HTML page requests get appropriate error pages
-3. Each context (admin/store/shop) has its own error design
+3. Each context (admin/store/storefront) has its own error design
 4. Fallback mechanism prevents broken error pages
 5. 401 errors redirect to appropriate login pages