fix(app): cache the actual live deployment after --no-promote

setKnownLiveDeployment cached the un-promoted candidate as the known-live deployment; with --no-promote that id is not live. Cache the actually-live id instead (the previous deployment that keeps serving), and skip the write when the app has no live deployment yet.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: kristof-siket

packages/cli/src/controllers/app.ts

@@ -823,11 +823,18 @@ async function runSingleAppDeploy(
     id: deployResult.app.id,
     name: deployResult.app.name,
   });
-  await context.stateStore.setKnownLiveDeployment(
-    projectId,
-    deployResult.app.id,
-    deployResult.deployment.id,
-  );
+  // With --no-promote the live deployment is unchanged, so cache the actually-live
+  // id (never the un-promoted candidate); skip when the app has nothing live yet.
+  const knownLiveDeploymentId = deployResult.promoted
+    ? deployResult.deployment.id
+    : deployResult.app.liveDeploymentId;
+  if (knownLiveDeploymentId) {
+    await context.stateStore.setKnownLiveDeployment(
+      projectId,
+      deployResult.app.id,
+      knownLiveDeploymentId,
+    );
+  }
 
   return {
     command: "app.deploy",

packages/cli/tests/app-controller.test.ts

@@ -7037,6 +7037,11 @@ describe("app controller", () => {
       "prisma-cli app promote dep_candidate",
       "prisma-cli app show-deploy dep_candidate",
     ]);
+    // The un-promoted candidate must not be cached as the known-live deployment;
+    // the previously-live one keeps serving.
+    expect(
+      await context.stateStore.readKnownLiveDeployment("proj_123", "app_1"),
+    ).toBe("dep_live");
   });
 
   it("deploy --no-promote on the production branch bypasses the production gate", async () => {