refine design of TimeSkippingConfig

Author: feiyang3cat

temporal/api/workflow/v1/message.proto

@@ -594,32 +594,28 @@ message TimeSkippingConfig {
     // Enables or disables time skipping for this workflow execution.
     bool enabled = 1;
 
-    // By default, the time skipping configuration is propagated to transitively related workflows.
-    // If set, transitively related workflows will be started with time skipping disabled.
-    bool disable_propagation = 2;
+    reserved 2;
+    reserved "disable_propagation";
+
+    // By default, the time skipping configuration (enabled and bound) is propagated to child workflows
+    // with the same value 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;
 
     // Optional bound that limits how long time skipping remains active.
     // Once the bound is reached, time skipping is automatically disabled.
     // It can later be re-enabled via UpdateWorkflowExecutionOptions.
     //
-    // This is particularly useful in testing scenarios where workflows
+    // This is useful in testing scenarios where workflows
     // are expected to receive signals, updates, or other events while
     // timers are in progress.
     //
-    // The bound is propagated to transitively related workflows differently
-    // depending on the type and semantics of the related workflow:
-    // - Child workflows: the bound is propagated with the same value as the
-    //   parent workflow, and the child begins execution at the parent's virtual
-    //   time. If the bound is duration-based, each child calculates its skipped
-    //   duration independently from its own start.
-    //
-    // - Continue-as-new workflows: the bound is propagated with the same value
-    //   as the previous workflow. If the bound is duration-based, the
-    //   continue-as-new workflow shares the accumulated duration with the
-    //   previous workflow.
-    //
-    // - Reset workflows: the entire TimeSkippingConfig is restored to the value
-    //   it had at the event this workflow was reset to.
+    // The bound usually manages the lifecycle of one workflow execution, 
+    // for example: the bound of parent workflow only affects the parent workflow itself,
+    // and if propagated to child workflow, the bound of child workflow only affects the child workflow itself.
+    // But for continue-as-new workflows, they are treated combined as one workflow execution,
+    // so the bound of continue-as-new workflow affects the all of the workflow executions.
     oneof bound {
 
         // Maximum total virtual time that can be skipped.