@zhuoyuezs/ml-platform 0.1.17 → 0.1.19

package/checksums.json

@@ -2,17 +2,17 @@
   "files": [
     {
       "path": "runtime/business-client/README.md",
-      "sha256": "sha256:168e376d3eec34da4cb7966aac44b5c87239ca432d9921588f499713c6aeb24b",
-      "size_bytes": 6122
+      "sha256": "sha256:61708adaee4479fe138ac5e6df1adc02be09cfeb6c30a7f9211ccc372c0e8ced",
+      "size_bytes": 7553
     },
     {
       "path": "runtime/business-client/package-lock.json",
-      "sha256": "sha256:b234d20b44cbfd166efef2a9ec6d91e00488952c9a6c7ccb1fdfa50374c4b986",
+      "sha256": "sha256:386e8b46ae8e6d7fd83e247b0412560710bee263c2545b593c5442b8f1363765",
       "size_bytes": 381
     },
     {
       "path": "runtime/business-client/package.json",
-      "sha256": "sha256:95551c271e726f4d69bf81b9f234b11781dc3b9a2e4b9f86db90ba8ca827ce42",
+      "sha256": "sha256:83e60780d91abc78420a533ba0f8ea184f31886f963ca6f1554da819530a6335",
       "size_bytes": 501
     },
     {
@@ -22,8 +22,8 @@
     },
     {
       "path": "runtime/business-client/src/cli.js",
-      "sha256": "sha256:3739b93b0bf42bf8c0521005cfe73b080e14ec88e0fe46feb0f375575a98b7ec",
-      "size_bytes": 53174
+      "sha256": "sha256:255c1ddf9521f7d6b336122a4678b1e9aab34e1ff4e894395a9e69316bacb4ad",
+      "size_bytes": 54119
     },
     {
       "path": "runtime/business-client/src/config.js",
@@ -37,8 +37,8 @@
     },
     {
       "path": "skills/feature-management/SKILL.md",
-      "sha256": "sha256:e5b927611cd401bc5e6160a2d358369efd0c4f65d3fe5cbf21bbab9adb6bd978",
-      "size_bytes": 31991
+      "sha256": "sha256:88898ea83ff339512d5512537db485a2764420abb67afceb9dd090cc780c00e0",
+      "size_bytes": 33021
     },
     {
       "path": "skills/feature-management/agents/openai.yaml",
@@ -92,13 +92,13 @@
     },
     {
       "path": "skills/feature-management/references/commands.md",
-      "sha256": "sha256:c748f1877f6d2ac1f6ecc29e45cd270997cbd35b498a190decddb66c74b840ab",
-      "size_bytes": 13751
+      "sha256": "sha256:ffd106cd785fe0d07ee20f51b7f55ca520da2fc6367bc5bc1ec0218600146d6e",
+      "size_bytes": 13905
     },
     {
       "path": "skills/feature-management/references/contracts.md",
-      "sha256": "sha256:4e10ba13399de17561a10b1dead4e2fcc57e0962cf81eba5131d12d66c4ce013",
-      "size_bytes": 29965
+      "sha256": "sha256:ef582d4ee9ade16de2a5f97b8bf9546969b6f2859eb020986bf25952993df402",
+      "size_bytes": 30483
     },
     {
       "path": "skills/feature-management/references/operator-authoring.md",
@@ -117,8 +117,8 @@
     },
     {
       "path": "skills/model-deployment-management/SKILL.md",
-      "sha256": "sha256:5dfeab163f2c11bd4554da23e898d388a7883a2501e6a9655ee45fcada7659bb",
-      "size_bytes": 2608
+      "sha256": "sha256:d50f64fa709c8ff36da97c60ce0d20b1217d1d9f78f602048f49c0c4bbab7ea2",
+      "size_bytes": 3927
     },
     {
       "path": "skills/model-deployment-management/agents/openai.yaml",
@@ -127,23 +127,23 @@
     },
     {
       "path": "skills/model-deployment-management/references/contracts.md",
-      "sha256": "sha256:3b040a97dcbf3b22b194bef2bb8c1af744d434ee88a6f47deed9ee4b83cf3147",
-      "size_bytes": 1926
+      "sha256": "sha256:de9fd3de8d88179b09108ee0778fb83fbffa304353706a3bbc14ae3d9276ac01",
+      "size_bytes": 5417
     },
     {
       "path": "skills/model-deployment-management/references/operations.md",
-      "sha256": "sha256:410111f01b972832bd48290d280f5364cacf2e63e7d586d3b670fad9b997f695",
-      "size_bytes": 2333
+      "sha256": "sha256:93977ec65a8b1ac51a5134ab98ac095e177de537c81f0db447ad97fb8a7e910f",
+      "size_bytes": 4455
     },
     {
       "path": "skills/model-deployment-management/references/troubleshooting.md",
-      "sha256": "sha256:2354dfad1493c361f534a7d02dbd8ccafa4662a6ebc8e6d1b0bf8dce447dd527",
-      "size_bytes": 1410
+      "sha256": "sha256:08762d603b938375cd3a76539c1d0320337d48f5bcd5ba061b8f16eaf35f9268",
+      "size_bytes": 3555
     },
     {
       "path": "skills/model-lifecycle-management/SKILL.md",
-      "sha256": "sha256:74ca6bad54ddb1dc30d3307335d045a70d2d383279011657cc49c1e549eda5a6",
-      "size_bytes": 3801
+      "sha256": "sha256:61a89145ef33a2d58c58d8f352006590a47cf9587705568dec1c8ffe7ed8938e",
+      "size_bytes": 4014
     },
     {
       "path": "skills/model-lifecycle-management/agents/openai.yaml",
@@ -162,18 +162,18 @@
     },
     {
       "path": "skills/model-lifecycle-management/references/packaging.md",
-      "sha256": "sha256:f46a5f9c326049a0c2411fdb9d392bea2f4d667062289ee0322a5d9d328c8363",
-      "size_bytes": 4888
+      "sha256": "sha256:1e3c5080fa085255b29223890c333333ee6011326b56f1b2e0b859b0d73d2ec0",
+      "size_bytes": 6146
     },
     {
       "path": "skills/model-lifecycle-management/references/training-contracts.md",
-      "sha256": "sha256:b6d72f37adf40c7d3832dbe46645cd416485411dcd48ea7b93f6072d458922c9",
-      "size_bytes": 11825
+      "sha256": "sha256:28fe32b2673db8f6cb1e02053bf5709826786e48dbe9951eac7bb4d98368d0c4",
+      "size_bytes": 12644
     },
     {
       "path": "skills/model-lifecycle-management/references/training.md",
-      "sha256": "sha256:f7bb40919da78b99cad13d4f1f05fef136552409df5ba6e2838e1e6b4a2435a5",
-      "size_bytes": 5508
+      "sha256": "sha256:97c20f02b1179dc7b7527cb7b5e11978778ccb8b76cdf88c229bcfdb5786f045",
+      "size_bytes": 5629
     }
   ],
   "schema_version": "data_platform.ml_platform_checksums/v1"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zhuoyuezs/ml-platform",
-  "version": "0.1.17",
+  "version": "0.1.19",
   "description": "ML 数据平台 business CLI 与 Agent Skills 管理工具",
   "bin": {
     "ml-platform": "scripts/main.js"

package/release.json

@@ -13,8 +13,8 @@
     "entrypoint": "src/cli.js",
     "name": "ml-platform",
     "path": "runtime/business-client",
-    "sha256": "sha256:864a3c32efc728bda13b4e2364174e63b9054368be9062ce4f67fe1aac034720",
-    "version": "0.7.7"
+    "sha256": "sha256:94d80ebfe36808fa5c0ed5585a002d8c77cb95c16b5f1ec856e5725d0d4b347f",
+    "version": "0.7.8"
   },
   "policy_sha256": "sha256:02fbde0134696b78c0c365d6e0b76c9814227208da5b2b3d4e5dbd82dc4a3606",
   "public_schema_versions": [
@@ -25,7 +25,7 @@
     "ml_data_platform.feature_set/v1",
     "ml_data_platform.dataset_manifest/v1"
   ],
-  "release_version": "0.1.17",
+  "release_version": "0.1.19",
   "runtime_requirements": {
     "node": ">=18",
     "os": [
@@ -37,22 +37,22 @@
   "skills": {
     "feature-management": {
       "path": "skills/feature-management",
-      "requires_cli": ">=0.7.7 <0.8.0",
-      "revision": "0.1.17",
-      "sha256": "sha256:182b6f2df4fe58c946e482dfaf416c7d5b78c6fde9c8c8d7293103246618cb4e"
+      "requires_cli": ">=0.7.8 <0.8.0",
+      "revision": "0.1.19",
+      "sha256": "sha256:d32f0306f129d7bf76eb037fe239c84dd3c29c64b61600799d6e40320784bb10"
     },
     "model-deployment-management": {
       "path": "skills/model-deployment-management",
-      "requires_cli": ">=0.7.7 <0.8.0",
-      "revision": "0.1.17",
-      "sha256": "sha256:8a4c71ec8bde6c8b37c038f327797286ffa5a3ec10501278bd3d0abbab1b7509"
+      "requires_cli": ">=0.7.8 <0.8.0",
+      "revision": "0.1.19",
+      "sha256": "sha256:d81becca0076d0513e7b8277e7584d9f810db755aa56e79235df68d0f7a7659b"
     },
     "model-lifecycle-management": {
       "path": "skills/model-lifecycle-management",
-      "requires_cli": ">=0.7.7 <0.8.0",
-      "revision": "0.1.17",
-      "sha256": "sha256:a00a50de7b7a5244a08d9865db10c812a1c6291c94ca01a8562f1b2d1ff72f2b"
+      "requires_cli": ">=0.7.8 <0.8.0",
+      "revision": "0.1.19",
+      "sha256": "sha256:5a911eff6a4c188d8e3709f37e4f37819effea61db9f5a015e6ec4dddd4a0ec7"
     }
   },
-  "source_commit": "2f547af208a94ebaf2a4c61ff6ca93f11bdbf43e"
+  "source_commit": "ff73d381b4b895ea46ca764d9ad1bf32920faee1"
 }

package/runtime/business-client/README.md

@@ -22,8 +22,15 @@ ml-platform get-dataset <dataset_id> <dataset_version> --project <project>
 ml-platform resolve-dataset <dataset_id> <dataset_version> --project <project>
 ml-platform build-registered-dataset <dataset_id> <dataset_version> \
   --project <project> --wait
+ml-platform register-model-artifact <artifact_id> --evaluation-id <evaluation_result_or_summary_id>
 ```
 
+`resolve-dataset` 返回两个不同的身份：`manifest_hash` 是解析后的 DatasetArtifact
+缓存/构建键，`registered_manifest_hash` 是注册 DatasetManifest 的 canonical 契约哈希。
+构造 `FeatureRetrievalSpec.manifest.manifest_hash` 时必须使用后者；客户端不需要、也不应
+自行复算 Python canonical hash。模型评估结果通过 `register-model-artifact` 交给服务端治理
+校验后注册，不要绕过 CLI 直接调用 HTTP 注册接口。
+
 `resolve-manifest` 和 `build-dataset <manifest.json>` 仍用于尚未注册的本地契约。Catalog
 normalizer 保留并校验非默认 `project`；`apply --project` 与 Catalog 内项目不一致时拒绝执行。
 
@@ -69,9 +76,19 @@ ml-platform get-deployment-events <deployment-id> --limit 100 --offset 0
 ml-platform predict-deployment <deployment-id> /absolute/path/to/request.json
 ```
 
+部署文件可用 `inference_policy` 配置默认执行 horizon 和输出窗口。`boundary` 默认
+`[start,end)`，也可显式使用 `(start,end]`。例如 15 分钟频率、
+当天 00:00 cutoff、只返回次日全天时，配置 `horizon=2d` 和 `[1d,2d)`；模型必须具备
+192 点输出能力，响应返回 96 点。请求可省略 `horizon` 和 `output_window` 使用部署默认值，
+也可携带其中任意一项覆盖；覆盖值仍受模型长度、频率和窗口边界校验。8 天、768 点模型要
+返回次日 00:15 至第八天 24:00，可配置
+`{"start_offset":"1d","end_offset":"8d","boundary":"(start,end]"}`，仍返回 672 点。
+
 直接访问已知外部 Serving URL 时仍可使用 `predict-model`。Chronos-2 v2 的
 `known_future` 协变量放在 inline 请求的 `inputs.future_covariates` 中；每个预测步一行，
-行数必须等于模型的 `prediction_length`。下例为 15 分钟频率、预测 30 分钟；预测明天时
+行数必须等于模型的 `prediction_length`。`feature_lookup` 模式不得传该字段；Serving 会从
+部署绑定的 FeatureSet 在线读取完整未来 Feature 窗口，并只使用
+`available_at <= cutoff_time` 的修订。下例为 15 分钟频率、预测 30 分钟；预测明天时
 同样提供整天的所有未来步：
 
 ```json

package/runtime/business-client/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@zhuoyuezs/ml-platform-business-client",
-  "version": "0.7.7",
+  "version": "0.7.8",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@zhuoyuezs/ml-platform-business-client",
-      "version": "0.7.7",
+      "version": "0.7.8",
       "license": "UNLICENSED",
       "bin": {
         "ml-platform": "src/cli.js"

package/runtime/business-client/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zhuoyuezs/ml-platform-business-client",
-  "version": "0.7.7",
+  "version": "0.7.8",
   "private": true,
   "description": "JavaScript implementation of the ML Platform business client",
   "bin": {

package/runtime/business-client/src/cli.js

@@ -29,12 +29,12 @@ const BUSINESS_COMMANDS = new Set([
   "add-dataset", "update-dataset", "delete-dataset", "list-dataset-artifacts",
   "register-operator", "show-operator-specs", "delete-operator", "run-operator",
   "get-job", "wait-job", "retry-job", "cancel-job", "get-dataset-artifact", "download-dataset-artifact", "fetch-inference-data", "fetch-inference-context", "predict-model", "apply",
-  "register-trainer", "list-trainer-definitions", "get-trainer-definition", "register-training-run", "validate-training-run", "submit-training-job", "get-training-job", "retry-training-job", "cancel-training-job",
+  "list-system-models", "get-system-model", "list-trainer-definitions", "get-trainer-definition", "register-training-run", "validate-training-run", "submit-training-job", "get-training-job", "retry-training-job", "cancel-training-job",
   "register-evaluation-config", "get-evaluation-config", "register-metric-definition", "get-metric-definition",
   "register-executable-package", "verify-executable-package", "publish-executable-package",
   "validate-evaluation-run", "submit-evaluation", "get-evaluation-run", "get-evaluation-job", "retry-evaluation-job", "cancel-evaluation-job", "list-evaluation-attempts",
   "get-evaluation-result", "get-evaluation-result-metrics", "get-evaluation-result-artifacts", "summarize-evaluation-run", "get-evaluation-summary",
-  "create-model-package", "get-model-package", "cancel-model-package", "validate-model-artifact",
+  "create-model-package", "get-model-package", "cancel-model-package", "validate-model-artifact", "register-model-artifact",
   "list-deployment-targets", "validate-deployment", "create-deployment", "list-deployments",
   "get-deployment", "wait-deployment", "reconcile-deployment", "approve-deployment",
   "promote-deployment", "rollback-deployment", "suspend-deployment", "resume-deployment",
@@ -110,7 +110,8 @@ const COMMAND_USAGE = {
   "fetch-inference-data": "fetch-inference-data MANIFEST --cutoff-time TIMESTAMP [--max-workers N] [--max-source-lag-hours HOURS] [--no-validate-freshness] [--allow-missing]",
   "fetch-inference-context": "fetch-inference-context REQUEST_JSON",
   "predict-model": "predict-model REQUEST_JSON --serving-url URL",
-  "register-trainer": "register-trainer DEFINITION_JSON",
+  "list-system-models": "list-system-models",
+  "get-system-model": "get-system-model NAME VERSION [--project PROJECT]",
   "list-trainer-definitions": "list-trainer-definitions",
   "get-trainer-definition": "get-trainer-definition NAME VERSION [--project PROJECT]",
   "register-training-run": "register-training-run RUN_JSON",
@@ -142,6 +143,7 @@ const COMMAND_USAGE = {
   "get-model-package": "get-model-package PACKAGE_ID [--package-version VERSION]",
   "cancel-model-package": "cancel-model-package PACKAGE_ID [--package-version VERSION]",
   "validate-model-artifact": "validate-model-artifact ARTIFACT_ID",
+  "register-model-artifact": "register-model-artifact ARTIFACT_ID --evaluation-id EVALUATION_ID",
   "list-deployment-targets": "list-deployment-targets",
   "validate-deployment": "validate-deployment SPEC_JSON --evaluation-id ID",
   "create-deployment": "create-deployment SPEC_JSON --evaluation-id ID",
@@ -431,9 +433,8 @@ async function runBusinessCli(argv) {
     const out = take(rest, "--out");
     if (out) { const target = resolvedPath(out); fs.mkdirSync(path.dirname(target), { recursive: true }); fs.writeFileSync(target, `${JSON.stringify(result, null, 2)}\n`); }
   } else if (options.command === "resolve-dataset") {
-    const datasetId = positional(rest, "dataset id"); const datasetVersion = positional(rest, "dataset version"); const project = take(rest, "--project", "default"); const api = client(options);
-    const manifest = normalizeRegistryDataset(await registeredDataset(api, project, datasetId, datasetVersion));
-    result = await api.post("/datasets/resolve", manifest);
+    const datasetId = positional(rest, "dataset id"); const datasetVersion = positional(rest, "dataset version"); const project = take(rest, "--project", "default");
+    result = await client(options).post(`/datasets/${encodeURIComponent(project)}/${encodeURIComponent(datasetId)}/${encodeURIComponent(datasetVersion)}/resolve`);
     const out = take(rest, "--out");
     if (out) { const target = resolvedPath(out); fs.mkdirSync(path.dirname(target), { recursive: true }); fs.writeFileSync(target, `${JSON.stringify(result, null, 2)}\n`); }
   } else if (options.command === "build-dataset") {
@@ -598,18 +599,23 @@ async function runBusinessCli(argv) {
   } else if (options.command === "get-executable-package") {
     const name = positional(rest, "package name"); const version = positional(rest, "package version");
     result = await client(options).get(`/executable-packages/${encodeURIComponent(name)}/${encodeURIComponent(version)}`);
+  } else if (options.command === "list-system-models") {
+    result = await client(options).get("/system-models");
+  } else if (options.command === "get-system-model") {
+    const name = positional(rest, "system model name"); const version = positional(rest, "system model version"); const project = take(rest, "--project", "default");
+    result = await client(options).get(`/system-models/${encodeURIComponent(project)}/${encodeURIComponent(name)}/${encodeURIComponent(version)}`);
   } else if (options.command === "list-trainer-definitions") {
     result = await client(options).get("/trainer-definitions");
   } else if (options.command === "get-trainer-definition") {
     const name = positional(rest, "trainer name"); const version = positional(rest, "trainer version"); const project = take(rest, "--project", "default");
     result = await client(options).get(`/trainer-definitions/${encodeURIComponent(project)}/${encodeURIComponent(name)}/${encodeURIComponent(version)}`);
   } else if ({
-    "register-trainer": "/trainer-definitions", "register-training-run": "/training-runs", "validate-training-run": "/training-runs/validate",
+    "register-training-run": "/training-runs", "validate-training-run": "/training-runs/validate",
     "validate-training-job": "/training-jobs/validate", "validate-model-package": "/model-packages/validate", "submit-training-job": "/training-jobs", "register-evaluation-config": "/evaluation-configs", "register-metric-definition": "/metric-definitions",
     "register-executable-package": "/executable-packages", "validate-evaluation-run": "/evaluation-runs/validate", "submit-evaluation": "/evaluation-runs",
     "create-model-package": "/model-packages",
   }[options.command]) {
-    const endpoint = { "register-trainer": "/trainer-definitions", "register-training-run": "/training-runs", "validate-training-run": "/training-runs/validate", "validate-training-job": "/training-jobs/validate", "validate-model-package": "/model-packages/validate", "submit-training-job": "/training-jobs", "register-evaluation-config": "/evaluation-configs", "register-metric-definition": "/metric-definitions", "register-executable-package": "/executable-packages", "validate-evaluation-run": "/evaluation-runs/validate", "submit-evaluation": "/evaluation-runs", "create-model-package": "/model-packages" }[options.command];
+    const endpoint = { "register-training-run": "/training-runs", "validate-training-run": "/training-runs/validate", "validate-training-job": "/training-jobs/validate", "validate-model-package": "/model-packages/validate", "submit-training-job": "/training-jobs", "register-evaluation-config": "/evaluation-configs", "register-metric-definition": "/metric-definitions", "register-executable-package": "/executable-packages", "validate-evaluation-run": "/evaluation-runs/validate", "submit-evaluation": "/evaluation-runs", "create-model-package": "/model-packages" }[options.command];
     result = await client(options).post(endpoint, readSpec(positional(rest, "request JSON")));
   } else if (/^(get|retry|cancel)-training-job$/.test(options.command)) {
     const jobId = positional(rest, "training job id"); const endpoint = `/training-jobs/${encodeURIComponent(jobId)}`;
@@ -632,6 +638,11 @@ async function runBusinessCli(argv) {
     const name = positional(rest, "package name"); const version = positional(rest, "package version"); const action = options.command.split("-")[0];
     result = await client(options).post(`/executable-packages/${encodeURIComponent(name)}/${encodeURIComponent(version)}/${action}`);
   } else if (options.command === "validate-model-artifact") result = await client(options).get(`/model-artifacts/${encodeURIComponent(positional(rest, "model artifact id"))}/validate`);
+  else if (options.command === "register-model-artifact") {
+    const artifactId = positional(rest, "model artifact id"); const evaluationId = take(rest, "--evaluation-id");
+    if (!evaluationId) throw new Error("--evaluation-id is required");
+    result = await client(options).post(`/models/${encodeURIComponent(artifactId)}/register`, { evaluation_id: evaluationId });
+  }
   else if (/^(get|cancel)-model-package$/.test(options.command)) {
     const packageId = positional(rest, "model package id"); const params = { package_version: take(rest, "--package-version") }; const endpoint = `/model-packages/${encodeURIComponent(packageId)}`;
     result = options.command === "get-model-package" ? await client(options).get(endpoint, params) : await client(options).post(`${endpoint}/cancel`, undefined, params);

package/skills/feature-management/SKILL.md

@@ -205,11 +205,14 @@ platform source checkout or a local Catalog directory for a matching JSON file.
    target from a similar local filename.
 4. Run `get-dataset <dataset_id> <dataset_version> --project <project>` and
    inspect the returned registered contract.
-5. Run `resolve-dataset` for a read-only dependency and manifest-hash check.
+5. Run `resolve-dataset` for a read-only dependency and identity check. Use its
+   `registered_manifest_hash` for `FeatureRetrievalSpec.manifest.manifest_hash`;
+   use its `manifest_hash` only as the resolved DatasetArtifact/build key.
 6. Submit exactly one `build-registered-dataset ... --wait` only after the user
    authorizes that exact registered version.
-7. Use the returned Job ID with `get-job`, then use the returned manifest hash
-   with `get-dataset-artifact` after success.
+7. Use the returned Job ID with `get-job`, then use the resolved `manifest_hash`
+   with `get-dataset-artifact` after success. Keep the separate
+   `registered_manifest_hash` for FeatureRetrievalSpec binding.
 
 Local `resolve-manifest` and `build-dataset <file>` remain authoring tools for a
 new or changed Catalog contract before it is registered. They are not required
@@ -419,6 +422,17 @@ replayable `as_of` manifest; when an online source override is active, `replay.s
 must be false because the offline manifest cannot reproduce that source. Report
 tolerated missing or gap-filled inputs as degraded freshness, not as a normal read.
 
+Model-serving `feature_lookup` may additionally request declared known-future
+Features from the same FeatureSet. Do not emulate that by passing model inputs
+through this Skill. Author their Parameters with trustworthy availability
+evidence: future event times are valid, but only revisions with
+`available_at <= cutoff_time` may be used. `available_at` may therefore be
+earlier than `event_time` for forecasts and schedules. The platform reads only
+the requested known-future Features and their Parameter dependency closure;
+unrelated historical Parameters in the same DatasetManifest do not need a
+future-visibility contract. Every Parameter inside the requested closure still
+fails closed when trustworthy availability is absent.
+
 ## Verify The Artifact
 
 Treat Registry metadata inspection and downloaded-file inspection as separate
@@ -461,7 +475,7 @@ Require all of the following before reporting success:
   windows tiling the fetch range, and any retries are accounted for;
 - missing values and warnings are reported, not silently repaired.
 
-The manifest hash returned by `resolve-manifest` or `resolve-dataset` is the artifact key: it stays
+The `manifest_hash` returned by `resolve-manifest` or `resolve-dataset` is the artifact key: it stays
 the same after the build, so it is usable for cache reuse and polling before
 submission. Distinguish the two lookup failures rather than treating both as "not
 ready" — `422` with `invalid_artifact_key` means the key can never name an
@@ -480,7 +494,7 @@ new / unchanged assets by type
 planned versus resolved dependency versions and any explicitly retained old versions
 Operator package filename and SHA-256
 FeatureSet and ordered feature count
-dataset id, version, manifest hash, and Job id
+ dataset id, version, resolved manifest hash, registered manifest hash when applicable, and Job id
 row and column counts
 rowset candidate / policy-applied / eligible / ineligible counts when endpoint_policy is declared
 validation status, warnings, and missing-data summary

package/skills/feature-management/references/commands.md

@@ -220,7 +220,8 @@ DatasetManifest hash. The initial implementation is sequential, so keep
 `--max-parallelism 1`. Completed partitions are checkpointed and resumed by
 default; use `--no-resume` only to force a clean execution.
 
-Record the returned `job_id`, `dataset_id`, and `manifest_hash`. If a separate wait is needed:
+Record the returned `job_id`, `dataset_id`, and resolved `manifest_hash`; for a registered Dataset
+also retain `registered_manifest_hash` for FeatureRetrievalSpec binding. If a separate wait is needed:
 
 ```bash
 ml-platform --profile server wait-job <job_id>
@@ -266,7 +267,8 @@ ml-platform --profile server fetch-inference-context /tmp/inference-context.json
 ```
 
 The `FeatureRetrievalSpec` must bind an existing inference-mode DatasetManifest
-by project, dataset id, version, and manifest hash; its FeatureSet and contract
+by project, dataset id, version, and the `registered_manifest_hash` returned by
+`resolve-dataset`; its FeatureSet and contract
 signature must match the resolved online contract. Context mode also fixes
 `context_length`, `frequency`, `context_end`, `stride`, input-adapter hash, and
 temporal-binding hash. Do not replace these immutable deployment bindings with

package/skills/feature-management/references/contracts.md

@@ -138,6 +138,12 @@ supported field.
 当前严格 `as_of` 只接受 `exact` 或有合同支撑的 `upper_bound`；修改这些语义需要发布
 新的 Parameter 业务版本。
 
+未来预报、排程、日历等 known-future 数据允许 `available_at < event_time`。这不是时钟错误：
+`event_time` 是未来目标时刻，`available_at` 是该修订何时已可读取。模型
+`feature_lookup` 会读取 cutoff 后的未来事件窗口，但仍严格过滤
+`available_at <= cutoff_time`。因此这类 Parameter 应优先使用能表达预报签发时间或计划发布
+时间的 `source_field`，不能用事后实测值替代，也不能用调用方请求绕过 availability 合同。
+
 An optional `rounding` section states the fixed-point precision the platform
 enforces at the Parameter boundary:
 

package/skills/model-deployment-management/SKILL.md

@@ -28,6 +28,13 @@ deployment does not reach `READY` or an operation is rejected.
   `ml-platform --profile server health` before control-plane work.
 - Use only a `READY` ModelPackage image with an immutable `@sha256:` digest and
   the package-bound FeatureRetrievalSpec and smoke request.
+- When `DeploymentSpec.inference_policy` is configured, treat its horizon and
+  output window as request defaults. The window boundary defaults to
+  `[start,end)` and may explicitly use `(start,end]`. Prediction requests may omit or
+  override `horizon` and `output_window`; every effective combination must fit
+  the model capacity and sampling grid. In `feature_lookup` mode, never send
+  `future_covariates`; the platform retrieves the complete known-future Feature
+  window visible at the cutoff. Inline mode still supplies those rows in inputs.
 - Run `validate-deployment` before `create-deployment`. Validation is read-only
   and does not authorize creation.
 - Obtain explicit authorization for the exact deployment and operation before
@@ -36,9 +43,20 @@ deployment does not reach `READY` or an operation is rejected.
   returned an ambiguous result.
 - Treat `READY` as valid only when `ReplicasReady`, `ArtifactsVerified`, and
   `SmokePredictionPassed` are all true for the current revision.
-- Use `predict-deployment`; it routes through the control plane to the recorded
-  deployment endpoint. Do not infer Kubernetes Service names or require the
-  user to reach a cluster-local URL.
+- Use `predict-deployment` for governed deployment verification. Do not infer
+  Kubernetes Service names from a deployment ID.
+- Treat every prediction response `target_time` as China Standard Time in RFC
+  3339 `+08:00` form. The represented instant remains identical to the UTC
+  cutoff and output-window calculations.
+- `DeploymentSpec.service_exposure` defaults to `ClusterIP`. An explicit
+  `NodePort` value creates one deployment-level direct Serving Service that
+  follows the current revision; it does not replace validation, approval,
+  rollout, READY gates, or audit history.
+- Every model Serving process publishes that model's Swagger UI at `/docs`,
+  OpenAPI JSON at `/openapi.json`, and ReDoc at `/redoc`. The document embeds
+  the deployed artifact identity and its actual input modes, ordered columns,
+  horizon semantics, known-future contract, and output schema. These are model
+  data-plane documents, not the control-plane API documentation.
 - Never create, modify, or delete NetworkPolicy. Cluster operators own that
   boundary.
 

package/skills/model-deployment-management/references/contracts.md

@@ -16,7 +16,23 @@ load-bearing fields:
   "package_version": "1",
   "image": "registry.example/model-serving@sha256:<64-hex>",
   "target": {"type": "kubernetes", "namespace": "itsmp-model-serving"},
+  "service_exposure": {
+    "type": "NodePort",
+    "port": 80,
+    "node_port": 32080,
+    "advertised_host": "10.36.9.212",
+    "scheme": "http"
+  },
   "feature_retrieval": {},
+  "inference_policy": {
+    "horizon": {"duration": "2d"},
+    "output_window": {
+      "start_offset": "1d",
+      "end_offset": "2d",
+      "boundary": "[start,end)"
+    },
+    "allow_request_override": true
+  },
   "replicas": 1,
   "resources": {},
   "rollout": {"strategy": "canary", "traffic_percent": 10},
@@ -29,15 +45,56 @@ They must match the registered artifact lineage and the tested ModelPackage.
 The server normalizes an omitted lookup test from the package during
 validation and creation.
 
+`inference_policy` is optional. When present, its horizon and offsets must be
+whole-minute durations aligned to the model sampling frequency. `boundary`
+defaults to `[start,end)` and may be `(start,end]`. The selected interval must
+be non-empty, end within the configured horizon, and fit the model's maximum
+sequence output. A 15-minute model using `horizon=2d` and `[1d,2d)` therefore
+needs at least 192 output steps and returns 96 steps. An 8-day, 768-step model
+using `(1d,8d]` returns step 97 through step 768: next-day 00:15 through day-eight
+24:00, 672 points total. This is a response projection, not extra model capacity.
+
+The deployment values are defaults. Calls may omit `horizon` and
+`output_window`, override either one, or override both. Serving validates the
+effective values again; an output window must remain non-empty, aligned, inside
+the effective horizon, and within model capacity. Set
+`allow_request_override=false` only when the endpoint must reject non-equivalent
+request values. An override that omits `boundary` uses `[start,end)`; include
+`boundary` explicitly to preserve `(start,end]` semantics.
+
+Known-future covariates still cover the model's complete prediction length,
+including points outside a shorter returned window. In `feature_lookup` mode,
+Serving requests those Feature columns from the deployment-bound FeatureSet;
+the platform permits future event times only when `available_at <= cutoff_time`.
+The prediction caller must not send top-level `future_covariates`. Inline mode
+continues to carry them in `inputs.future_covariates`.
+
 The first deployment starts at `staging`. A replacement for an existing
 service/environment declares the active leaf in `previous_deployment_id`.
 Production is reached only by staging to canary to production promotion.
 
+`service_exposure` is optional and defaults to `{"type":"ClusterIP"}`. Set
+`type=NodePort` only when direct node access is required. `node_port` is
+optional; when omitted Kubernetes allocates it, and the observed endpoint
+reports the assigned value. An explicit value must be in `30000..32767`.
+`advertised_host` is also optional: provide it only when that node address is
+known to be reachable by callers. Without it, the endpoint returns a URL
+template rather than claiming external reachability.
+
+The controller keeps preview, stable, and canary Services as ClusterIP for
+verification and Gateway traffic. NodePort exposure uses one fixed-name Service
+per DeploymentSpec and creates or updates it only after the revision passes all
+READY gates. Retained revisions of that deployment share the Service, while a
+replacement deployment receives a different Service so staging cannot rewrite
+the existing production route. When replacement deployments request explicit
+ports, their values must not collide while both deployments exist.
+
 ## Revision State
 
-`DeploymentSpec` is immutable. Promotion, rollback, suspension, resumption,
-and undeploy append immutable revisions. Reconcile writes mutable observed
-state separately.
+`DeploymentSpec` is immutable. Its inference policy and full deployment contract
+hash are copied into each immutable revision. Promotion, rollback, suspension,
+resumption, and undeploy append revisions that retain that policy. Reconcile
+writes mutable observed state separately.
 
 `READY` requires all three current-revision conditions:
 
@@ -50,6 +107,12 @@ The detail response includes `endpoints`. Cluster-local endpoints have
 when rollout hostname metadata exists. `available=true` means the current
 revision passed all READY gates.
 
+Each endpoint advertises `inference_path=/v1/inference`, `docs_url`,
+`openapi_url`, and `redoc_url`. When no reviewed host is available, the
+NodePort endpoint returns corresponding URL templates instead. The Serving
+OpenAPI document is generated for the deployed ModelArtifact and embeds the
+effective model contract; it is not a generic platform API schema.
+
 Successful smoke verification is cached durably by revision, image digest,
-contract hash, and frozen lookup-test hash. A new revision or changed identity
-must run smoke again.
+FeatureRetrieval contract hash, deployment contract hash, and frozen lookup-test
+hash. A new revision or changed identity must run smoke again.

package/skills/model-deployment-management/references/operations.md

@@ -29,6 +29,22 @@ Use `get-deployment` to inspect the full revision history and endpoints. Use
 `list-deployments` for discovery and `get-deployment-events` for paginated
 audit evidence.
 
+For direct model access, declare `service_exposure.type=NodePort` in the same
+validated DeploymentSpec. After the revision is `READY`, read the observed
+`nodeport` endpoint instead of constructing a Service name. Given an observed
+base URL such as `http://<node-ip>:<node-port>`:
+
+```bash
+curl http://<node-ip>:<node-port>/v1/model
+curl http://<node-ip>:<node-port>/openapi.json
+```
+
+Open `http://<node-ip>:<node-port>/docs` for that model's Swagger UI or
+`http://<node-ip>:<node-port>/redoc` for ReDoc. The schemas describe the exact
+deployed model. NodePort network reachability remains an environment concern;
+do not report it as reachable unless `advertised_host` was reviewed and the
+client can connect.
+
 ## Promotion And Approval
 
 ```bash
@@ -68,6 +84,47 @@ history; it is not equivalent to resume.
 
 ## Prediction
 
+With a deployment-level inference policy, the request may use both deployment
+defaults by omitting `horizon` and `output_window`:
+
+```json
+{
+  "input_mode": "feature_lookup",
+  "cutoff_time": "2026-09-14T00:00:00+08:00",
+  "entity": {}
+}
+```
+
+To override the revision defaults, add either or both fields. This example keeps
+the deployment horizon but returns its first day:
+
+```json
+{
+  "input_mode": "feature_lookup",
+  "cutoff_time": "2026-09-14T00:00:00+08:00",
+  "entity": {},
+  "output_window": {
+    "start_offset": "0min",
+    "end_offset": "1d",
+    "boundary": "[start,end)"
+  }
+}
+```
+
+For the storage-power deployment that predicts eight days but returns only
+next-day 00:15 through day-eight 24:00, use the deployment default or override
+with `{"start_offset":"1d","end_offset":"8d","boundary":"(start,end]"}`.
+
+Do not send `future_covariates` in `feature_lookup` mode. Serving derives the
+declared known-future columns and full model prediction length from the
+ModelArtifact, then the platform retrieves visible future Feature revisions.
+Only those Features and their Parameter dependency closure are read; unrelated
+historical Parameters in the same inference Manifest are not evaluated as
+future inputs. Requested future Parameters must still provide trustworthy
+`available_at <= cutoff_time` evidence.
+For inline mode only, supply one row per model prediction step in
+`inputs.future_covariates`.
+
 ```bash
 ml-platform --profile server predict-deployment <deployment-id> \
   /absolute/path/request.json

package/skills/model-deployment-management/references/troubleshooting.md

@@ -14,8 +14,37 @@ Interpret conditions before considering a reconcile:
   readiness through the platform/cluster diagnostic boundary.
 - `ArtifactsVerified=false`: the Serving `/model` identity does not match the
   revision, or the endpoint is unavailable.
+- A NodePort endpoint with `url=null` is not a failed deployment. Kubernetes
+  assigned or will assign the port, but the DeploymentSpec did not declare a
+  reviewed `advertised_host`; use the returned `node_port` with a reachable
+  cluster node address.
+- `/docs` or `/openapi.json` showing the wrong artifact identity indicates that
+  traffic is reaching a different Serving revision. Compare the document's
+  top-level `x-itsmp-model.artifact_id` with the observed DeploymentRevision.
 - `SmokePredictionPassed=false`: preserve the frozen package smoke request and
   error. Do not replace it with a current-time request to force success.
+- `request horizon cannot override deployment inference_policy` or
+  `request output_window cannot override deployment inference_policy`: the
+  revision has `allow_request_override=false`; use equivalent values or create
+  a reviewed revision whose policy permits the required request behavior.
+- `inference_policy output window must end within the configured horizon`:
+  override `horizon` and `output_window` together, or keep the deployment
+  defaults. A shorter horizon cannot retain a later default window.
+- `feature_lookup obtains known future covariates from online retrieval`: remove
+  top-level `future_covariates`. Verify the columns belong to the bound
+  FeatureSet and their Parameters provide trustworthy `available_at` values.
+- `availability_not_supported` or `available_at_missing` during future lookup:
+  publish a corrected Parameter/Feature dependency version with a source-field
+  or justified upper-bound availability contract; do not substitute caller data.
+- `inference_policy horizon exceeds model maximum prediction length`: retrain
+  or select a model artifact with enough sequence steps. For `[1d,2d)` at
+  15-minute frequency, the model needs 192 steps, not only the returned 96.
+- An unexpected output point count usually indicates frequency/target-time
+  drift or an incomplete runtime trajectory. Inspect `output_window.boundary`,
+  UTC `start_time`/`end_time`, `point_count`, and the model sampling interval.
+- If a right-closed deployment unexpectedly returns next-day 00:00 and omits
+  day-eight 24:00, check whether a request-level `output_window` omitted
+  `boundary`; omission intentionally falls back to `[start,end)`.
 - `SUPERSEDED`: operate on the active deployment leaf.
 - `SUSPENDED`: resume only with explicit authorization and a reason.
 - `UNDEPLOYED`: create a governed deployment or rollback as supported; resume

package/skills/model-lifecycle-management/SKILL.md

@@ -32,6 +32,7 @@ to discover fields. Preserve release/error evidence when deployment differs.
 - Before submission, show the exact JSON path, immutable identities, expected workload, and target API. Obtain explicit authorization. Retry and cancel require separate authorization for the exact Job.
 - Never use `latest` image tags. During development TrainerDefinition stays at `v1`; rebinding it follows the reviewed release procedure and requires confirming no active Job references the old definition.
 - A succeeded Job is insufficient evidence. Training requires a valid ModelArtifact and signature; evaluation requires immutable Result/Summary evidence and coverage; packaging requires `READY`, an immutable image digest, manifest, and passing test report.
+- Register a ModelArtifact through `register-model-artifact` only after a platform-generated PASS evaluation/result or summary has complete evidence; do not bypass the CLI with a direct registration HTTP request.
 - Do not register caller-computed evaluation results. Workers produce predictions, metrics, decisions, and summaries from frozen DatasetArtifact rowsets.
 - Keep credentials, registry secrets, Kubernetes details, and model binaries out of request JSON and reports.
 

package/skills/model-lifecycle-management/references/packaging.md

@@ -24,6 +24,14 @@ do not guess registries or pass deployment secrets. A mismatch needs the approve
 runtime contract, not repeated package versions. Unknown request keys return 422; do not add `runtime`, `image`, or `resources`
 fields. Inspect the returned resolved package.
 
+Chronos-2 LoRA packages also require exactly one platform-managed
+`chronos2-checkpoint` runtime artifact for the selected trainer/device binding.
+It must set `DATA_PLATFORM_CHRONOS2_MODEL_PATH`; otherwise
+`validate-model-package` fails before a Kubernetes Job is created. Cache-hit
+messages for `adapter_model.safetensors` or `model.chronos2` do not prove that
+the base checkpoint is present. Full fine-tuned Chronos-2 artifacts contain
+their complete weights and do not require this external checkpoint.
+
 `input_modes` must be unique, include `inline`, and may additionally include
 `feature_lookup` or `tabular_forecast` only when supported by the selected
 runtime. `feature_lookup` still requires artifact lineage
@@ -31,6 +39,17 @@ runtime. `feature_lookup` still requires artifact lineage
 signature. Do not infer either capability from training success.
 Omit rather than use an empty list to request default inline behavior.
 
+Register a validated artifact only after a platform-generated evaluation result or
+summary is `PASS`, `COMPLETE`, and belongs to the same artifact:
+
+```bash
+ml-platform --profile server register-model-artifact <artifact-id> \
+  --evaluation-id <evaluation-result-or-summary-id>
+```
+
+The API performs the complete registration gate. Do not replace this command with
+a direct `POST /models/{artifact_id}/register` request.
+
 For `feature_lookup`, the package request must bind both the exact retrieval
 contract and a sanitized real lookup test. They are immutable package identity,
 not namespace Secret/ConfigMap settings:
@@ -74,6 +93,11 @@ not namespace Secret/ConfigMap settings:
 The inference DatasetManifest must exist with the supplied hash and use
 `mode=inference`. Its FeatureSet, stable contract signature, adapter/temporal
 hashes, entity keys, and row/context parameters must match the ModelArtifact.
+The package-bound signature remains the Serving binding identity. Online fetch
+responses may also report an independently resolved execution signature for
+diagnostics; database principals are excluded from new stable signatures, so
+credential rotation or distinct read-only workload accounts do not alter the
+model data contract.
 The test cutoff must include a timezone. A legacy feature-lookup package missing
 either package-bound field remains readable but cannot be rerun or deployed;
 create a new package version.

package/skills/model-lifecycle-management/references/training-contracts.md

@@ -169,10 +169,12 @@ and `data.labels` must use that same output-label order:
 Every target and covariate must be a numeric Feature. `past_only` is available
 only through the cutoff. `known_future` must be represented in training by the
 forecast or schedule available at that historic cutoff, never by a later actual
-observation. At runtime callers provide one finite numeric value for every
-`known_future` column and every prediction step. The current contract validates
-the names, values, and row count; retain forecast issue/availability lineage in
-the upstream Feature data when revisions must be audited.
+observation. At runtime inline callers provide one finite numeric value for
+every `known_future` column and every model prediction step. In
+`feature_lookup` mode, callers provide none: Serving requests the declared
+Feature columns from the deployment-bound FeatureSet, and the platform selects
+future event rows whose revisions satisfy `available_at <= cutoff_time`.
+Retain forecast issue/availability lineage in the upstream Feature data.
 
 ## TrainingJobRequest and identity propagation
 
@@ -243,6 +245,16 @@ aligned horizons up to that maximum and returns the corresponding trajectory
 prefix; it rejects unaligned or longer horizons. A one-step model remains a
 scalar response.
 
+When a deployment must use cutoff at today's 00:00 and return only tomorrow's
+00:00 through the following 00:00, train for the complete interval from cutoff
+to the output end. At 15-minute frequency, deployment horizon `2d` means
+`prediction_length=192`; output window `[1d,2d)` then projects the second 96
+points. Chronos-2 known-future covariates must still contain all 192 rows. In
+`feature_lookup` mode the platform retrieves those rows even when the request
+overrides the returned window; inline requests must still carry them. A
+150-step artifact cannot serve this contract and must be retrained rather than
+having its response window stretched at deployment time.
+
 `gap_policy=fill` requires `padding_policy=edge` or `zero`; non-fill requires
 `padding_policy=none`. Filling changes model inputs and needs an intended
 business policy. `skip` and padding are not automatic fixes for rejected grids.

package/skills/model-lifecycle-management/references/training.md

@@ -93,15 +93,18 @@ the ordered target/output-label pairs; see [training-contracts.md](training-cont
 for the complete JSON fragment.
 
 Training records must contain the forecast that was available at each historic
-cutoff, not actual weather observed later. At online inference, pass one numeric
-row per forecast step using the Serving runtime, not `fetch-inference-data`:
+cutoff, not actual weather observed later. Invoke the Serving runtime, not
+`fetch-inference-data`:
 
 ```bash
 ml-platform predict-model /absolute/path/to/inference-request.json \
   --serving-url https://storage-forecast.example
 ```
 
-For `input_mode=inline`, put those rows in `inputs.future_covariates`. For
-`input_mode=feature_lookup`, put them in the top-level `future_covariates`.
-Their column names must exactly match the adapter's `known_future` covariates,
-and their count must equal the trained `prediction_length`.
+For `input_mode=inline`, put one row per trained prediction step in
+`inputs.future_covariates`; names must exactly match the adapter's
+`known_future` columns. For `input_mode=feature_lookup`, do not send future
+rows. Serving asks the platform for the declared columns and full
+`prediction_length`; the Features must belong to the deployment-bound
+FeatureSet, and their source revisions must satisfy
+`available_at <= cutoff_time` even though their event times are later.