@objectstack/metadata 10.3.0 → 11.1.0

package/dist/node.cjs

@@ -3201,6 +3201,8 @@ var import_spec2 = require("@objectstack/spec");
 var queryableMetadataObjects = [
   import_metadata_core2.SysMetadataObject,
   import_metadata_core2.SysMetadataHistoryObject,
+  // ADR-0067 commit log — sibling of sys_metadata_history (see note above).
+  import_metadata_core2.SysMetadataCommitObject,
   import_metadata_core2.SysMetadataAuditObject,
   // Runtime view storage (shared / personal). Must always be provisioned so
   // end-user view creation via the generic data API has a place to write —
@@ -3353,7 +3355,7 @@ var MetadataPlugin = class {
             const src3 = this.options.artifactSource;
             if (src3?.mode === "local-file") {
               try {
-                await this._loadFromLocalFile(ctx, src3.path, src3.fetchTimeoutMs);
+                await this._reloadAndAnnounce(ctx, src3, body?.changed ?? [src3.path]);
                 ctx.logger.info("[MetadataPlugin] artifact reloaded via HMR POST", {
                   path: src3.path,
                   reason: body?.reason
@@ -3388,7 +3390,7 @@ var MetadataPlugin = class {
                 if (pending) return;
                 pending = true;
                 try {
-                  await this._loadFromLocalFile(ctx, src2.path, src2.fetchTimeoutMs);
+                  await this._reloadAndAnnounce(ctx, src2, [src2.path]);
                   hub.broadcastReload("artifact-file-changed", [src2.path]);
                   ctx.logger.info("[MetadataPlugin] artifact auto-reloaded (file watcher)", {
                     path: src2.path
@@ -3559,6 +3561,27 @@ var MetadataPlugin = class {
     ctx.logger.info("[MetadataPlugin] Artifact metadata loaded", { source: label, totalRegistered });
     return totalRegistered;
   }
+  /**
+   * Reload the artifact from disk into the MetadataManager, then announce a
+   * generic `metadata:reloaded` hook. Used by BOTH reload paths (the HMR POST
+   * handler and the server-side artifact-file watcher) — but NOT the initial
+   * boot load, which other plugins already consume directly.
+   *
+   * Runtime consumers that cached boot-time metadata re-sync on this signal.
+   * The automation engine subscribes to re-bind flow triggers it pulled ONCE
+   * at boot — notably scheduled jobs: without this, an edited
+   * schedule-triggered flow keeps firing its pre-edit definition (old runAs /
+   * schedule / logic) until a full process restart. A subscriber failure is
+   * logged but never blocks the reload.
+   */
+  async _reloadAndAnnounce(ctx, src, changed) {
+    await this._loadFromLocalFile(ctx, src.path, src.fetchTimeoutMs);
+    try {
+      await ctx.trigger("metadata:reloaded", { changed });
+    } catch (e) {
+      ctx.logger.warn("[MetadataPlugin] metadata:reloaded subscriber failed", { error: e?.message });
+    }
+  }
   async _loadFromLocalFile(ctx, filePath, fetchTimeoutMs) {
     const isUrl = /^https?:\/\//i.test(filePath);
     ctx.logger.info(