@zhuoyuezs/ml-platform 0.1.8 → 0.1.9

package/checksums.json

@@ -37,8 +37,8 @@
     },
     {
       "path": "skills/feature-management/SKILL.md",
-      "sha256": "sha256:50646fd4c5884fe25b9488f223b680ad44417b96da160950b454202ea756e7f8",
-      "size_bytes": 30846
+      "sha256": "sha256:5b3ce57d84f11188579227dd42617075f87534ac113a3f37b3543c85c0ff0b3d",
+      "size_bytes": 31114
     },
     {
       "path": "skills/feature-management/agents/openai.yaml",
@@ -97,8 +97,8 @@
     },
     {
       "path": "skills/feature-management/references/contracts.md",
-      "sha256": "sha256:b705dec6e801f95d0d354a0d0f0d6fb5bd139d5f9938f78d70f1fe108b7c95b9",
-      "size_bytes": 27741
+      "sha256": "sha256:d9ff95edb3ac50cb590df640c5034d45ddd5b758431a4ae2e69eb807bb659314",
+      "size_bytes": 28449
     },
     {
       "path": "skills/feature-management/references/operator-authoring.md",
@@ -137,18 +137,18 @@
     },
     {
       "path": "skills/model-lifecycle-management/references/packaging.md",
-      "sha256": "sha256:fd87f0ea6f79bff0498ff1688ab782340d572815872c86520032549910160028",
-      "size_bytes": 2858
+      "sha256": "sha256:8435283061d740e57aafc90fa402cd89adcd8e2e957805b3d435ea4ba1f8721c",
+      "size_bytes": 3142
     },
     {
       "path": "skills/model-lifecycle-management/references/training-contracts.md",
-      "sha256": "sha256:e93f5361f5f7cfaef53ba65b2606e58b06585d7de6c966706c66995e844b4804",
-      "size_bytes": 6909
+      "sha256": "sha256:1d1fa51ef7deb6abf178cf019eb69e8ee6a93ecb018029780f01a33696473dd6",
+      "size_bytes": 8229
     },
     {
       "path": "skills/model-lifecycle-management/references/training.md",
-      "sha256": "sha256:10a6694f1904ce210f062221273a0687574354764bafb573318a5f7fcb425e55",
-      "size_bytes": 4206
+      "sha256": "sha256:370d5e663292ce1bdcf0eb88c133c07a77f57dd31e21748906c92aa3407c4e95",
+      "size_bytes": 4516
     }
   ],
   "schema_version": "data_platform.ml_platform_checksums/v1"

package/package.json

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

package/release.json

@@ -25,7 +25,7 @@
     "ml_data_platform.feature_set/v1",
     "ml_data_platform.dataset_manifest/v1"
   ],
-  "release_version": "0.1.8",
+  "release_version": "0.1.9",
   "runtime_requirements": {
     "node": ">=18",
     "os": [
@@ -38,15 +38,15 @@
     "feature-management": {
       "path": "skills/feature-management",
       "requires_cli": ">=0.7.0 <0.8.0",
-      "revision": "0.1.8",
-      "sha256": "sha256:38ec81d73353bf8eb39ae56074c15cc0fcae14701e8aba1462b5cbd155a1fa65"
+      "revision": "0.1.9",
+      "sha256": "sha256:82a49a3f636d4e1a4b5adf28cbcab533168e3aa5fc3014f096149055e7745624"
     },
     "model-lifecycle-management": {
       "path": "skills/model-lifecycle-management",
       "requires_cli": ">=0.7.0 <0.8.0",
-      "revision": "0.1.8",
-      "sha256": "sha256:e3eefccb76748847975024cc6fc124df1a581d286d8de165195bd708f5dfa00f"
+      "revision": "0.1.9",
+      "sha256": "sha256:b84505ee632967d019e97f89292c0041f8b722bd320e7d68d170e41131edaff7"
     }
   },
-  "source_commit": "07afde3b78bcf2fcee220a136f226c0ccdf96e38"
+  "source_commit": "5f855cd27f7951b739424704ea7dc15d714aeb5d"
 }

package/skills/feature-management/SKILL.md

@@ -107,7 +107,8 @@ Confirm:
 
 - the target project (namespace) for the assets; use the built-in `default` only when the user has no dedicated project. After the target is confirmed, write its explicit `project` field in every Parameter, Operator, Feature, FeatureSet and DatasetManifest draft; never rely on the schema default. Reads and filters use the `--project` command option;
 - business meaning, stable asset names, owner, and intended consumers;
-- Parameter source adapter and credential-free source mapping;
+- Parameter source adapter (`postgresql_direct`, `mysql_direct`,
+  `sqlserver_direct`, or `influxdb_direct`) and credential-free source mapping;
 - feature formula, exact Parameter dependencies, windows, inclusion rules, rounding, null behavior, and output dtype;
 - whether an approved Operator already implements the formula;
 - FeatureSet column order;
@@ -255,7 +256,7 @@ unit, time/availability semantics and missing policy in the semantic review.
 Never infer a source table, column, measurement, tag, unit or timezone from a
 Parameter name.
 
-Create one stable, versioned source contract for each independently readable value. Keep credentials out of JSON. Use only supported direct adapters and explicit source identity. Put source data validity in `quality_rules`; put dataset-specific transformations in preprocess Operators.
+Create one stable, versioned source contract for each independently readable value. Keep credentials out of JSON. Use only supported direct adapters (`postgresql_direct`, `mysql_direct`, `sqlserver_direct`, and `influxdb_direct`) and explicit source identity. The server supplies database DSNs from managed Secrets; never add them to CLI arguments or Catalog JSON. Put source data validity in `quality_rules`; put dataset-specific transformations in preprocess Operators.
 
 When the approved source contract supplies SQL, copy its query text and named
 parameters exactly into `source.sql`/`source.params`. Do not retype, beautify,

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

@@ -127,7 +127,9 @@ tie with a different rule cannot be repaired downstream. Do not repeat the same
 Parameter-level rounding in an Operator. Changing the mode, decimals, or stage
 requires a new Parameter version and the affected reverse-dependency closure.
 
-PostgreSQL direct-column example:
+PostgreSQL, MySQL, and SQL Server direct-column Parameters share this source
+shape. Set `adapter` to `postgresql_direct`, `mysql_direct`, or
+`sqlserver_direct`; keep database-specific DSNs in server-managed Secrets.
 
 ```json
 {
@@ -143,6 +145,16 @@ PostgreSQL direct-column example:
 }
 ```
 
+The same contract for MySQL or SQL Server changes only the adapter name:
+
+```json
+{"adapter": "mysql_direct", "mode": "direct_column", "schema": "process_data", "table": "sensor_readings", "time_column": "event_time", "value_column": "hot_blast_pressure", "metric_name": "hot_blast_pressure"}
+```
+
+```json
+{"adapter": "sqlserver_direct", "mode": "direct_column", "schema": "process_data", "table": "sensor_readings", "time_column": "event_time", "value_column": "hot_blast_pressure", "metric_name": "hot_blast_pressure"}
+```
+
 InfluxDB direct-column example:
 
 ```json

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

@@ -44,6 +44,11 @@ Confirm the ModelArtifact, signature, runtime, immutable base/builder/worker ima
 
 A deliverable package is `READY` and includes its remote image digest, immutable reference, manifest, signature and adapter hashes, runtime capabilities, and a passing test report for the same digest. Other states are not deliverable.
 
+For a sequence-output artifact, inspect the returned runtime contract for
+`output_schema.kind=sequence`, its fixed maximum `length` and frequency, and
+`horizon_prediction=prefix`. Inference returns the requested aligned prefix up
+to that maximum; a one-step artifact remains scalar.
+
 ```bash
 ml-platform --profile server cancel-model-package <package-id> --package-version <version>
 ```

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

@@ -11,7 +11,7 @@ Example forecasting sequence run:
 
 ```json
 {
-  "schema_version": "ml_data_platform.training_run/v2",
+  "schema_version": "ml_data_platform.training_run/v3",
   "run_id": "pressure_forecast_run_01",
   "experiment": "pressure_forecast",
   "task": {"kind": "forecasting", "objective": "regression"},
@@ -38,6 +38,14 @@ Example forecasting sequence run:
     "context_end": "prediction_time_inclusive", "frequency": "5min",
     "stride": 1, "gap_policy": "reject", "padding_policy": "none"
   },
+  "forecast_target_adapter": {
+    "schema_version": "ml_data_platform.forecast_target_adapter/v1",
+    "kind": "continuous_target_series",
+    "target_input_column": "pressure",
+    "output_label_column": "future_pressure",
+    "target_gap_policy": "reject",
+    "point_output": {"statistic": "median", "step": "horizon"}
+  },
   "label_transform": {"name": "identity", "version": "v1"},
   "trainer": {
     "project": "default", "name": "replace_approved_trainer", "version": "v1",
@@ -128,6 +136,18 @@ null Features or labels also skip samples. Candidate row counts therefore are
 not training/evaluation sample counts. Report the materialized population and
 coverage instead of assuming all Parquet rows were used.
 
+For `continuous_target_series`, TrainingRun v3 derives the fixed maximum
+`prediction_length` as `data.temporal.horizon / data.temporal.frequency`; the
+horizon must be a positive exact multiple of the frequency. The target input
+must be a numeric, at-prediction Feature and the output label must be the sole
+entry in `data.labels`. Use this adapter only when the inspected TrainerDefinition
+advertises `forecast_target_modes=["continuous_target_series"]`.
+
+The resulting model emits the complete fixed-length trajectory. Serving accepts
+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.
+
 `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.
@@ -137,3 +157,8 @@ EvaluationConfig uses versioned names such as `regression.mae`. They are differe
 contracts. Training `evaluation.split=auto` prefers nonempty test, then validation,
 then train; choose an explicit split when reserving the test set for final review.
 Training metrics are not a governed EvaluationResult or release gate pass.
+
+For sequence outputs, current training and governed evaluation apply regression
+metrics to the terminal point at the trained maximum horizon. They do not yet
+provide per-step or whole-trajectory release gates; record this limitation when
+reporting evidence for a multi-point package.

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

@@ -7,7 +7,7 @@ FeatureSet order and evaluation runtime before the first Job. See
 [evaluation.md](evaluation.md) for inherited split bindings and runtime failures.
 
 - Inspect exact TrainerDefinition `project/name:v1`, entrypoint, image digest,
-  capabilities and parameter schema. Similar names in different projects are
+  capabilities (including `forecast_target_modes`) and parameter schema. Similar names in different projects are
   distinct identities; registration does not imply runtime approval.
 - Match definition and device to the active runtime release. On `not approved
   for device`, preserve the rejected identity, device and release ID. Use `get-model-runtime-release` to find the
@@ -21,6 +21,10 @@ FeatureSet order and evaluation runtime before the first Job. See
   `label_time - prediction_time`, and validate the complete TrainingRun before
   registration/submission. Validation may not catch undeclared plugin limits or
   missing dependencies in the eventual Worker.
+- For a continuous future trajectory, use TrainingRun v3 with
+  `forecast_target_adapter.kind=continuous_target_series`. Its fixed maximum
+  prediction length comes from temporal horizon divided by frequency; do not
+  put `prediction_length` in trainer-specific parameters.
 
 Merge this fragment under TrainingRun `data`, alongside `artifact`, `features`,
 `labels` and the applicable `temporal` binding: