@stigmer/protos 3.12.2 → 3.12.4

package/ai/stigmer/agentic/workflowexecution/v1/query_pb.d.ts

@@ -33,72 +33,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * - status: Current execution state (phase, tasks, progress_events, output/error)
      * - metadata: Resource identification (id, name, labels, tags)
      *
-     * @internal
-     * Authorization:
-     * Standard authorization checks that user has "get" permission on the WorkflowExecution.
-     * Permission is granted if:
-     * - User created the execution (metadata.audit.created_by matches user)
-     * - User has organization-level "workflow_execution:get" permission
-     * - User has explicit permission via IamPolicy
-     *
-     * Use Cases:
-     *
-     * 1. View Execution Details:
-     * - User clicks on an execution in the UI
-     * - UI calls get() to fetch full details
-     * - UI displays execution status, tasks, progress, output/error
-     *
-     * 2. Poll for Completion:
-     * - Client triggers execution via create()
-     * - Client periodically calls get() to check if phase is terminal
-     * - Client retrieves output when phase == EXECUTION_COMPLETED
-     *
-     * 3. Debug Failed Execution:
-     * - User sees execution failed
-     * - User calls get() to inspect status.error and status.tasks
-     * - User checks status.tasks[] for task-level execution details
-     *
-     * 4. Retry Failed Execution:
-     * - User calls get() to retrieve failed execution's spec
-     * - User creates new execution with same spec values
-     * - New execution retries with identical inputs
-     *
-     * Error Cases:
-     *
-     * - NOT_FOUND:
-     *   - No WorkflowExecution exists with the given ID
-     *
-     * - PERMISSION_DENIED:
-     *   - User doesn't have "get" permission on this WorkflowExecution
-     *   - WorkflowExecution belongs to different organization
-     *
-     * Example Request:
-     * {
-     *   "value": "wfx_abc123xyz456"
-     * }
-     *
-     * Example Response:
-     * {
-     *   "api_version": "agentic.stigmer.ai/v1",
-     *   "kind": "WorkflowExecution",
-     *   "metadata": {
-     *     "id": "wfx_abc123xyz456",
-     *     "name": "customer-onboarding-20250111-143022",
-     *     "org": "acme"
-     *   },
-     *   "spec": {
-     *     "workflow_instance_id": "wfi_customer-onboarding-prod",
-     *     "trigger_message": "New signup: john.doe@example.com"
-     *   },
-     *   "status": {
-     *     "phase": 2,  // EXECUTION_IN_PROGRESS
-     *     "total_tasks": 3,
-     *     "completed_tasks": 1,
-     *     "tasks": [ ... ],
-     *     "started_at": "2025-01-11T14:30:22Z"
-     *   }
-     * }
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.get
      */
     get: {
@@ -112,74 +46,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * Returns a paginated list of WorkflowExecution resources that the user has access to.
      * Results are automatically filtered based on user's permissions and owner scope.
      *
-     * @internal
-     * Authorization:
-     * Custom authorization filters results to only include executions the user can access:
-     * - Organization users: Only executions in their organization
-     * - Users with cross-org access: Public executions from other orgs
-     *
-     * Pagination:
-     * - page_size: Maximum number of results to return (default: 50, max: 100)
-     * - page_token: Opaque token from previous response for next page
-     * - Returns total_pages count for UI pagination
-     *
-     * Filtering:
-     * - phase: Filter by execution phase (PENDING, IN_PROGRESS, COMPLETED, FAILED, CANCELLED)
-     * - tags: Filter by resource tags (AND logic - must match all tags)
-     *
-     * Sorting:
-     * Results are sorted by created_at descending (newest first).
-     *
-     * Use Cases:
-     *
-     * 1. Execution History Dashboard:
-     * - UI displays list of all recent executions
-     * - User can filter by status (show only failed, show only in-progress)
-     * - User can page through historical executions
-     *
-     * 2. Monitor Active Executions:
-     * - UI calls list(phase=EXECUTION_IN_PROGRESS) to show running executions
-     * - UI displays progress for each execution (completed_tasks / total_tasks)
-     * - UI refreshes list periodically to show updates
-     *
-     * 3. Audit and Compliance:
-     * - Admin lists all executions for a time period
-     * - Admin filters by tags (environment, team, project)
-     * - Admin exports execution history for audit logs
-     *
-     * 4. Debug and Troubleshooting:
-     * - Developer lists failed executions (phase=EXECUTION_FAILED)
-     * - Developer inspects error messages and retry patterns
-     * - Developer identifies systematic failures
-     *
-     * Error Cases:
-     *
-     * - INVALID_ARGUMENT:
-     *   - page_size is negative or exceeds maximum
-     *   - Invalid page_token (expired, corrupted)
-     *
-     * Example Request (Filter for failed executions):
-     * {
-     *   "page_size": 20,
-     *   "phase": 4,  // EXECUTION_FAILED
-     *   "tags": ["environment:production"]
-     * }
-     *
-     * Example Response:
-     * {
-     *   "total_pages": 3,
-     *   "entries": [
-     *     {
-     *       "metadata": { "id": "wfx_failed-1", ... },
-     *       "status": { "phase": 4, "error": "Task failed: API timeout", ... }
-     *     },
-     *     {
-     *       "metadata": { "id": "wfx_failed-2", ... },
-     *       "status": { "phase": 4, "error": "Task failed: Rate limit", ... }
-     *     }
-     *   ]
-     * }
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.list
      */
     list: {
@@ -193,74 +59,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * Returns executions filtered by a specific Workflow ID.
      * This is useful for viewing execution history of a particular workflow.
      *
-     * @internal
-     * Authorization:
-     * Custom authorization verifies:
-     * 1. User has access to the referenced Workflow or WorkflowInstance
-     * 2. Results are filtered to only include executions user can access
-     *
-     * Pagination:
-     * - page_size: Maximum number of results to return (default: 50, max: 100)
-     * - page_token: Opaque token from previous response for next page
-     *
-     * Sorting:
-     * Results are sorted by created_at descending (newest first).
-     *
-     * Use Cases:
-     *
-     * 1. Workflow Execution History:
-     * - User views a Workflow in the UI
-     * - UI calls listByWorkflow(workflow_id) to show all executions
-     * - UI displays timeline of executions with success/failure indicators
-     *
-     * 2. Performance Analysis:
-     * - Developer wants to analyze workflow performance over time
-     * - Developer calls listByWorkflow() to get all executions
-     * - Developer calculates average duration, success rate, failure patterns
-     *
-     * 3. Retry Analysis:
-     * - User sees failed execution
-     * - User calls listByWorkflow() to see if other executions also failed
-     * - User determines if failure is systematic or one-off
-     *
-     * 4. Workflow Testing:
-     * - Developer tests a workflow with multiple executions
-     * - Developer calls listByWorkflow() to see all test runs
-     * - Developer compares outputs across executions
-     *
-     * Error Cases:
-     *
-     * - INVALID_ARGUMENT:
-     *   - workflow_id is empty or invalid format
-     *   - page_size is negative or exceeds maximum
-     *
-     * - PERMISSION_DENIED:
-     *   - User doesn't have access to the referenced Workflow/WorkflowInstance
-     *
-     * - NOT_FOUND:
-     *   - No Workflow or WorkflowInstance exists with the given ID
-     *
-     * Example Request:
-     * {
-     *   "workflow_id": "wfi_customer-onboarding-prod",
-     *   "page_size": 50
-     * }
-     *
-     * Example Response:
-     * {
-     *   "total_pages": 5,
-     *   "entries": [
-     *     {
-     *       "metadata": { "id": "wfx_latest", "created_at": "2025-01-11T14:30:22Z" },
-     *       "status": { "phase": 3, ... }  // COMPLETED
-     *     },
-     *     {
-     *       "metadata": { "id": "wfx_previous", "created_at": "2025-01-11T10:15:00Z" },
-     *       "status": { "phase": 4, ... }  // FAILED
-     *     }
-     *   ]
-     * }
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.listByWorkflow
      */
     listByWorkflow: {
@@ -278,114 +76,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * - Progress events are appended
      * - Output or error fields are set
      *
-     * @internal
-     * Authorization:
-     * Standard authorization checks that user has "get" permission on the WorkflowExecution.
-     * This is the same permission check as get() RPC.
-     *
-     * Stream Lifecycle:
-     * 1. Client sends SubscribeWorkflowExecutionRequest with execution_id
-     * 2. Server validates authorization
-     * 3. Server sends initial WorkflowExecution (current state)
-     * 4. Server streams updates as execution progresses
-     * 5. Server closes stream when execution reaches terminal state (COMPLETED/FAILED/CANCELLED)
-     * 6. Client can close stream early (e.g., user navigates away from page)
-     *
-     * Update Frequency:
-     * - Updates are sent immediately when execution state changes
-     * - No polling necessary (server pushes updates)
-     * - Typical update latency: < 100ms
-     *
-     * Use Cases:
-     *
-     * 1. Real-Time Progress Monitoring:
-     * - User triggers an execution from UI
-     * - UI subscribes to execution updates
-     * - UI displays live progress: tasks completing, progress bar updating
-     * - UI shows final output when execution completes
-     *
-     * 2. Long-Running Workflow Monitoring:
-     * - Workflow takes hours to complete (e.g., data processing)
-     * - UI subscribes and shows live progress
-     * - User can leave page, come back, and reconnect to same execution
-     *
-     * 3. Debugging with Live Updates:
-     * - Developer triggers test execution
-     * - Developer subscribes to watch execution progress
-     * - Developer sees exactly which task is running and when failures occur
-     *
-     * 4. Multi-User Collaboration:
-     * - Multiple users watching same execution
-     * - All users receive same updates simultaneously
-     * - All users see consistent view of execution state
-     *
-     * Stream Message Format:
-     * Each message is a complete WorkflowExecution resource with updated status.
-     *
-     * Error Cases:
-     *
-     * - NOT_FOUND:
-     *   - No WorkflowExecution exists with the given ID
-     *
-     * - PERMISSION_DENIED:
-     *   - User doesn't have "get" permission on this WorkflowExecution
-     *
-     * - DEADLINE_EXCEEDED:
-     *   - Client timeout (client should reconnect)
-     *
-     * - UNAVAILABLE:
-     *   - Server unavailable (client should retry with backoff)
-     *
-     * Example Request:
-     * {
-     *   "execution_id": "wfx_abc123xyz456"
-     * }
-     *
-     * Example Stream (sequence of messages):
-     *
-     * Message 1 (initial state):
-     * {
-     *   "metadata": { "id": "wfx_abc123xyz456" },
-     *   "status": {
-     *     "phase": 1,  // EXECUTION_PENDING
-     *     "total_tasks": 3,
-     *     "completed_tasks": 0
-     *   }
-     * }
-     *
-     * Message 2 (execution started):
-     * {
-     *   "metadata": { "id": "wfx_abc123xyz456" },
-     *   "status": {
-     *     "phase": 2,  // EXECUTION_IN_PROGRESS
-     *     "started_at": "2025-01-11T14:30:22Z"
-     *   }
-     * }
-     *
-     * Message 3 (task 1 completed):
-     * {
-     *   "metadata": { "id": "wfx_abc123xyz456" },
-     *   "status": {
-     *     "phase": 2,  // EXECUTION_IN_PROGRESS
-     *     "completed_tasks": 1,
-     *     "tasks": [
-     *       { "task_id": "task-1", "status": 3, "output": { ... } }
-     *     ]
-     *   }
-     * }
-     *
-     * Message 4 (execution completed):
-     * {
-     *   "metadata": { "id": "wfx_abc123xyz456" },
-     *   "status": {
-     *     "phase": 3,  // EXECUTION_COMPLETED
-     *     "completed_tasks": 3,
-     *     "output": { ... },
-     *     "completed_at": "2025-01-11T14:35:47Z"
-     *   }
-     * }
-     * [Stream closes]
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.subscribe
      */
     subscribe: {
@@ -399,40 +89,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * Returns execution events ordered by sequence_number ascending, with
      * cursor-based pagination and optional filtering by event type or task name.
      *
-     * @internal
-     * Authorization:
-     * Standard authorization checks that user has "get" permission on the
-     * WorkflowExecution. Same permission as get() and subscribe().
-     *
-     * The event log complements the status snapshot: the snapshot tells you
-     * current state, the event log tells you what happened and when.
-     *
-     * Use Cases:
-     *
-     * 1. Execution Viewer Timeline:
-     *    - Load full event history for a completed execution
-     *    - Render timeline with task transitions, retries, approvals, cost
-     *
-     * 2. Task Drill-Down:
-     *    - Filter by task_name to see all events for a specific task
-     *    - Inspect retry history, duration, cost per attempt
-     *
-     * 3. Cost Audit:
-     *    - Filter by budget_checkpoint events to chart cost over time
-     *    - Correlate cost spikes with specific agent_call tasks
-     *
-     * 4. Approval Audit Trail:
-     *    - Filter by approval_requested and approval_resolved
-     *    - See who approved what, when, and with what comment
-     *
-     * Error Cases:
-     *
-     * - NOT_FOUND: No WorkflowExecution exists with the given ID
-     * - PERMISSION_DENIED: User doesn't have "get" permission
-     * - INVALID_ARGUMENT: page_size exceeds maximum (500)
-     *
-     * @since T06 (Execution Event Stream Model)
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.getEventLog
      */
     getEventLog: {
@@ -448,55 +104,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * Unlike subscribe() which streams full WorkflowExecution snapshots,
      * this streams lightweight incremental events for the timeline view.
      *
-     * @internal
-     * Authorization:
-     * Standard authorization checks that user has "get" permission on the
-     * WorkflowExecution. Same permission as get() and subscribe().
-     *
-     * Stream Lifecycle:
-     * 1. Client sends SubscribeEventsRequest with execution_id
-     * 2. Server validates authorization
-     * 3. If after_sequence > 0: Server replays missed events from persistence
-     * 4. Server streams new events in real-time as the runner emits them
-     * 5. Server closes stream when execution reaches a terminal phase
-     *    (COMPLETED, FAILED, CANCELLED, TERMINATED)
-     * 6. Client can close stream early
-     *
-     * Reconnection:
-     * On disconnect, the client reconnects with after_sequence set to the
-     * sequence_number of the last received event. The server replays any
-     * events missed during the disconnect, then resumes live streaming.
-     * No events are lost.
-     *
-     * Complementary Streams:
-     * - subscribe(): Full snapshots for current-state views (progress bars, dashboards)
-     * - subscribeEvents(): Incremental events for timeline views (execution viewer)
-     * Both streams can be used simultaneously for different UI concerns.
-     *
-     * Use Cases:
-     *
-     * 1. Live Execution Timeline:
-     *    - User watches a running execution in the execution viewer
-     *    - Events stream in real-time, building the timeline as tasks progress
-     *    - Each event adds a row: "task X started", "task X completed (2.3s, $0.05)"
-     *
-     * 2. Cost Monitoring:
-     *    - Dashboard subscribes with event_types filter for budget_checkpoint
-     *    - Budget gauge updates in real-time as costs accumulate
-     *
-     * 3. Approval Notifications:
-     *    - Subscribe with event_types filter for approval_requested
-     *    - Surface approval gates immediately when they activate
-     *
-     * Error Cases:
-     *
-     * - NOT_FOUND: No WorkflowExecution exists with the given ID
-     * - PERMISSION_DENIED: User doesn't have "get" permission
-     * - DEADLINE_EXCEEDED: Client timeout (reconnect with after_sequence)
-     * - UNAVAILABLE: Server unavailable (retry with backoff)
-     *
-     * @since T06 (Execution Event Stream Model)
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.subscribeEvents
      */
     subscribeEvents: {
@@ -511,27 +118,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * workflows, and per-workflow cost breakdown — scoped to a configurable
      * time window (24h, 7d, 30d, all-time).
      *
-     * @internal
-     * Authorization:
-     * Custom authorization — user must have organization-level access.
-     * Results are scoped to the user's organization.
-     *
-     * Use Cases:
-     *
-     * 1. Dashboard Overview:
-     *    - Display KPI cards: active runs, completed, failed, total cost
-     *    - Time window selector toggles between 24h / 7d / 30d views
-     *
-     * 2. Cost Monitoring:
-     *    - Show per-workflow cost breakdown to identify expensive workflows
-     *    - Track cost trends across time windows
-     *
-     * 3. Reliability Monitoring:
-     *    - Surface top failing workflows for investigation
-     *    - Track failure rates across the organization
-     *
-     * @since T14 (Dashboard Integration)
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.getExecutionSummary
      */
     getExecutionSummary: {
@@ -546,24 +132,6 @@ export declare const WorkflowExecutionQueryController: GenService<{
      * task is actively waiting for a response. Each entry includes the
      * execution context, task details, requester, and timeout information.
      *
-     * @internal
-     * Authorization:
-     * Custom authorization — user must have organization-level access.
-     * Results are scoped to the user's organization.
-     *
-     * Use Cases:
-     *
-     * 1. Pending Approvals Dashboard Widget:
-     *    - Display a list of items requiring human attention
-     *    - Show time waiting and timeout countdown
-     *    - Link to execution viewer for review action
-     *
-     * 2. Approval Queue:
-     *    - Reviewers see all pending approvals in one view
-     *    - Sorted by urgency (closest to timeout first)
-     *
-     * @since T14 (Dashboard Integration)
-     *
      * @generated from rpc ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionQueryController.listPendingApprovals
      */
     listPendingApprovals: {

package/ai/stigmer/agentic/workflowexecution/v1/query_pb.js.map

@@ -1 +1 @@
-{"version":3,"file":"query_pb.js","sourceRoot":"","sources":["../../../../../../ai/stigmer/agentic/workflowexecution/v1/query_pb.ts"],"names":[],"mappings":"AAAA,oFAAoF;AACpF,4IAA4I;AAC5I,oBAAoB;AAGpB,OAAO,EAAE,QAAQ,EAAE,WAAW,EAAE,MAAM,8BAA8B,CAAC;AAErE,OAAO,EAAE,gDAAgD,EAAE,MAAM,aAAa,CAAC;AAE/E,OAAO,EAAE,kDAAkD,EAAE,MAAM,eAAe,CAAC;AAEnF,OAAO,EAAE,+CAA+C,EAAE,MAAM,YAAY,CAAC;AAC7E,OAAO,EAAE,uDAAuD,EAAE,MAAM,wDAAwD,CAAC;AACjI,OAAO,EAAE,0CAA0C,EAAE,MAAM,2CAA2C,CAAC;AAEvG;;GAEG;AACH,MAAM,CAAC,MAAM,kDAAkD,GAAY,aAAa,CACtF,QAAQ,CAAC,kpEAAkpE,EAAE,CAAC,gDAAgD,EAAE,kDAAkD,EAAE,+CAA+C,EAAE,uDAAuD,EAAE,0CAA0C,CAAC,CAAC,CAAC;AAE75E;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,gCAAgC,GAmiBxC,aAAa,CAChB,WAAW,CAAC,kDAAkD,EAAE,CAAC,CAAC,CAAC"}
+{"version":3,"file":"query_pb.js","sourceRoot":"","sources":["../../../../../../ai/stigmer/agentic/workflowexecution/v1/query_pb.ts"],"names":[],"mappings":"AAAA,oFAAoF;AACpF,4IAA4I;AAC5I,oBAAoB;AAGpB,OAAO,EAAE,QAAQ,EAAE,WAAW,EAAE,MAAM,8BAA8B,CAAC;AAErE,OAAO,EAAE,gDAAgD,EAAE,MAAM,aAAa,CAAC;AAE/E,OAAO,EAAE,kDAAkD,EAAE,MAAM,eAAe,CAAC;AAEnF,OAAO,EAAE,+CAA+C,EAAE,MAAM,YAAY,CAAC;AAC7E,OAAO,EAAE,uDAAuD,EAAE,MAAM,wDAAwD,CAAC;AACjI,OAAO,EAAE,0CAA0C,EAAE,MAAM,2CAA2C,CAAC;AAEvG;;GAEG;AACH,MAAM,CAAC,MAAM,kDAAkD,GAAY,aAAa,CACtF,QAAQ,CAAC,kpEAAkpE,EAAE,CAAC,gDAAgD,EAAE,kDAAkD,EAAE,+CAA+C,EAAE,uDAAuD,EAAE,0CAA0C,CAAC,CAAC,CAAC;AAE75E;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,gCAAgC,GAmHxC,aAAa,CAChB,WAAW,CAAC,kDAAkD,EAAE,CAAC,CAAC,CAAC"}

package/ai/stigmer/agentic/workflowexecution/v1/spec_pb.d.ts

@@ -9,94 +9,30 @@ export declare const file_ai_stigmer_agentic_workflowexecution_v1_spec: GenFile;
 /**
  * WorkflowExecutionSpec defines the user-provided inputs for a workflow execution.
  *
- * @internal
- * This is the "Execution" layer in the Template→Instance→Execution pattern.
- * WorkflowExecutionSpec is ephemeral - it defines the inputs for a single runtime invocation.
- * The spec is immutable after creation. To retry with different inputs, create a new
- * WorkflowExecution with updated spec values.
- *
- * Instance Resolution (matches AgentExecution pattern):
- * - Either workflow_instance_id OR workflow_id must be provided
- * - If workflow_instance_id: Use the specified instance directly
- * - If workflow_id: Resolve to workflow's default instance (auto-create if missing)
- * - Handler enforces: at least one must be provided
- *
  * @generated from message ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionSpec
  */
 export type WorkflowExecutionSpec = Message<"ai.stigmer.agentic.workflowexecution.v1.WorkflowExecutionSpec"> & {
     /**
      * ID of the WorkflowInstance to execute.
      *
-     * @internal
-     * Either workflow_instance_id OR workflow_id must be provided.
-     * Handler enforces this validation.
-     *
-     * The WorkflowInstance contains:
-     * - Reference to the Workflow template (orchestration definition)
-     * - Environment bindings (configuration and secrets)
-     * - Default configuration values
-     *
-     * Format: "wfi-{slug}" (e.g., "wfi-customer-onboarding-prod")
-     *
-     * Authorization:
-     * User must have "execute" permission on the referenced WorkflowInstance.
-     *
      * @generated from field: string workflow_instance_id = 1;
      */
     workflowInstanceId: string;
     /**
      * ID of the Workflow template to execute (alternative to workflow_instance_id).
      *
-     * @internal
-     * When workflow_id is provided without workflow_instance_id, the system:
-     * 1. Checks if the Workflow has a default_instance_id in its status
-     * 2. If exists: Uses the default instance
-     * 3. If missing: Auto-creates a default instance (name: "{workflow_slug}-default")
-     * 4. Updates the Workflow status with the default_instance_id
-     * 5. Executes using the resolved instance
-     *
-     * Format: "wf-{slug}" (e.g., "wf-customer-onboarding")
-     *
-     * Either workflow_instance_id OR workflow_id must be provided.
-     * Handler enforces this validation.
-     *
-     * Authorization:
-     * User must have "execute" permission on the resolved WorkflowInstance.
-     *
      * @generated from field: string workflow_id = 6;
      */
     workflowId: string;
     /**
      * Input message or payload that triggers the workflow.
      *
-     * @internal
-     * This is the primary input to the workflow - the "trigger event" or "request payload".
-     * It can be a human-readable message, a JSON payload, or an event description.
-     *
-     * The workflow can access this value using: {{workflow.input.trigger_message}}
-     * Tasks can reference it in their input configurations.
-     *
-     * The trigger_message is optional - some workflows don't need input (scheduled jobs,
-     * workflows that fetch data from APIs, etc.).
-     *
      * @generated from field: string trigger_message = 3;
      */
     triggerMessage: string;
     /**
      * Contextual metadata about what triggered this execution.
      *
-     * @internal
-     * This metadata is NOT used by the workflow logic itself - it's for audit, debugging,
-     * and analytics.
-     *
-     * Common metadata keys:
-     * - "source": How was this triggered? (api, webhook, schedule, manual, ui)
-     * - "caller_id": Who triggered it? (usr-abc123, sys-scheduler, webhook-stripe)
-     * - "ip_address": Client IP address (for API/UI triggers)
-     * - "webhook_id": Webhook ID (for webhook triggers)
-     * - "schedule_id": Schedule ID (for scheduled triggers)
-     * - "timestamp": When was it triggered? (ISO 8601)
-     *
      * @generated from field: map<string, string> trigger_metadata = 4;
      */
     triggerMetadata: {
@@ -110,27 +46,6 @@ export type WorkflowExecutionSpec = Message<"ai.stigmer.agentic.workflowexecutio
      * a declaration whitelist (name + is_secret + optional), never a value source
      * — undeclared keys are dropped.
      *
-     * @internal
-     * Merge priority (lowest to highest):
-     * 1. Environment values (resolved from WorkflowInstance.environment_refs, in
-     *    order; a later ref wins on key conflicts)
-     * 2. runtime_env (this field)
-     *
-     * The merged map is then filtered to the keys declared in Workflow.spec.env
-     * (no filtering when the workflow declares none); a declared-but-required key
-     * that is still missing only logs a warning — the run is not failed. The
-     * merge is owned by backend/libs/go/envmerge and the workflowexecution
-     * controller's createExecutionContextStep, and asserted by
-     * test/conformance/src/suites-execution/envmerge.conformance.test.ts.
-     *
-     * Security:
-     * - runtime_env values are consumed into the ExecutionContext at create time
-     *   and cleared from the persisted execution (never in Temporal history)
-     * - ExecutionContext is deleted when execution completes (ephemeral secrets)
-     * - Values with is_secret=true are encrypted at rest and redacted in logs
-     *
-     * Tasks can access these values using: {{env.VARIABLE_NAME}}
-     *
      * @generated from field: map<string, ai.stigmer.agentic.executioncontext.v1.ExecutionValue> runtime_env = 5;
      */
     runtimeEnv: {
@@ -139,52 +54,12 @@ export type WorkflowExecutionSpec = Message<"ai.stigmer.agentic.workflowexecutio
     /**
      * Opaque callback token for asynchronous completion by a parent orchestrator.
      *
-     * @internal
-     * Enables async completion pattern where the caller (typically a parent workflow)
-     * waits for actual workflow completion without blocking worker threads.
-     *
-     * Flow:
-     * 1. Caller (Temporal activity) extracts its task token
-     * 2. Passes token in this field when creating WorkflowExecution
-     * 3. Returns activity.ErrResultPending (activity paused, thread released)
-     * 4. Workflow executes (minutes/hours later)
-     * 5. Workflow calls ActivityCompletionClient.complete(token, result)
-     * 6. Temporal resumes the paused activity with the result
-     *
-     * When empty: fire-and-forget or direct API call (backward compatible).
-     * When provided: workflow MUST complete the external activity using this token.
-     *
-     * Token format: opaque binary blob from Temporal SDK (typically 100-200 bytes).
-     * DO NOT parse or modify - treat as opaque handle.
-     *
-     * Same pattern as AgentExecution.spec.callback_token.
-     *
-     * References:
-     * - ADR: docs/adr/20260122-async-agent-execution-temporal-token-handshake.md
-     * - Temporal Docs: https://docs.temporal.io/activities#asynchronous-activity-completion
-     *
-     * @since 2026-01-22
-     *
      * @generated from field: bytes callback_token = 7;
      */
     callbackToken: Uint8Array;
     /**
      * Where workflow activities are executed — shared runner pool or dedicated sandbox.
      *
-     * @internal
-     * Determines dispatch routing for the workflow and all child executions:
-     * - UNSPECIFIED: server defaults (LOCAL for OSS, CLOUD for managed)
-     * - LOCAL: workflow runs on global queue (stigmer_runner)
-     * - CLOUD: server provisions a dedicated sandbox with per-execution queue
-     *
-     * When CLOUD: all call:agent tasks within this workflow share the same sandbox.
-     * Child agent executions inherit this sandbox via activity_task_queue propagation
-     * on AgentExecutionSpec, avoiding N separate sandbox cold starts.
-     *
-     * Immutable after creation (sandbox provisioning is a one-time operation).
-     *
-     * @since Workflow Sandbox Affinity
-     *
      * @generated from field: ai.stigmer.agentic.session.v1.ExecutionTarget execution_target = 8;
      */
     executionTarget: ExecutionTarget;

package/ai/stigmer/agentic/workflowexecution/v1/spec_pb.js.map

@@ -1 +1 @@
-{"version":3,"file":"spec_pb.js","sourceRoot":"","sources":["../../../../../../ai/stigmer/agentic/workflowexecution/v1/spec_pb.ts"],"names":[],"mappings":"AAAA,oFAAoF;AACpF,2IAA2I;AAC3I,oBAAoB;AAGpB,OAAO,EAAE,QAAQ,EAAE,WAAW,EAAE,MAAM,8BAA8B,CAAC;AAErE,OAAO,EAAE,gDAAgD,EAAE,MAAM,sCAAsC,CAAC;AAExG,OAAO,EAAE,uCAAuC,EAAE,MAAM,6BAA6B,CAAC;AAGtF;;GAEG;AACH,MAAM,CAAC,MAAM,iDAAiD,GAAY,aAAa,CACrF,QAAQ,CAAC,w4BAAw4B,EAAE,CAAC,gDAAgD,EAAE,uCAAuC,CAAC,CAAC,CAAC;AA4Ll/B;;;GAGG;AACH,MAAM,CAAC,MAAM,2BAA2B,GAAsC,aAAa,CACzF,WAAW,CAAC,iDAAiD,EAAE,CAAC,CAAC,CAAC"}
+{"version":3,"file":"spec_pb.js","sourceRoot":"","sources":["../../../../../../ai/stigmer/agentic/workflowexecution/v1/spec_pb.ts"],"names":[],"mappings":"AAAA,oFAAoF;AACpF,2IAA2I;AAC3I,oBAAoB;AAGpB,OAAO,EAAE,QAAQ,EAAE,WAAW,EAAE,MAAM,8BAA8B,CAAC;AAErE,OAAO,EAAE,gDAAgD,EAAE,MAAM,sCAAsC,CAAC;AAExG,OAAO,EAAE,uCAAuC,EAAE,MAAM,6BAA6B,CAAC;AAGtF;;GAEG;AACH,MAAM,CAAC,MAAM,iDAAiD,GAAY,aAAa,CACrF,QAAQ,CAAC,w4BAAw4B,EAAE,CAAC,gDAAgD,EAAE,uCAAuC,CAAC,CAAC,CAAC;AA+Dl/B;;;GAGG;AACH,MAAM,CAAC,MAAM,2BAA2B,GAAsC,aAAa,CACzF,WAAW,CAAC,iDAAiD,EAAE,CAAC,CAAC,CAAC"}