docs: describe what the base compose file actually does

It does not always build from source: with no `image:` key it builds
once, then reuses that local image until --build. What is load-bearing
is that it never reaches a registry, which is what makes the overlay the
only path to the published image.

Also drops the note about the frozen `rickstaa/` images. Those were
never production, and it was the only thing in the repo pointing readers
at a personal namespace.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: rickstaa

README.md

@@ -138,9 +138,6 @@ docker compose -f compose.yml -f compose.image.yml up -d
 
 The base `compose.yml` always builds from source, so the registry is reached only when you ask for it by adding the overlay. It stacks with the on-chain one (`-f compose.yml -f compose.onchain.yml -f compose.image.yml`).
 
-> [!NOTE]
-> The images previously published under `rickstaa/` on Docker Hub are frozen; use the GHCR ones.
-
 ### On-chain (paid) setup
 
 On-chain runs add a **remote signer** that holds the payer wallet and mints [probabilistic micropayment](https://medium.com/livepeer-blog/a-primer-on-livepeers-probabilistic-micropayments-e16788b29331) tickets; the orchestrator redeems the winning ones. Shared across examples:

echo/compose.image.yml

@@ -1,9 +1,10 @@
 # Run the published image instead of building. Layer it on the offchain base:
 #   docker compose -f compose.yml -f compose.image.yml up -d
 #
-# The base file always builds from source, so this overlay is the only way to
-# reach the registry; `pull_policy: always` keeps a stale local copy from
-# shadowing the published one. Stacks with the on-chain overlay too:
+# The base file names no image, so it never reaches a registry: it builds, then
+# reuses that local build until you pass --build. This overlay is the only path
+# to the published image, and `pull_policy: always` is what stops a stale local
+# copy of the moving `latest` tag from shadowing it. Stacks with on-chain too:
 #   docker compose -f compose.yml -f compose.onchain.yml -f compose.image.yml up -d
 
 services:

hello-world/compose.image.yml

@@ -1,9 +1,10 @@
 # Run the published image instead of building. Layer it on the offchain base:
 #   docker compose -f compose.yml -f compose.image.yml up -d
 #
-# The base file always builds from source, so this overlay is the only way to
-# reach the registry; `pull_policy: always` keeps a stale local copy from
-# shadowing the published one. Stacks with the on-chain overlay too:
+# The base file names no image, so it never reaches a registry: it builds, then
+# reuses that local build until you pass --build. This overlay is the only path
+# to the published image, and `pull_policy: always` is what stops a stale local
+# copy of the moving `latest` tag from shadowing it. Stacks with on-chain too:
 #   docker compose -f compose.yml -f compose.onchain.yml -f compose.image.yml up -d
 
 services:

realtime-transcription/compose.image.yml

@@ -1,9 +1,10 @@
 # Run the published image instead of building. Layer it on the offchain base:
 #   docker compose -f compose.yml -f compose.image.yml up -d
 #
-# The base file always builds from source, so this overlay is the only way to
-# reach the registry; `pull_policy: always` keeps a stale local copy from
-# shadowing the published one. Stacks with the on-chain overlay too:
+# The base file names no image, so it never reaches a registry: it builds, then
+# reuses that local build until you pass --build. This overlay is the only path
+# to the published image, and `pull_policy: always` is what stops a stale local
+# copy of the moving `latest` tag from shadowing it. Stacks with on-chain too:
 #   docker compose -f compose.yml -f compose.onchain.yml -f compose.image.yml up -d
 
 services:

tiles/compose.image.yml

@@ -1,9 +1,10 @@
 # Run the published image instead of building. Layer it on the offchain base:
 #   docker compose -f compose.yml -f compose.image.yml up -d
 #
-# The base file always builds from source, so this overlay is the only way to
-# reach the registry; `pull_policy: always` keeps a stale local copy from
-# shadowing the published one. Stacks with the on-chain overlay too:
+# The base file names no image, so it never reaches a registry: it builds, then
+# reuses that local build until you pass --build. This overlay is the only path
+# to the published image, and `pull_policy: always` is what stops a stale local
+# copy of the moving `latest` tag from shadowing it. Stacks with on-chain too:
 #   docker compose -f compose.yml -f compose.onchain.yml -f compose.image.yml up -d
 
 services: