fix: update message name and comments

Author: chene40

openapi/openapiv2.json

@@ -10054,7 +10054,7 @@
         }
       }
     },
-    "v1ActionsMetering": {
+    "v1ActionMetadata": {
       "type": "object",
       "properties": {
         "actions": {
@@ -10063,7 +10063,7 @@
             "type": "object",
             "$ref": "#/definitions/v1Action"
           },
-          "description": "A history event can be attributed to multiple metering subtypes\nEx: EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED is used for both\ngrpc:SignalWorkflowExecution and grpc:SignalWithStartWorkflowExecution subtypes."
+          "title": "A history event can be attributed to multiple metering subtypes\nEx. EVENT_TYPE_WORKFLOW_EXECUTION_STARTED, which is used by both Start\nWorkflow Execution and Scheduled Workflow Executions.\ngrpc:StartWorkflowExecution and grpc:StartWorkflowExecution.Scheduled.Adjusted"
         }
       }
     },
@@ -12484,7 +12484,7 @@
           "description": "Links associated with the event."
         },
         "actionMetadata": {
-          "$ref": "#/definitions/v1ActionsMetering",
+          "$ref": "#/definitions/v1ActionMetadata",
           "description": "Actions metering metadata for the event."
         },
         "workflowExecutionStartedEventAttributes": {

openapi/openapiv3.yaml

@@ -7243,7 +7243,7 @@ components:
         actionCount:
           type: integer
           format: int32
-    ActionsMetering:
+    ActionMetadata:
       type: object
       properties:
         actions:
@@ -7252,8 +7252,9 @@ components:
             $ref: '#/components/schemas/Action'
           description: |-
             A history event can be attributed to multiple metering subtypes
-             Ex: EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED is used for both
-             grpc:SignalWorkflowExecution and grpc:SignalWithStartWorkflowExecution subtypes.
+             Ex. EVENT_TYPE_WORKFLOW_EXECUTION_STARTED, which is used by both Start
+             Workflow Execution and Scheduled Workflow Executions.
+             grpc:StartWorkflowExecution and grpc:StartWorkflowExecution.Scheduled.Adjusted
     ActivityExecutionInfo:
       type: object
       properties:
@@ -9726,7 +9727,7 @@ components:
           description: Links associated with the event.
         actionMetadata:
           allOf:
-            - $ref: '#/components/schemas/ActionsMetering'
+            - $ref: '#/components/schemas/ActionMetadata'
           description: Actions metering metadata for the event.
         workflowExecutionStartedEventAttributes:
           $ref: '#/components/schemas/WorkflowExecutionStartedEventAttributes'

temporal/api/history/v1/message.proto

@@ -1116,7 +1116,7 @@ message HistoryEvent {
     // Links associated with the event.
     repeated temporal.api.common.v1.Link links = 302;
     // Actions metering metadata for the event.
-    temporal.api.server.v1.ActionsMetering action_metadata = 303;
+    temporal.api.server.v1.ActionMetadata action_metadata = 303;
 
     oneof attributes {
         WorkflowExecutionStartedEventAttributes workflow_execution_started_event_attributes = 6;

temporal/api/server/v1/message.proto

@@ -7,10 +7,11 @@ option java_package = "io.temporal.api.server.v1";
 option java_outer_classname = "MessageProto";
 option java_multiple_files = true;
 
-message ActionsMetering {
+message ActionMetadata {
     // A history event can be attributed to multiple metering subtypes
-    // Ex: EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED is used for both
-    // grpc:SignalWorkflowExecution and grpc:SignalWithStartWorkflowExecution subtypes.
+    // Ex. EVENT_TYPE_WORKFLOW_EXECUTION_STARTED, which is used by both Start
+    // Workflow Execution and Scheduled Workflow Executions.
+    // grpc:StartWorkflowExecution and grpc:StartWorkflowExecution.Scheduled.Adjusted
     repeated Action actions = 1;
 }