chore: prepare repository migration and Docker Build Cloud publishing

docs/self-hosting/docker.mdx

@@ -3,6 +3,13 @@ title: "Self-hosting with Docker"
 description: "How to self-host Reactive Resume with Docker (Postgres only), with an environment variable reference and troubleshooting tips."
 ---
 
+<Warning>
+  **Repository migration planned.** The GitHub repository is moving to `reactive-resume/app`.
+  Docker Hub stays at `amruthpillai/reactive-resume`; GHCR is moving to `ghcr.io/reactive-resume/app`.
+  The GHCR examples below use the new address. Keep your current image configuration until the
+  [pinned migration announcement](https://github.com/amruthpillai/reactive-resume/issues/3503) confirms availability.
+</Warning>
+
 <Info>
   **From v5.1.0 onwards** — PDF generation now runs entirely client-side via `@react-pdf/renderer`. New deployments no longer require Browserless, Chromium, or any external print service as a dependency. The `PRINTER_*` and `BROWSERLESS_*` environment variables are no longer read and can be removed from your `.env`.
 </Info>
@@ -28,7 +35,18 @@ planned. Follow the [Docker Compose quickstart](#quickstart-using-docker-compose
 You can pull the latest app image from:
 
 - Docker Hub: `amruthpillai/reactive-resume:latest`
-- GitHub Container Registry: `ghcr.io/amruthpillai/reactive-resume:latest`
+- GitHub Container Registry: `ghcr.io/reactive-resume/app:latest`
+
+### Switching an existing GHCR installation
+
+After the new GHCR image is confirmed available, replace `ghcr.io/amruthpillai/reactive-resume` with
+`ghcr.io/reactive-resume/app` in your deployment configuration. Keep your current version tag only if that tag
+exists at the new address. Historical tags are not copied automatically, and the old GHCR address does not redirect.
+
+Docker Hub users need no image-name change. Changing registries does not require deleting containers' persistent
+volumes, resetting the database, or migrating resumes. Normal upgrade instructions still apply if you also change
+the application version. If you verify image signatures, update the accepted workflow identity for new releases
+to the workflow under `reactive-resume/app`; retain the old identity when verifying historical releases.
 
 ## Minimum requirements
 
@@ -191,7 +209,7 @@ services:
 
   reactive-resume:
     image: amruthpillai/reactive-resume:latest
-    # image: ghcr.io/amruthpillai/reactive-resume:latest
+    # image: ghcr.io/reactive-resume/app:latest
     restart: unless-stopped
     ports:
       - "3000:3000"
@@ -216,7 +234,7 @@ volumes:
     </CodeGroup>
 
     <Tip>
-      Prefer pulling from Docker Hub? Keep <code>amruthpillai/reactive-resume:latest</code>. Prefer GHCR? Swap it to <code>ghcr.io/amruthpillai/reactive-resume:latest</code>.
+      Prefer pulling from Docker Hub? Keep <code>amruthpillai/reactive-resume:latest</code>. Prefer GHCR? Swap it to <code>ghcr.io/reactive-resume/app:latest</code>.
     </Tip>
 
     <Note>
@@ -254,7 +272,7 @@ docker compose logs -f reactive-resume
 Use your platform's generic container configuration to create two separately managed containers: one for Reactive
 Resume and one for PostgreSQL. No official Unraid Community Applications template is provided.
 
-- Use the official `amruthpillai/reactive-resume:latest` or `ghcr.io/amruthpillai/reactive-resume:latest` image for the
+- Use the official `amruthpillai/reactive-resume:latest` or `ghcr.io/reactive-resume/app:latest` image for the
   app container.
 - Map the app's container port `3000` to the host port you want to use.
 - Connect both containers to a private container network. Set the host in `DATABASE_URL` to the PostgreSQL container or

docs/self-hosting/examples.mdx

@@ -15,7 +15,7 @@ They go further than the basic setup in the [Self-hosting with Docker](/self-hos
 
 <Info>
   **Share your setup.** If you have a working configuration that isn't covered here, I'd love to include it. [Open a
-  pull request](https://github.com/amruthpillai/reactive-resume) with your example added to this page.
+  pull request](https://github.com/reactive-resume/app) with your example added to this page.
 </Info>
 
 ---
@@ -352,7 +352,8 @@ services:
       replicas: 1
 
   reactive_resume:
-    image: ghcr.io/amruthpillai/reactive-resume:latest
+    # Wait for the migration announcement to confirm this GHCR address is available.
+    image: ghcr.io/reactive-resume/app:latest
     networks:
       - traefik_network
       - reactive_resume_network
@@ -457,7 +458,7 @@ Have a different deployment setup that works well? Consider contributing it here
 - Podman configurations
 - Cloud-specific deployments (AWS ECS, Google Cloud Run, Azure Container Apps)
 
-To contribute, [open a pull request](https://github.com/amruthpillai/reactive-resume) with your example added to this page. Include:
+To contribute, [open a pull request](https://github.com/reactive-resume/app) with your example added to this page. Include:
 
 1. A brief description of when/why someone would use this setup
 2. The complete Docker Compose (or equivalent) configuration

docs/self-hosting/migration.mdx

@@ -150,7 +150,7 @@ To run the migration scripts, you need the following installed on your host mach
   <Card title="Reactive Resume Source Code">
     Clone the Reactive Resume repository and check out the last tag that includes the migration scripts:
     ```bash
-    git clone https://github.com/amruthpillai/reactive-resume.git
+    git clone https://github.com/reactive-resume/app.git reactive-resume
     cd reactive-resume
     git checkout tags/v5.0.20
     pnpm install