Simplify proto comments, reference YAML for service definition

Author: rkannan82

temporal/api/worker/v1/worker_nexus_service_commands.proto

@@ -10,40 +10,19 @@ option ruby_package = "Temporalio::Api::Worker::V1";
 option csharp_namespace = "Temporalio.Api.Worker.V1";
 
 // (--
-/////////////////////////////////////////////////////////////////////
-// This file contains:
-// - Conventions between server and worker.
-// - Definitions for commands and payloads for server-worker communication via Nexus
-//
-// COMMUNICATION PROTOCOL:
-// - Transport: Nexus tasks on task queue
-// - Service name: "temporal.api.worker.v1.WorkerService"
-// - Task queue: /temporal-sys/worker-commands/{namespace}/{worker_grouping_key}
-//
-// WORKER COMMANDS CONVENTIONS:
-//
-// - Worker commands are used to manage worker configurations, operations, etc.
-// - Command names should match names defined in the server API.
-// - Command names are provided in StartOperationRequest.Operation field.
-//
-// PAYLOAD CONVENTIONS:
-//
-// - In/out payloads namings follow the same convention as the regular API:
-// - CommandNameRequest (input payload)
-// - CommandNameResponse (output payload).
-// - Empty payload if response is not needed/not expected
+// Internal Nexus service for server-to-worker communication.
+// See worker_service.nexusrpc.yaml for the service definition.
 //
+// Task queue format: /temporal-sys/worker-commands/{namespace}/{worker_grouping_key}
 // --)
 
 // Request payload for the "cancel-activities" Nexus operation.
 message CancelActivitiesRequest {
     // Task tokens identifying the activities to cancel.
-    // Each token corresponds to a specific activity task that the worker received.
     repeated bytes task_tokens = 1;
 }
 
 // Response payload for the "cancel-activities" Nexus operation.
 message CancelActivitiesResponse {
-    // Empty for now. Can be extended to include cancellation status per activity.
 }