Rename runtime images to explicit plex-playlist names

docs/CICD_SUCCESS_SUMMARY.md

@@ -72,12 +72,12 @@
 ### **Current Release Lifecycle (2026-07)**
 
 - Runtime deployable images are published first to staging repositories:
-  - `deployable-backend-staging`
-  - `deployable-frontend-staging`
+  - `plex-playlist-backend-staging`
+  - `plex-playlist-frontend-staging`
 - Runtime validation (`Runtime Black-Box Integration Tests` and `End-to-End Tests`) must pass before release tagging.
 - `Promote Release Images` retags validated staging artifacts to release repositories, but only on automated `push` runs to `main`:
-  - `deployable-backend`
-  - `deployable-frontend`
+  - `plex-playlist-backend`
+  - `plex-playlist-frontend`
 - Published release tags:
   - `latest`
   - `v<major>.<minor>.0`

docs/DEPLOYABLE_RUNTIME_CONTRACT.md

@@ -14,10 +14,10 @@ automation work under epic #66.
 Lifecycle note:
 
 - CI first builds deployable runtime artifacts in staging repositories
-  (`deployable-backend-staging`, `deployable-frontend-staging`).
+  (`plex-playlist-backend-staging`, `plex-playlist-frontend-staging`).
 - After integration and E2E validation pass, CI promotes those immutable
-  artifacts to release repositories (`deployable-backend`,
-  `deployable-frontend`) via tag promotion.
+  artifacts to release repositories (`plex-playlist-backend`,
+  `plex-playlist-frontend`) via tag promotion.
 
 Included:
 

docs/DEVELOPMENT.md

@@ -411,11 +411,11 @@ The pipeline is intentionally staged so expensive image jobs run only after sour
 2. Source + audit lanes:
    `Source Checks` and `Dependency Audits (Informational)` run after producer completion. Audit failures are intentionally non-blocking so both frontend and backend audits always report.
 3. Runtime image lanes:
-   `Build Release Images` publishes `deployable-backend-staging` and `deployable-frontend-staging`; `Build Tester Images` publishes integration/e2e tester images; then `Production Images Complete` gates downstream runtime tests.
+   `Build Release Images` publishes `plex-playlist-backend-staging` and `plex-playlist-frontend-staging`; `Build Tester Images` publishes integration/e2e tester images; then `Production Images Complete` gates downstream runtime tests.
 4. Runtime validation lanes:
    `Runtime Black-Box Integration Tests` and `End-to-End Tests` validate staged runtime artifacts.
 5. Promotion lane:
-   `Promote Release Images` runs only for automated `push` events on `main`. It retags validated staging artifacts to release repos (`deployable-backend`, `deployable-frontend`) with `latest`, `v<major>.<minor>.0`, `v<major>.<minor>.<patch>`, and `v<major>.<minor>.<patch>-<7-char-short-sha>` tags. If the `main` commit is untagged, CI creates the next patch tag automatically; if no prior semver tag exists, the bootstrap baseline is `v0.0.0`.
+   `Promote Release Images` runs only for automated `push` events on `main`. It retags validated staging artifacts to release repos (`plex-playlist-backend`, `plex-playlist-frontend`) with `latest`, `v<major>.<minor>.0`, `v<major>.<minor>.<patch>`, and `v<major>.<minor>.<patch>-<7-char-short-sha>` tags. If the `main` commit is untagged, CI creates the next patch tag automatically; if no prior semver tag exists, the bootstrap baseline is `v0.0.0`.
 6. Postmortem lanes:
    targeted postmortem jobs run when key lanes fail to capture diagnostics even when primary jobs fail early.