@synopackageland/cli 0.10.7 → 0.10.9

package/CHANGELOG.md

@@ -1,5 +1,82 @@
 # Changelog
 
+## 0.10.9 (2026-10-15)
+
+Builds with SDK 0.10.9 and templates 0.10.10: `init` writes SDK v0.10.9,
+`@synopackageland/sdk` 0.10.9 and `@synopackageland/ui` 0.9.8, and the root-ops
+template's `ExecutorGate.vue` passes `preload`. The executor digest table adds
+SDK 0.10.8 and 0.10.9 (equal to each other; the executor changed in 0.10.8).
+**An App moved from SDK 0.10.7 or earlier and rebuilt is approved once more
+by an administrator after the upgrade**, since its executor digest changes.
+The CLI still needs SDK 0.10.5 or later: an executor without `tasks` (before
+0.10.8) is read back by the window as before. Use SDK 0.10.9, not 0.10.8:
+0.10.8's `ExecutorApproval` kept its loading text beside the pages without an
+executor setup.
+
+To upgrade an App: devDependency `@synopackageland/cli` 0.10.9 (exact) with
+its lockfile; an App that depends on the SDK directly moves to 0.10.9 (Go
+`require github.com/synopackageland/syno-pkg-land-sdk v0.10.9` with go.sum,
+`@synopackageland/sdk` and `@synopackageland/app` 0.10.9, Cargo tag
+`v0.10.9`, `backend.sdk: 0.10.9`); then rebuild, upgrade, and approve once.
+
+繁中摘要：搭配 SDK 0.10.9、templates 0.10.10（UI 0.9.8）。digest 表新增 SDK 0.10.8／0.10.9
+（兩者相同，executor 在 0.10.8 改變）。自 SDK 0.10.7 以前升級並重建的 App，升級後要由管理員
+重新核准一次。SDK 下限維持 0.10.5（沒有 `tasks` 的舊 executor 照舊完整核對）。請用 SDK 0.10.9，
+不要用 0.10.8。App 要改：`@synopackageland/cli` 0.10.9＋lock；直接依賴 SDK 的 App 升到 0.10.9。
+
+- The DSM window shows an administrator the App without reading Task
+  Scheduler and EventScheduler when the pinned, running executor's status
+  says its own readback of the approval tasks is `ready` (`tasks`, SDK
+  0.10.8 or later). That readback runs at the executor's start and
+  every 10 minutes; a task another administrator changes after it is seen at
+  the next one, up to 15 minutes later, instead of when the window opens.
+  Approval, the control task's start, stop and purge, and a scope selection
+  still read both tasks back first. An executor without `tasks`, or with a
+  readback that is not `ready`, is read back by the window as before, and
+  the first status request now also serves its health check.
+  繁中：管理員開啟視窗時，若 executor 回報自己的排程核對為 ready，就不再呼叫兩個
+  排程 API；核准、start／stop／purge 與範圍選擇仍先完整核對。舊 executor 照舊核對。
+
+## 0.10.8 (2026-10-15)
+
+Builds with SDK 0.10.7 and templates 0.10.8, as 0.10.7 did: `init` still
+writes SDK v0.10.7, `@synopackageland/sdk` 0.10.7 and `@synopackageland/ui`
+0.9.8, and the executor digest table is unchanged, so an App rebuilt on it
+keeps its approval unless its executor or policy changes. Only the DSM
+window's `ctx.call` changes. The CLI still needs SDK 0.10.5 or later: the
+SDK's Gate, `useLifecycleRetry`, `appLifecycle` and `ExecutorApproval` already
+read an `APP_STOPPED` that arrives at once and check again; SDK 0.10.7 changed
+only its protocol README's wording, and nothing in the CLI depends on it.
+
+繁中摘要：搭配 SDK 0.10.7、templates 0.10.8（UI 0.9.8），digest 不變；SDK 下限維持 0.10.5
+（SDK 的 Gate／`useLifecycleRetry`／`appLifecycle`／`ExecutorApproval` 本來就處理立即回的
+`APP_STOPPED`）。只改 DSM window 的 `ctx.call`。
+
+- `ctx.call` rejects `APP_STOPPED` at once: a stopped package waits for the
+  user to start it in Package Center, so the SDK's stopped copy shows within a
+  page's next read instead of 30 s later (Download Hub 29.3 s, t-0527; Reclaim
+  showed its old content or loading, t-0528). `APP_STARTING` and
+  `EXECUTOR_STARTING` repeat for 4 s of waiting (0.5, 1, 2, 0.5 s), so a short
+  start still shows the page nothing and the SDK's starting copy follows a
+  longer one within its own 4 s recheck. `executor.control`, which the window's
+  approval starts the executor with, still repeats a start for 30 s; the SDK's
+  status reads are still not repeated.
+  繁中：套件停止時 `ctx.call` 立即回 `APP_STOPPED`；啟動中最多重試 4 s（`executor.control` 維持 30 s）。
+
+### Behavior changes
+
+- An App rebuilt with CLI 0.10.8 shows a stopped package's copy within its
+  page's next read: `ctx.call` rejects `APP_STOPPED` at once instead of after
+  about 30 s, and repeats `APP_STARTING` and `EXECUTOR_STARTING` for at most
+  about 4 s. The App's code needs no change; only its devDependency
+  `@synopackageland/cli` 0.10.8 and its lockfile, then a rebuild.
+- An e2e test that waits only for the Gate's stopped title
+  (`authorization.stopped.title`) can miss it: `ExecutorApproval` now takes
+  over first and shows its own stopped copy. Accept either of the SDK's stopped
+  copies.
+  繁中：App 升到 CLI 0.10.8 重新 build 後，套件停止時頁面立即收到 `APP_STOPPED`（不再等 30 s），
+  啟動中最多重試約 4 s；App 不需改程式。E2E 若只等 Gate 的停止標題，應接受 SDK 的任一停止文案。
+
 ## 0.10.7 (2026-10-15)
 
 Builds with SDK 0.10.7 and templates 0.10.8: `init` writes SDK v0.10.7 (Go

package/dist/runtime/executor-digests.json

@@ -86,5 +86,27 @@
             "armv7": "cafc97c89f5645c14a8cf31d6d9f258394ed6f2d086478a7aebd04d57c274b4e"
         },
         "goToolchain": "go1.26.9"
+    },
+    "0.10.8": {
+        "x86_64": "ba38f5764d5f0510706afe39979eef18bf2b8a72421a3a495810c628db0c962d",
+        "aarch64": "b5129b26714c25c0eda83931f3a66961fa9ecd059074c534159db6a68aefd8f7",
+        "armv7": "359005fbab7714c29d0d0598f09f3b011aa643be26d0368726a023edbef53b8e",
+        "lifecycle": {
+            "x86_64": "d65500c4f04713a32b45d360059281391acfa5e00ee24895fdd2de7b82735372",
+            "aarch64": "94f6cd119186ff482b8aea56541dd1f9d53c147566bc1efdca6f5a1c86198331",
+            "armv7": "cafc97c89f5645c14a8cf31d6d9f258394ed6f2d086478a7aebd04d57c274b4e"
+        },
+        "goToolchain": "go1.26.9"
+    },
+    "0.10.9": {
+        "x86_64": "ba38f5764d5f0510706afe39979eef18bf2b8a72421a3a495810c628db0c962d",
+        "aarch64": "b5129b26714c25c0eda83931f3a66961fa9ecd059074c534159db6a68aefd8f7",
+        "armv7": "359005fbab7714c29d0d0598f09f3b011aa643be26d0368726a023edbef53b8e",
+        "lifecycle": {
+            "x86_64": "d65500c4f04713a32b45d360059281391acfa5e00ee24895fdd2de7b82735372",
+            "aarch64": "94f6cd119186ff482b8aea56541dd1f9d53c147566bc1efdca6f5a1c86198331",
+            "armv7": "cafc97c89f5645c14a8cf31d6d9f258394ed6f2d086478a7aebd04d57c274b4e"
+        },
+        "goToolchain": "go1.26.9"
     }
 }

package/dist/standalone/dsm-window.js

@@ -192,17 +192,21 @@ ${ns}.callOnce = function (method, params, options, requestTimeout) {
 };
 
 // APP_STOPPED, APP_STARTING and EXECUTOR_STARTING mean the executor op was not
-// sent: the package is stopped, or starting. The call repeats on its own, half a
-// second, then doubling up to 8 s, for 30 s of waiting in all; each attempt keeps
-// its own deadline. Past that it rejects with the last refusal, and leaving the
+// sent. A stopped package waits for the user to start it in Package Center, so
+// APP_STOPPED rejects at once (t-0529). A start ends by itself: a call repeats
+// half a second, then doubling, for 4 s of waiting in all, so a short start
+// shows the page nothing and the SDK's starting copy follows a long one within
+// its own 4 s recheck; executor.control, which the window's approval starts the
+// executor with, repeats up to 8 s apart for 30 s. Each attempt keeps its own
+// deadline; past the wait it rejects with the last refusal, and leaving the
 // page during a wait rejects request_canceled at once. The SDK's status reads
 // are not repeated: its panels show the stopped or starting package and check
-// again on their own, and a page waiting here shows nothing (t-0503 R1).
-${ns}.retryCodes = ["APP_STOPPED", "APP_STARTING", "EXECUTOR_STARTING"];
+// again on their own (t-0503 R1).
+${ns}.retryCodes = ["APP_STARTING", "EXECUTOR_STARTING"];
 ${ns}.statusReads = ["delegate.status", "authorization.status", "executor.status"];
 ${ns}.call = function (method, params, options, requestTimeout) {
   var signal = options && options.signal;
-  var left = ${ns}.statusReads.indexOf(method) < 0 ? 30000 : 0;
+  var left = ${ns}.statusReads.indexOf(method) >= 0 ? 0 : method === "executor.control" ? 30000 : 4000;
   var delay = 500;
   var attempt = function () {
     return ${ns}.callOnce(method, params, options, requestTimeout).catch(function (error) {

package/dist/standalone/root-window.js

@@ -291,25 +291,29 @@ export const ROOT_RUNTIME = `function createRootAccess(options) {
     waited = waited || 0;
     delay = waited < 4000 ? 500 : Math.min(delay * 2, 2000);
     step = step === undefined ? stepBudget : step;
-    return options.call("executor.status", {}).then(function (status) {
+    return judged(options.call("executor.status", {})).catch(function (e) {
+      var steps = e.code === "executor_starting";
+      if ((steps ? step : budget) >= delay && options.wait) return options.wait(delay).then(function () { return steps ? alive(budget, delay, step - delay, waited + delay) : alive(budget - delay, delay, step, waited + delay); });
+      throw e;
+    });
+  }
+  // The approved executor's reply to one status request, or why it is not.
+  function judged(asked) {
+    return asked.then(function (status) {
       if (starting(status)) throw fail("executor_starting", "the executor's start step has not ended.");
       var why = mismatch(status);
       if (why) throw fail("executor_status_mismatch", why);
       return status;
     }, function (e) {
       throw fail(e && e.code, "the executor status request failed.");
-    }).catch(function (e) {
-      var steps = e.code === "executor_starting";
-      if ((steps ? step : budget) >= delay && options.wait) return options.wait(delay).then(function () { return steps ? alive(budget, delay, step - delay, waited + delay) : alive(budget - delay, delay, step, waited + delay); });
-      throw e;
     });
   }
   // step: how long to wait for a start step (ms). A status read waits none:
   // executor_starting says the package is starting, which the SDK checks
-  // again on its own.
-  function health(verified, step) {
+  // again on its own. asked: a status request already made, judged as is.
+  function health(verified, step, asked) {
     if (verified.state !== "ready") return Promise.resolve(verified);
-    return settle(verified, alive(0, undefined, step)).then(function (result) {
+    return settle(verified, asked ? judged(asked) : alive(0, undefined, step)).then(function (result) {
       if (result.code === "executor_starting") delete result.retry;
       return result;
     });
@@ -347,8 +351,23 @@ export const ROOT_RUNTIME = `function createRootAccess(options) {
       return e && lifecycleCodes.indexOf(e.code) >= 0 ? block({tasks: {}}, fail(e.code, "the executor status request failed.")) : needed;
     });
   }
+  // An administrator asks the executor first. The pinned, running executor
+  // reads both tasks back itself under the same rules (spec/scheduler/v1),
+  // at start and every 10 minutes, and its status says whether they were
+  // ready; the scheduler takes seconds per read. Anything else (an executor
+  // without tasks, a stale or failed readback, other digests) is read back
+  // here, and that first status serves the health check. Approval and
+  // control read back on their own.
+  function checked(status) { return pinned(status) && !!status.tasks && status.tasks.state === "ready"; }
+  function adminStatus() {
+    var asked = options.call("executor.status", {});
+    function verify() { return read().then(function (verified) { return health(verified, 0, asked); }); }
+    return asked.then(function (status) {
+      return checked(status) ? {state: "ready", tasks: {boot: {state: "ready"}, control: {state: "ready"}}, executor: status} : verify();
+    }, verify);
+  }
   return {
-    status: function () { return (isAdmin() ? read().then(function (verified) { return health(verified, 0); }) : userStatus()).then(publish); },
+    status: function () { return (isAdmin() ? adminStatus() : userStatus()).then(publish); },
     authorize: function (password, selectedScope) {
       if (!busy) busy = Promise.resolve().then(function () { return approve(password, selectedScope); }).catch(function (e) { var r = block({tasks: {}}, e); r.retry = !!(e && e.passwordConfirm); return r; }).then(function (r) { busy = null; return publish(r); });
       return busy;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synopackageland/cli",
-  "version": "0.10.7",
+  "version": "0.10.9",
   "description": "Syno Package Land Developer Kit CLI",
   "type": "module",
   "bin": {
@@ -25,7 +25,7 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@synopackageland/templates": "0.10.8",
+    "@synopackageland/templates": "0.10.10",
     "ajv": "^8.17.1",
     "commander": "^13.1.0",
     "tar": "^7.4.3",