docs(workflow): document tailor.workflow.resumeWorkflow (#155)

* docs(workflow): document tailor.workflow.resumeWorkflow

The SDK now exposes `tailor.workflow.resumeWorkflow(executionId)` so user
code can resume a failed or pending-retry execution directly
(tailor-platform/sdk#1608). The workflow guides only covered the
`tailor-sdk workflow resume` CLI command, leaving self-healing flows
(functions, executors, pipeline resolvers) with no in-code path to point
readers at. Add a "Resuming from Code" subsection to the monitoring guide
covering the API, its return value, and the error it rejects with.

* docs(workflow): return results directly in workflow samples

Review the workflow guide samples for the same result-object smell fixed
in the IdP guide. The `tailor.workflow.*` runtime calls reject on
failure, so wrapping their results in `{ success: true }` (and, in the
resumeWorkflow example, catching to return `{ success: false }`) made the
samples read as if they presuppose try/catch-based error handling.

Drop the redundant `success` field from the triggerWorkflow, multi-step,
and error-handling samples, and rewrite the resumeWorkflow example to let
the error propagate. Keep the one try/catch that re-throws a wrapped
message, since controlling the error message is the case where catching
is warranted.

* docs(workflow): clarify resumeWorkflow example and resume semantics

Apply Copilot review feedback on the Resuming from Code section.

- Use `args.executionId` in the example so it matches the
  `resumeWorkflow(executionId)` signature and the `executionId` term used
  elsewhere in the guide.
- Reword the behavior paragraph to match the "restart from main, reuse
  cached results" mechanics described earlier in the section, rather than
  the looser "resumes from the point of failure" phrasing.

* docs(workflow): mention pending-retry in Resuming from Code intro

Apply Copilot review feedback. The intro said "a failed execution" while
the API reference below and the SDK changeset both cover "failed or
pending-retry" executions, so widen the intro to match and avoid
implying resumeWorkflow cannot resume pending-retry executions.

Author: k1LoW

docs/guides/workflow/creating-workflows.md

@@ -189,7 +189,6 @@ export function main(args) {
   });
 
   return {
-    success: true,
     orderId: validated.id,
     paymentId: payment.id,
   };
@@ -239,7 +238,7 @@ export function main(args) {
   try {
     // Risky operation
     const result = performOperation();
-    return { success: true, result };
+    return { result };
   } catch (error) {
     throw new Error(`Operation failed: ${error.message}`);
   }

docs/guides/workflow/monitoring-executions.md

@@ -204,6 +204,30 @@ processData  → Skipped (cached)
 saveToDb     → Executed again
 ```
 
+### Resuming from Code
+
+You can also resume a failed or pending-retry execution from your own code (a workflow job function, an executor, or a pipeline resolver) using `tailor.workflow.resumeWorkflow()`. This lets you build self-healing flows that recover from transient failures automatically, without an operator running `tailor-sdk workflow resume` or using the Tailor Console.
+
+**Example:**
+
+```javascript
+export async function main(args) {
+  const resumedId = await tailor.workflow.resumeWorkflow(args.executionId);
+  console.log("Resumed execution:", resumedId);
+  return { resumedExecutionId: resumedId };
+}
+```
+
+**API Reference:**
+
+- **First argument**: Execution ID of a failed or pending-retry execution (string)
+
+**Return value:**
+
+- Execution ID of the resumed execution (string)
+
+`resumeWorkflow()` behaves like the `resume` command described above. The workflow restarts from the main function and reuses the cached results of successful job functions, so only failed or not-yet-executed jobs run again. It rejects with an error whose message is prefixed with `resumeWorkflow failed:` when the execution cannot be resumed. Let that error propagate to fail the calling execution, and add a `try`/`catch` only when you need to control the error or its message.
+
 ### When to Use Resume
 
 Resume is useful when:

docs/guides/workflow/triggering-workflow.md

@@ -32,7 +32,6 @@ export async function main(args) {
   console.log("Notification workflow started:", executionId);
 
   return {
-    success: true,
     notificationExecutionId: executionId,
   };
 }