kylon-cli 0.7.9-next.1243 → 0.7.9-next.1246

package/README.md

@@ -1234,6 +1234,17 @@ new production CLI build must be published. Service deployment alone leaves
   PR and that its service changes have deployed. CLI-only changes can follow
   the already-deployed ancestor. Both stable paths run full provider E2E and
   platform verification; prior PR CI evidence does not replace fresh proof.
+- **The merged PR's preview must still match `main`.** Stable preparation
+  restores the merged PR's exact preview by rerunning its last
+  `pull_request` run, and that rerun is accepted only when the run's merge
+  commit has the same tree as the current `main` head. The merge commit was
+  computed against `main` as it stood at the PR's last push, so anything that
+  lands on `main` between that push and the stable run (a hotfix, another
+  release) makes the trees differ and the rerun is refused with
+  `Closed previews can only be recreated by rerunning the exact production
+  candidate still on main`. Nothing about the closed PR can be repaired: open
+  a fresh CLI-only PR from the current `main`, merge it, and dispatch stable
+  on that commit, keeping `main` still until the CLI is published.
 
 Do not `npm publish` ad hoc: use the stable workflow and its OIDC provenance.
 Pushing a version tag alone does not publish.

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.7.9-next.1243",
-  "fingerprint": "8c8348607a5823a92ad12816f4ad1bccdcdd4b643cb05b1c1542ab72d9474940",
-  "source_commit": "0b7e45ed92c4228edc5ddf62bcdb1a05f07c5432"
+  "version": "0.7.9-next.1246",
+  "fingerprint": "e90891fc8b04e2f4f5fb236e2fcf3e2df08a94c1b1206307c06297d5987ec0c1",
+  "source_commit": "97566e0f9b1404a8b1849999aeeccb66a38f5f4a"
 }