examples: replace --format with --output

Author: moedash

examples/EXPERIMENT.md

@@ -179,11 +179,11 @@ Based on experiment findings, the following improvements were made:
 
 | Feature | Status | Flag/Command |
 |---------|--------|--------------|
-| Trace flowchart | ✅ Done | `temporal workflow describe --trace-root-cause --format mermaid` |
-| Timeline sequence diagram | ✅ Done | `temporal workflow show --compact --format mermaid` |
-| State diagram | ✅ Done | `temporal workflow describe --pending --format mermaid` |
-| Failures pie chart | ✅ Done | `temporal workflow list --failed --group-by error --format mermaid` |
-| Failures flowchart | ✅ Done | `temporal workflow list --failed --format mermaid` |
+| Trace flowchart | ✅ Done | `temporal workflow describe --trace-root-cause --output mermaid` |
+| Timeline sequence diagram | ✅ Done | `temporal workflow show --compact --output mermaid` |
+| State diagram | ✅ Done | `temporal workflow describe --pending --output mermaid` |
+| Failures pie chart | ✅ Done | `temporal workflow list --failed --group-by error --output mermaid` |
+| Failures flowchart | ✅ Done | `temporal workflow list --failed --output mermaid` |
 
 ---
 
@@ -226,6 +226,6 @@ The `temporal workflow` CLI commands successfully achieve the goals:
 6. **Timing analysis**: Timeline timestamps enable race condition diagnosis
 7. **Low token cost**: Structured JSON is ~10x more efficient than raw logs
 8. **Autonomous debugging**: LLM successfully diagnosed and fixed a TOCTOU bug without hints
-9. **Mermaid visualization**: `--format mermaid` generates visual diagrams for human-in-the-loop debugging
+9. **Mermaid visualization**: `--output mermaid` generates visual diagrams for human-in-the-loop debugging
 
 **Temporal's execution history + agent-optimized CLI = effective AI debugging feedback loop.**

examples/agent-demo/README.md

@@ -94,7 +94,7 @@ temporal workflow list --failed \
     --tls \
     --since 1h \
     --follow-children \
-    --format json | jq
+    --output json | jq
 ```
 
 ### Trace a Workflow Chain
@@ -107,7 +107,7 @@ temporal workflow describe --trace-root-cause \
     --api-key $TEMPORAL_API_KEY \
     --tls \
     -w order-payment-fail-XXXXXX \
-    --format json | jq
+    --output json | jq
 
 # Trace the nested failure workflow (3 levels deep)
 temporal workflow describe --trace-root-cause \
@@ -116,7 +116,7 @@ temporal workflow describe --trace-root-cause \
     --api-key $TEMPORAL_API_KEY \
     --tls \
     -w nested-failure-XXXXXX \
-    --format json | jq
+    --output json | jq
 ```
 
 ### Get Workflow Timeline
@@ -129,7 +129,7 @@ temporal workflow show --compact \
     --tls \
     -w order-success-XXXXXX \
     --compact \
-    --format json | jq
+    --output json | jq
 ```
 
 ## Workflow Scenarios

examples/agent-demo/starter/main.go

@@ -248,7 +248,7 @@ func runLongRunningScenario(ctx context.Context, c client.Client, taskQueue, tim
 	}
 	log.Printf("Started LongRunningWorkflow: %s", run.GetID())
 	log.Println("TIP: While running, query its state with:")
-	log.Printf("  temporal workflow describe --pending --workflow-id %s --namespace <your-namespace> --format json", workflowID)
+	log.Printf("  temporal workflow describe --pending --workflow-id %s --namespace <your-namespace> --output json", workflowID)
 }
 
 func runDeepChainScenario(ctx context.Context, c client.Client, taskQueue, timestamp string) {
@@ -266,5 +266,5 @@ func runDeepChainScenario(ctx context.Context, c client.Client, taskQueue, times
 	}
 	log.Printf("Started DeepChainWorkflow (4 levels deep, fails with DB error): %s", run.GetID())
 	log.Println("TIP: Trace the full chain with:")
-	log.Printf("  temporal workflow describe --trace-root-cause --workflow-id %s --namespace <your-namespace> --format json", workflowID)
+	log.Printf("  temporal workflow describe --trace-root-cause --workflow-id %s --namespace <your-namespace> --output json", workflowID)
 }

examples/ai-research-agent-impl/CLAUDE.md

@@ -6,28 +6,28 @@ When debugging Temporal workflows, use the `temporal workflow` CLI commands inst
 
 ### Find Failures
 ```bash
-temporal workflow list --failed --since 1h --format json
-temporal workflow list --failed --since 1h --follow-children --leaf-only --compact-errors --format json
-temporal workflow list --failed --since 1h --group-by error --format json
+temporal workflow list --failed --since 1h --output json
+temporal workflow list --failed --since 1h --follow-children --leaf-only --compact-errors --output json
+temporal workflow list --failed --since 1h --group-by error --output json
 ```
 
 ### Trace Workflow Chain
 ```bash
-temporal workflow describe --trace-root-cause --workflow-id <id> --format json
-temporal workflow describe --trace-root-cause --workflow-id <id> --format mermaid
+temporal workflow describe --trace-root-cause --workflow-id <id> --output json
+temporal workflow describe --trace-root-cause --workflow-id <id> --output mermaid
 ```
 
 ### Get Timeline
 ```bash
-temporal workflow show --compact --workflow-id <id> --format json
-temporal workflow show --compact --workflow-id <id> --compact --format json
-temporal workflow show --compact --workflow-id <id> --format mermaid
+temporal workflow show --compact --workflow-id <id> --output json
+temporal workflow show --compact --workflow-id <id> --compact --output json
+temporal workflow show --compact --workflow-id <id> --output mermaid
 ```
 
 ### Check State
 ```bash
-temporal workflow describe --pending --workflow-id <id> --format json
-temporal workflow describe --pending --workflow-id <id> --format mermaid
+temporal workflow describe --pending --workflow-id <id> --output json
+temporal workflow describe --pending --workflow-id <id> --output mermaid
 ```
 
 ## Key Flags
@@ -36,21 +36,21 @@ temporal workflow describe --pending --workflow-id <id> --format mermaid
 - `--leaf-only` - Show only leaf failures (de-duplicate chains)
 - `--compact-errors` - Strip wrapper context, show core error
 - `--group-by error|namespace|type|status` - Aggregate failures
-- `--format mermaid` - Output visual diagrams
-- `--format json` - Structured JSON output
+- `--output mermaid` - Output visual diagrams
+- `--output json` - Structured JSON output
 
 ## Visualization
 
-Use `--format mermaid` to generate diagrams:
-- `trace --format mermaid` → Flowchart of workflow chain
-- `timeline --format mermaid` → Sequence diagram of events
-- `state --format mermaid` → State diagram with pending work
-- `failures --group-by error --format mermaid` → Pie chart
+Use `--output mermaid` to generate diagrams:
+- `trace --output mermaid` → Flowchart of workflow chain
+- `timeline --output mermaid` → Sequence diagram of events
+- `state --output mermaid` → State diagram with pending work
+- `failures --group-by error --output mermaid` → Pie chart
 
 ## Debugging Workflow
 
 1. Start with `workflow diagnose` to see the chain and root cause
-2. Use `--format mermaid` to visualize if complex
+2. Use `--output mermaid` to visualize if complex
 3. Use `workflow failures --leaf-only` to see actual failures
 4. Use `workflow describe --pending` to check pending work on running workflows
 5. Use `--group-by` to find patterns in multiple failures
@@ -60,8 +60,8 @@ Use `--format mermaid` to generate diagrams:
 User: "The order workflow failed"
 
 You should:
-1. Run `temporal workflow describe --trace-root-cause --workflow-id order-123 --format json`
-2. If complex, add `--format mermaid` for visual
+1. Run `temporal workflow describe --trace-root-cause --workflow-id order-123 --output json`
+2. If complex, add `--output mermaid` for visual
 3. Identify the leaf failure and root cause
 4. Explain what went wrong
 5. Suggest a fix

examples/ai-research-agent-impl/llm-chat-transcript.md

@@ -807,7 +807,7 @@ func ResearchWorkflow(ctx workflow.Context, req shared.ResearchRequest) (*shared
 Restart your worker and run the starter to see it in action. You can watch the progress with:
 
 ```bash
-temporal agent timeline --workflow-id research-workflow --format mermaid
+temporal agent timeline --workflow-id research-workflow --output mermaid
 ```
 
 ```go
@@ -830,7 +830,7 @@ func ResearchWorkflow(ctx workflow.Context, req shared.ResearchRequest) (*shared
 ```
 
 ```shellscript
-temporal agent timeline --workflow-id research-workflow --format mermaid
+temporal agent timeline --workflow-id research-workflow --output mermaid
 ```
 
 ---
@@ -941,7 +941,7 @@ Done! The workflow now runs all sub-question research in parallel:
 Restart your worker and run again. You can see the parallel execution in the timeline:
 
 ```bash
-temporal agent timeline --workflow-id research-workflow --format mermaid
+temporal agent timeline --workflow-id research-workflow --output mermaid
 ```
 
 ```go
@@ -964,7 +964,7 @@ temporal agent timeline --workflow-id research-workflow --format mermaid
 ```
 
 ```shellscript
-temporal agent timeline --workflow-id research-workflow --format mermaid
+temporal agent timeline --workflow-id research-workflow --output mermaid
 ```
 
 ---
@@ -1434,7 +1434,7 @@ temporal agent failures --since 5m -o json
 
 **User**
 
-but, the output of `temporal agent failures --since 5m --format json` is empty. When I look at the Temporal UI, I see unlimited retries.
+but, the output of `temporal agent failures --since 5m --output json` is empty. When I look at the Temporal UI, I see unlimited retries.
 
 ---
 
@@ -1825,7 +1825,7 @@ Here's what happened, using the `temporal agent` commands to debug:
 
 **1. Timeline shows the failure:**
 ```bash
-temporal agent timeline --workflow-id research-workflow --format mermaid
+temporal agent timeline --workflow-id research-workflow --output mermaid
 ```
 
 ```mermaid
@@ -1863,7 +1863,7 @@ Key findings:
 To fix: either increase the timeout, reduce the sleep duration, or handle partial failures gracefully.
 
 ```shellscript
-temporal agent timeline --workflow-id research-workflow --format mermaid
+temporal agent timeline --workflow-id research-workflow --output mermaid
 ```
 
 ```plaintext

examples/ai-research-agent/.cursorrules

@@ -6,28 +6,28 @@ When debugging Temporal workflows, use the `temporal workflow` CLI commands inst
 
 ### Find Failures
 ```bash
-temporal workflow failures --since 1h --format json
-temporal workflow failures --since 1h --follow-children --leaf-only --compact-errors --format json
-temporal workflow failures --since 1h --group-by error --format json
+temporal workflow failures --since 1h --output json
+temporal workflow failures --since 1h --follow-children --leaf-only --compact-errors --output json
+temporal workflow failures --since 1h --group-by error --output json
 ```
 
 ### Trace Workflow Chain
 ```bash
-temporal workflow diagnose --workflow-id <id> --format json
-temporal workflow diagnose --workflow-id <id> --format mermaid
+temporal workflow diagnose --workflow-id <id> --output json
+temporal workflow diagnose --workflow-id <id> --output mermaid
 ```
 
 ### Get Timeline
 ```bash
-temporal workflow show --compact --workflow-id <id> --format json
-temporal workflow show --compact --workflow-id <id> --compact --format json
-temporal workflow show --compact --workflow-id <id> --format mermaid
+temporal workflow show --compact --workflow-id <id> --output json
+temporal workflow show --compact --workflow-id <id> --compact --output json
+temporal workflow show --compact --workflow-id <id> --output mermaid
 ```
 
 ### Check State
 ```bash
-temporal workflow describe --pending --workflow-id <id> --format json
-temporal workflow describe --pending --workflow-id <id> --format mermaid
+temporal workflow describe --pending --workflow-id <id> --output json
+temporal workflow describe --pending --workflow-id <id> --output mermaid
 ```
 
 ## Key Flags
@@ -36,21 +36,21 @@ temporal workflow describe --pending --workflow-id <id> --format mermaid
 - `--leaf-only` - Show only leaf failures (de-duplicate chains)
 - `--compact-errors` - Strip wrapper context, show core error
 - `--group-by error|namespace|type|status` - Aggregate failures
-- `--format mermaid` - Output visual diagrams
-- `--format json` - Structured JSON output
+- `--output mermaid` - Output visual diagrams
+- `--output json` - Structured JSON output
 
 ## Visualization
 
-Use `--format mermaid` to generate diagrams:
-- `trace --format mermaid` → Flowchart of workflow chain
-- `timeline --format mermaid` → Sequence diagram of events
-- `state --format mermaid` → State diagram with pending work
-- `failures --group-by error --format mermaid` → Pie chart
+Use `--output mermaid` to generate diagrams:
+- `trace --output mermaid` → Flowchart of workflow chain
+- `timeline --output mermaid` → Sequence diagram of events
+- `state --output mermaid` → State diagram with pending work
+- `failures --group-by error --output mermaid` → Pie chart
 
 ## Debugging Workflow
 
 1. Start with `workflow diagnose` to see the chain and root cause
-2. Use `--format mermaid` to visualize if complex
+2. Use `--output mermaid` to visualize if complex
 3. Use `workflow failures --leaf-only` to see actual failures
 4. Use `workflow describe --pending` to check pending work on running workflows
 5. Use `--group-by` to find patterns in multiple failures
@@ -60,8 +60,8 @@ Use `--format mermaid` to generate diagrams:
 User: "The order workflow failed"
 
 You should:
-1. Run `temporal workflow diagnose --workflow-id order-123 --format json`
-2. If complex, add `--format mermaid` for visual
+1. Run `temporal workflow diagnose --workflow-id order-123 --output json`
+2. If complex, add `--output mermaid` for visual
 3. Identify the leaf failure and root cause
 4. Explain what went wrong
 5. Suggest a fix