DOC-3498: Update Docker image name to ai-service-tiny

Registry URL confirmed as registry.containers.tiny.cloud/ai-service-tiny
per Dominik Szczepaniak.

Author: kemister85

modules/ROOT/pages/tinymceai-on-premises-database.adoc

@@ -420,7 +420,7 @@ When the AI service runs in Docker but the database or Redis runs natively on th
 ----
 services:
   ai-service:
-    image: registry.containers.tiny.cloud/ai-service:latest
+    image: registry.containers.tiny.cloud/ai-service-tiny:latest
     extra_hosts:
       - "host.docker.internal:host-gateway"
     environment:

modules/ROOT/pages/tinymceai-on-premises-getting-started.adoc

@@ -16,7 +16,7 @@ mkdir tinymce-ai-onpremise && cd tinymce-ai-onpremise
 
 === Authenticate with the container registry
 
-The service image lives at `registry.containers.tiny.cloud/ai-service`.
+The service image lives at `registry.containers.tiny.cloud/ai-service-tiny`.
 
 For Docker:
 
@@ -39,7 +39,7 @@ Replace `TINY_REGISTRY_USERNAME` with the username supplied by the Tiny account
 
 [source,bash]
 ----
-docker pull registry.containers.tiny.cloud/ai-service:latest
+docker pull registry.containers.tiny.cloud/ai-service-tiny:latest
 ----
 
 For Podman, substitute `podman pull`. For production, pin a specific version tag (for example `:5.1.0`) rather than `:latest`.
@@ -184,7 +184,7 @@ docker run --init -d -p 8000:8000 \
   -e PROVIDERS="$PROVIDERS" \
   -e STORAGE_DRIVER='database' \
   -e ENABLE_METRIC_LOGS='true' \
-  registry.containers.tiny.cloud/ai-service:latest
+  registry.containers.tiny.cloud/ai-service-tiny:latest
 ----
 ====
 

modules/ROOT/pages/tinymceai-on-premises-production.adoc

@@ -98,7 +98,7 @@ The AI service works with Podman as an alternative to Docker. In Podman, contain
 ----
 podman login -u 'TINY_REGISTRY_USERNAME' registry.containers.tiny.cloud
 
-podman pull registry.containers.tiny.cloud/ai-service:latest
+podman pull registry.containers.tiny.cloud/ai-service-tiny:latest
 
 podman pod create --name ai-pod -p 8000:8000 -p 3306:3306 -p 6379:6379
 
@@ -120,7 +120,7 @@ podman run --init -d --pod ai-pod --name ai-service \
   -e REDIS_HOST='127.0.0.1' \
   -e PROVIDERS='{"openai":{"type":"openai","apiKeys":["sk-proj-..."]}}' \
   -e STORAGE_DRIVER='database' \
-  registry.containers.tiny.cloud/ai-service:latest
+  registry.containers.tiny.cloud/ai-service-tiny:latest
 ----
 
 IMPORTANT: Pin to `mysql:8.0`. The `mysql:8` tag floats to MySQL 8.4, which removes the `default-authentication-plugin` flag and causes a crash loop. See xref:tinymceai-on-premises-database.adoc[Database, Redis, and storage] for details.
@@ -192,7 +192,7 @@ spec:
         - name: tiny-registry
       containers:
         - name: ai-service
-          image: registry.containers.tiny.cloud/ai-service:latest
+          image: registry.containers.tiny.cloud/ai-service-tiny:latest
           ports:
             - containerPort: 8000
           env:
@@ -355,7 +355,7 @@ spec:
   "containerDefinitions": [
     {
       "name": "ai-service",
-      "image": "registry.containers.tiny.cloud/ai-service:latest",
+      "image": "registry.containers.tiny.cloud/ai-service-tiny:latest",
       "portMappings": [{ "containerPort": 8000 }],
       "healthCheck": {
         "command": ["CMD-SHELL", "curl -f http://localhost:8000/health || exit 1"],
@@ -412,7 +412,7 @@ spec:
 |Database encryption at rest |Turn on encryption at rest in the cloud provider console. RDS, Cloud SQL, and Azure Database enable this by default.
 |Redis authentication |Always set `REDIS_PASSWORD` (or use a managed Redis instance with authentication enabled).
 |Container security |Run as non-root, use a read-only filesystem where possible, and drop unnecessary Linux capabilities.
-|Image scanning |Scan `registry.containers.tiny.cloud/ai-service` with Trivy, Snyk, or the registry's built-in scanner.
+|Image scanning |Scan `registry.containers.tiny.cloud/ai-service-tiny` with Trivy, Snyk, or the registry's built-in scanner.
 |Least-privilege JSON Web Tokens (JWTs) |Grant only the permissions each user role requires. Avoid full-access tokens in production.
 |API secret rotation |Periodically create a new access key, add the new key to the configuration, then revoke the old key. The token endpoint reads the secret at request time.
 |Audit logging |Enable `ENABLE_METRIC_LOGS=true` and ship logs to a Security Information and Event Management (SIEM).
@@ -592,7 +592,7 @@ Redis holds ephemeral state. Losing Redis data does not affect persistent data.
 +
 [source,bash]
 ----
-docker pull registry.containers.tiny.cloud/ai-service:NEW_VERSION
+docker pull registry.containers.tiny.cloud/ai-service-tiny:NEW_VERSION
 ----
 . For rolling deploys across version boundaries: start *one* instance at the new version and wait for it to become healthy before rolling the rest.
 . For Kubernetes: update the image tag in the Deployment. The default `RollingUpdate` strategy handles zero-downtime upgrades, provided the first new pod becomes Ready before the rollout continues.

modules/ROOT/pages/tinymceai-on-premises-providers.adoc

@@ -153,7 +153,7 @@ docker run --init -d -p 8000:8000 \
   -e REDIS_HOST='redis' \
   -e STORAGE_DRIVER='database' \
   -e PROVIDERS='{"openai":{"type":"openai","apiKeys":["sk-proj-YOUR_KEY_HERE"]}}' \
-  registry.containers.tiny.cloud/ai-service:latest
+  registry.containers.tiny.cloud/ai-service-tiny:latest
 ----
 
 *Verify:*
@@ -699,7 +699,7 @@ On Linux, add the host gateway so `host.docker.internal` resolves:
 ----
 services:
   ai-service:
-    image: registry.containers.tiny.cloud/ai-service:latest
+    image: registry.containers.tiny.cloud/ai-service-tiny:latest
     extra_hosts:
       - "host.docker.internal:host-gateway"
 ----

modules/ROOT/pages/tinymceai-on-premises.adoc

@@ -5,7 +5,7 @@
 
 The TinyMCE AI on-premises service is a self-hosted back end that powers AI writing assistance. It can be used with the TinyMCE rich text editor, particularly the xref:tinymceai.adoc[TinyMCE AI plugin], or as a standalone service. It runs entirely within the host infrastructure. Document content, conversation history, file attachments, and user data never leave the network.
 
-The service ships as a single Open Container Initiative (OCI) container image (`registry.containers.tiny.cloud/ai-service`). It exposes a REST API, a Management Panel, Server-Sent Events streaming, and an OpenAPI spec.
+The service ships as a single Open Container Initiative (OCI) container image (`registry.containers.tiny.cloud/ai-service-tiny`). It exposes a REST API, a Management Panel, Server-Sent Events streaming, and an OpenAPI spec.
 
 == Architecture