app-platform: remove unsupported saleor release surface

docs/APP-PACKAGING-MIGRATION-PLAN.md

@@ -50,7 +50,7 @@ The remaining migration work is mostly orchestration quality: post-reboot adopti
 Use a StartOS-inspired package model with Umbrel-like app folders.
 
 ```text
-apps/saleor/
+apps/example-commerce/
   manifest.yml
   Dockerfile
   icon.svg
@@ -109,12 +109,12 @@ Example `manifest.yml`:
 
 ```yaml
 app:
-  id: saleor
-  name: Saleor
+  id: example-commerce
+  name: Example Commerce
   version: 3.23.0
   description: Composable commerce platform
   container:
-    image: docker.io/myorg/saleor:3.23.0
+    image: docker.io/myorg/example-commerce:1.0.0
     pull_policy: if-not-present
     network: archy-net
     entrypoint: ["sh", "-lc"]
@@ -125,7 +125,7 @@ app:
         template: https://{{HOST_MDNS}}:9010
     secret_env:
       - key: SALEOR_SECRET_KEY
-        secret_file: saleor-secret-key
+        secret_file: example-commerce-secret-key
   dependencies:
     - storage: 20Gi
   resources:
@@ -142,7 +142,7 @@ app:
       protocol: tcp
   volumes:
     - type: bind
-      source: /var/lib/archipelago/saleor
+      source: /var/lib/archipelago/example-commerce
       target: /data
       options: [rw]
   environment:
@@ -293,7 +293,6 @@ Then moderate apps:
 
 Then complex apps:
 
-- Saleor
 - Mempool
 - BTCPay Server
 - NetBird only if safe
@@ -307,9 +306,11 @@ Leave for later:
 - System update
 - Mesh/Web5/FIPS core services
 
-## Saleor Reference Goal
+## Complex Stack Reference Goal
 
-Saleor should become the showcase package. It should prove:
+Saleor has been removed from the supported release catalog until it has a real
+manifest-owned package. A future complex stack should become the showcase
+package and prove:
 
 - Multi-container stack support.
 - Generated secrets.
@@ -322,7 +323,7 @@ Saleor should become the showcase package. It should prove:
 - Public domain support.
 - Alpha-node adoption.
 
-Once Saleor is clean, the app system is credible.
+Once a complex stack is clean, the app system is credible.
 
 ## Implementation Phases
 
@@ -364,7 +365,7 @@ Once Saleor is clean, the app system is credible.
 - Add adoption logic for existing containers.
 - Add migration metadata.
 - Migrate simple apps.
-- Migrate Saleor.
+- Migrate a serious multi-container app once the stack model is stable.
 - Keep rollback.
 - Prove reboot recovery with repeated clean post-reboot lifecycle passes.
 - Preserve Nostr signer bridges, Bitcoin dependency wait states, and public launch ports during adoption.
@@ -382,10 +383,10 @@ Once Saleor is clean, the app system is credible.
 Add commands like:
 
 ```bash
-archy app validate apps/saleor
-archy app render apps/saleor
-archy app install apps/saleor
-archy app test apps/saleor
+archy app validate apps/example-commerce
+archy app render apps/example-commerce
+archy app install apps/example-commerce
+archy app test apps/example-commerce
 ```
 
 Developers should be able to package an app without understanding Archipelago internals.
@@ -405,7 +406,7 @@ Public explanation:
 - Routing/public proxy integration: 1-2 weeks.
 - Hooks/secrets/backups: 2-3 weeks.
 - First migrations: 2-4 weeks.
-- Saleor reference migration: 1-2 weeks.
+- Complex stack reference migration: 1-2 weeks.
 - Cleanup/docs/tooling: 2-3 weeks.
 
 Total estimate: 8-14 weeks of serious work for an excellent system.
@@ -438,5 +439,5 @@ Minimum viable version: 3-5 weeks.
 3. Finish post-reboot adoption and stale scanner-state handling for migrated apps.
 4. Convert remaining multi-container legacy stacks to a manifest-owned model without deleting data.
 5. Add developer tooling around the current `manifest.yml` contract: validate, render, local install, lifecycle test.
-6. Migrate Saleor or another serious multi-container app as the proof package once the stack model is stable.
+6. Migrate a serious multi-container app as the proof package once the stack model is stable.
 7. Leave Bitcoin/LND/core services as managed infrastructure until the package system is proven for normal apps.