rm the flexibility of disable propagation for simplicity

Author: feiyang3cat

openapi/openapiv2.json

@@ -16754,7 +16754,7 @@
         },
         "timeSkippingConfig": {
           "$ref": "#/definitions/v1TimeSkippingConfig",
-          "description": "Initial time-skipping configuration for the child workflow execution.\nThis field cannot be set explicitly; it is propagated from the parent workflow."
+          "description": "The propagated time-skipping config for the child workflow."
         }
       }
     },
@@ -17129,9 +17129,9 @@
           "type": "boolean",
           "description": "Enables or disables time skipping for this workflow execution."
         },
-        "disableChildWorkflowPropagation": {
-          "type": "boolean",
-          "description": "By default, the time skipping configuration (enabled and bound) is propagated to child workflows,\nusing the same values as the parent workflow.\nIf set, child workflows will be started with time skipping disabled.\nRegardless of this field, the start time of the child workflow uses the parent's virtual time."
+        "propagatedSkippedDuration": {
+          "type": "string",
+          "description": "If this execution was started by a previous execution that already skipped some time,\nit inherits the virtual time through the propagated skipped duration."
         },
         "maxSkippedDuration": {
           "type": "string",
@@ -17145,10 +17145,6 @@
           "type": "string",
           "format": "date-time",
           "description": "Absolute virtual timestamp at which time skipping is disabled.\nTime skipping will not advance beyond this point."
-        },
-        "propagatedSkippedDuration": {
-          "type": "string",
-          "description": "If this execution was started by a previous execution that already skipped some time,\nit inherits the virtual time through the propagated skipped duration."
         }
       },
       "description": "Configuration for time skipping during a workflow execution.\nWhen enabled, virtual time advances automatically whenever there is no in-flight work.\nIn-flight work includes activities, child workflows, Nexus operations, signal/cancel external workflow operations,\nand possibly other features added in the future.\nUser timers are not classified as in-flight work and will be skipped over.\nWhen time advances, it skips to the earlier of the next user timer or the configured bound, if either exists."

openapi/openapiv3.yaml

@@ -14549,9 +14549,7 @@ components:
         timeSkippingConfig:
           allOf:
             - $ref: '#/components/schemas/TimeSkippingConfig'
-          description: |-
-            Initial time-skipping configuration for the child workflow execution.
-             This field cannot be set explicitly; it is propagated from the parent workflow.
+          description: The propagated time-skipping config for the child workflow.
     StartWorkflowExecutionRequest:
       type: object
       properties:
@@ -15107,13 +15105,12 @@ components:
         enabled:
           type: boolean
           description: Enables or disables time skipping for this workflow execution.
-        disableChildWorkflowPropagation:
-          type: boolean
+        propagatedSkippedDuration:
+          pattern: ^-?(?:0|[1-9][0-9]{0,11})(?:\.[0-9]{1,9})?s$
+          type: string
           description: |-
-            By default, the time skipping configuration (enabled and bound) is propagated to child workflows,
-             using the same values as the parent workflow.
-             If set, child workflows will be started with time skipping disabled.
-             Regardless of this field, the start time of the child workflow uses the parent's virtual time.
+            If this execution was started by a previous execution that already skipped some time,
+             it inherits the virtual time through the propagated skipped duration.
         maxSkippedDuration:
           pattern: ^-?(?:0|[1-9][0-9]{0,11})(?:\.[0-9]{1,9})?s$
           type: string
@@ -15130,12 +15127,6 @@ components:
             Absolute virtual timestamp at which time skipping is disabled.
              Time skipping will not advance beyond this point.
           format: date-time
-        propagatedSkippedDuration:
-          pattern: ^-?(?:0|[1-9][0-9]{0,11})(?:\.[0-9]{1,9})?s$
-          type: string
-          description: |-
-            If this execution was started by a previous execution that already skipped some time,
-             it inherits the virtual time through the propagated skipped duration.
       description: |-
         Configuration for time skipping during a workflow execution.
          When enabled, virtual time advances automatically whenever there is no in-flight work.

temporal/api/history/v1/message.proto

@@ -771,8 +771,7 @@ message StartChildWorkflowExecutionInitiatedEventAttributes {
     // Priority metadata
     temporal.api.common.v1.Priority priority = 20;
 
-    // Initial time-skipping configuration for the child workflow execution.
-    // This field cannot be set explicitly; it is propagated from the parent workflow.
+    // The propagated time-skipping config for the child workflow.
     temporal.api.workflow.v1.TimeSkippingConfig time_skipping_config = 21;
 }
 

temporal/api/workflow/v1/message.proto

@@ -596,11 +596,9 @@ message TimeSkippingConfig {
     // Enables or disables time skipping for this workflow execution.
     bool enabled = 1;
 
-    // By default, the time skipping configuration (enabled and bound) is propagated to child workflows,
-    // using the same values as the parent workflow.
-    // If set, child workflows will be started with time skipping disabled.
-    // Regardless of this field, the start time of the child workflow uses the parent's virtual time.
-    bool disable_child_workflow_propagation = 3;
+    // If this execution was started by a previous execution that already skipped some time,
+    // it inherits the virtual time through the propagated skipped duration.
+    google.protobuf.Duration propagated_skipped_duration = 3;
 
     // Optional bound that limits how far virtual time can advance while time skipping is active.
     // Once the bound is reached, time skipping is automatically disabled,
@@ -628,11 +626,6 @@ message TimeSkippingConfig {
         // Time skipping will not advance beyond this point.
         google.protobuf.Timestamp max_target_time = 6;
     }
-
-    // If this execution was started by a previous execution that already skipped some time,
-    // it inherits the virtual time through the propagated skipped duration.
-    google.protobuf.Duration propagated_skipped_duration = 7;
-
 }
 
 // Used to override the versioning behavior (and pinned deployment version, if applicable) of a