{"owner":"conductor-oss","repo":"conductor","hasSkills":true,"totalSkillsCount":8,"totalTokensCount":13806,"categories":["claude-rule","anthropic-skill","subagent-persona","root-instruction"],"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md","agentspan/src/test/resources/skills/crossref-skill.json","agentspan/src/test/resources/skills/dg-skill.json",".claude/agents/docs-writer.md","agentspan/src/test/resources/skills/conductor-skill.json","AGENTS.md","agentspan/src/test/resources/skills/large-skill.json","agentspan/src/test/resources/skills/simple-skill.json"],"skills":{"CLAUDE.md":"# CLAUDE.md — conductor (server repo)\n\nInstructions for Claude Code working in this repository.\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory or intuition. The workflow is: open the source → read what's there → write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nConcrete reason this matters: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Opening `WorkflowResource.java` first would have given the correct path (`POST /api/workflow/execute/{name}/{version}`) immediately.\n\n### For each content type, start here\n\n**REST endpoint or curl example**\n1. Open the controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method by its `@PostMapping`/`@GetMapping` annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body.\n4. Write the curl from what you just read.\n\n**CLI command or flag**\n1. Open `conductor-cli/cmd/*.go` (separate repo under this workspace).\n2. Find the `cobra.Command` for the subcommand and read its `Flags()` declarations.\n3. Write the example from what you just read — flag names, types, and defaults.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the SDK source file for the method you're documenting.\n2. Read the method signature and required parameters.\n3. If a working test exists for that method, use it as the starting point.\n4. Write from the signature — do not infer from the method name alone.\n\n**Expected output block**\n1. Get real output: run the command, or find it in test fixtures or CI logs.\n2. Paste verbatim. Do not construct output that \"looks right.\"\n3. For variable fields (IDs, timestamps), use annotated placeholders like `<workflow-id>`.\n\n**Editing an existing section**\n- Before changing anything, read every code block and command in the section.\n- Verify each one using the steps above, not just the block you plan to change.\n- Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI is unavailable:\n- Add `<!-- TODO: verify against live server -->` in the file.\n- Note it explicitly in the PR description.\n- Do not write an unverified example and leave it unmarked.\n\n### Key source locations\n\n| Content | Where to look |\n|---|---|\n| REST API routes | `rest/src/main/java/com/netflix/conductor/rest/controllers/` |\n| Workflow sync execution | `WorkflowResource.java` → `executeWorkflow()` at `@PostMapping(\"execute/{name}/{version}\")` |\n| Task routes | `TaskResource.java` |\n| CLI subcommands and flags | `conductor-cli/cmd/workflow.go`, `cmd/task.go`, etc. |\n\n## Other Guidelines\n\nSee [AGENTS.md](AGENTS.md) for full project conventions: code style, testing, dependency pinning, PR guidelines.\n","agentspan/src/test/resources/skills/crossref-skill.json":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: brainstorming\\ndescription: Brainstorming skill with cross-skill references.\\n---\\n# Brainstorming\\n\\nUse writing-plans to organize ideas.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {\n    \"writing-plans\": {\n      \"model\": \"openai/gpt-4o\",\n      \"agentModels\": {},\n      \"skillMd\": \"---\\nname: writing-plans\\ndescription: Create structured writing plans.\\n---\\n# Writing Plans\\n\\nYou help create structured writing plans.\",\n      \"agentFiles\": {},\n      \"scripts\": {},\n      \"resourceFiles\": [],\n      \"crossSkillRefs\": {}\n    }\n  }\n}\n","agentspan/src/test/resources/skills/dg-skill.json":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {\"gilfoyle\": \"openai/gpt-4o\"},\n  \"skillMd\": \"---\\nname: dg-skill\\ndescription: Adversarial code review.\\nmetadata:\\n  author: test\\n---\\n# DG Review\\n\\nDispatch gilfoyle, then dinesh. Repeat until convergence.\",\n  \"agentFiles\": {\n    \"gilfoyle\": \"# You Are Gilfoyle\\nReview code with precision.\",\n    \"dinesh\": \"# You Are Dinesh\\nDefend the code.\"\n  },\n  \"scripts\": {},\n  \"resourceFiles\": [\"comic-template.html\"],\n  \"crossSkillRefs\": {}\n}\n",".claude/agents/docs-writer.md":"---\nname: docs-writer\ndescription: Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.\ntools: Read, Grep, Glob, Write, Edit, Bash\nmodel: inherit\n---\n\nYou are a technical documentation specialist for Conductor, an open-source workflow orchestration engine built at Netflix.\n\n## Your Role\n\nCreate clear, comprehensive, and accurate documentation for Conductor features, including:\n- Workflow definitions and task types\n- REST API endpoints and payloads\n- System architecture and components\n- Configuration options and database integrations\n- SDK usage examples (Java, Python, JavaScript, Go, C#)\n- Developer guides and tutorials\n\n## Documentation Process\n\n1. **Understand the Feature**\n   - Read relevant source code to understand implementation\n   - Identify key classes, methods, and APIs\n   - Test functionality if possible\n   - Review existing related documentation\n\n2. **Structure Documentation**\n   - Start with a clear overview/summary\n   - Include purpose and use cases\n   - Provide syntax and parameters\n   - Add practical examples\n   - Document edge cases and limitations\n   - Link to related documentation\n\n3. **Follow Conductor Style**\n   - Use clear, concise language\n   - Include code examples in relevant languages\n   - Use Markdown formatting consistently\n   - Add diagrams or JSON examples for workflows\n   - Follow existing documentation patterns in `/docs`\n\n4. **Quality Standards**\n   - Ensure technical accuracy\n   - Test all code examples\n   - Use proper terminology (workflows, tasks, workers, etc.)\n   - Include error handling examples\n   - Add troubleshooting sections when relevant\n\n## Key Conductor Concepts to Reference\n\n- **Workflows**: JSON-based orchestration definitions\n- **Tasks**: Units of work (HTTP, Lambda, Sub-workflow, etc.)\n- **Workers**: Services that execute tasks\n- **Task Definitions**: Reusable task configurations\n- **System Tasks**: Built-in task types\n- **Event Handlers**: Trigger workflows from events\n\n## Output Format\n\nProvide documentation in Markdown format suitable for the `/docs` directory, with:\n- Clear headings and sections\n- Code blocks with proper syntax highlighting\n- Tables for parameters and options\n- Links to related documentation\n- Version information when relevant\n\nAlways prioritize clarity and practical usefulness for developers using Conductor.\n","agentspan/src/test/resources/skills/conductor-skill.json":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: conductor-skill\\ndescription: Manage Conductor workflows.\\n---\\n# Conductor\\n\\nUse conductor_api to manage workflows. See references/api-reference.md for details.\",\n  \"agentFiles\": {},\n  \"scripts\": {\n    \"conductor_api\": {\"filename\": \"conductor_api.py\", \"language\": \"python\"}\n  },\n  \"resourceFiles\": [\"references/api-reference.md\", \"references/workflow-definition.md\"],\n  \"crossSkillRefs\": {}\n}\n","AGENTS.md":"# AGENTS.md\n\nInstructions for AI coding agents working on the Conductor codebase.\n\n## Project Overview\n\nConductor is an open-source, distributed workflow orchestration engine designed for microservices.\nIt uses a pluggable architecture with interface-based abstractions for persistence, queuing, and indexing.\nThe project is built with Java 21 and uses Gradle as the build system.\n\n## Setup Commands\n\n| Command | Description |\n|---------|-------------|\n| `./gradlew build` | Build the entire project |\n| `./gradlew test` | Run all tests |\n| `./gradlew :module-name:test` | Run tests for a specific module |\n| `./gradlew spotlessApply` | Apply code formatting |\n| `./gradlew clean build` | Clean and rebuild |\n\n> **Important**: Always run `./gradlew spotlessApply` after making code changes to ensure consistent formatting.\n\n## Java Version References\n\n**Never link to a specific Java distribution** (e.g., Adoptium, Temurin, OpenJDK.org, Amazon Corretto) in docs, READMEs, or comments. Just say \"Java 21+\" and let users install it however they prefer.\n\n## Code Style\n\n- Use the Spotless plugin for uniform code formatting—always run before committing\n- Conductor is pluggable: when introducing new concepts, always use an **interface-based approach**\n- DAO interfaces **MUST** be defined in the `core` module\n- Implementation classes go in their respective persistence modules (e.g., `postgres-persistence`, `redis-persistence`)\n- Follow existing patterns in the codebase for consistency\n- Do not use emojis such as ✅ in the code, logs, or comments.  Keep comments professionals\n- When adding new logic, comment the algorithm, design etc.   \n\n## Architecture Guidelines\n\n### Module Structure\n\n- **core**: Contains interfaces, domain models, and core business logic\n- **persistence modules**: Implementations of DAO interfaces (postgres, redis, mysql, etc.)\n- **server**: Spring Boot application that brings everything together\n- **client**: SDK for interacting with Conductor\n- **ui**: React-based user interface\n\n### Key Patterns\n\n- DAOs are defined as interfaces in `core` and implemented in persistence modules\n- System tasks extend `WorkflowSystemTask` and are registered via Spring\n- Worker tasks use the `@WorkerTask` annotation for automatic discovery\n- Configuration is primarily done through Spring properties\n\n## Testing\n\n- **Avoid mocks**: Use real implementations whenever possible\n- **Test actual behavior**: Tests must verify real implementation logic, not duplicate it\n- **Use Testcontainers**: For database, cache, and other external dependencies\n- **Cover concurrency**: Ensure multi-threading scenarios are tested\n- **Run tests before submitting**: `./gradlew test` must pass\n\n### Test Locations\n\n- Unit tests: `src/test/java` in each module\n- Integration tests: `test-harness` module and `*-integration-test` modules\n- E2E tests: `e2e` module\n\n## PR Guidelines\n\n- Submit PRs against the `main` branch\n- Use clear, descriptive commit messages\n- Run `./gradlew spotlessApply` and `./gradlew test` before pushing\n- Add or update tests for any code changes\n- Keep PRs focused—one logical change per PR\n\n## Dependency Pinning\n\nSome dependencies have hard version constraints that **must not be auto-bumped**. These are marked with:\n\n```groovy\n// PINNED (#964): <reason>\n```\n\nThe issue number links back to https://github.com/conductor-oss/conductor/issues/964, which documents the full audit and upgrade path for each constraint.\n\n### What PINNED means\n\n`// PINNED (#964):` means the version is intentionally locked and upgrading it without understanding the constraint will break the build or cause a runtime failure. Do not bump a PINNED dependency as part of routine dependency updates or refactoring.\n\n### Current hard pins\n\n| Dependency | Pinned at | Why |\n|---|---|---|\n| `com.google.protobuf:protobuf-java` | `3.x` | 4.x + GraalVM polyglot 25.x causes Gradle to require `polyglot4`, which does not exist on Maven Central |\n| `com.google.protobuf:protoc` | `3.25.5` | Must match `grpc-protobuf:1.73.0`, which depends on protobuf-java 3.x |\n| `org.graalvm.*` (all 5 artifacts) | same version | All must share one version — mixing causes a `\"polyglot version X not compatible with Truffle Y\"` runtime error |\n| `redis.clients:jedis` in `redis-concurrency-limit` | `3.6.0` | `revJedis` (6.0.0) does not work with Spring Data Redis in that module |\n| `org.codehaus.jettison:jettison` | `strictly 1.5.4` | Gradle `strictly` constraint — no higher version has been validated |\n| `org.conductoross:conductor-client` in `test-harness` | `5.0.1` | Fat JAR classpath conflict with conductor-common; resolved via a stripped JAR task |\n| `org.awaitility:awaitility` in functional tests | `4.x` | e2e tests call `pollInterval(Duration)` added in Awaitility 4.0 |\n\n### Before bumping a PINNED dependency\n\n1. Read the comment carefully — it will name the incompatibility and often link to an upstream issue.\n2. Check whether the upstream blocker has been resolved (e.g., new grpc-java release, new GraalVM release).\n3. Test locally: `./gradlew clean build` plus `./gradlew test` in the affected modules.\n4. If bumping GraalVM, bump **all five** `org.graalvm.*` artifacts together using `revGraalVM` in `dependencies.gradle`.\n5. Update or remove the `// PINNED` comment once the constraint is lifted.\n\n### PINNED vs. version floors\n\nHard caps use `// PINNED (#964):`. Version floors — where a minimum is enforced but higher versions are always welcome — use one of two lowercase prefixes instead:\n\n```groovy\n// Security: CVE-2025-12183 — lz4-java minimum patched version\n// Compat: commons-lang3 3.18.0+ required by Testcontainers/commons-compress\n```\n\n- `// Security:` — minimum set to address a CVE or known vulnerability\n- `// Compat:` — minimum set for compatibility with another library or framework\n\nThese are grep-able (`grep \"// Security:\" **/*.gradle`, `grep \"// Compat:\" **/*.gradle`) but read as normal developer comments. Dependabot may raise these freely; no special review needed beyond the usual.\n\n## Security Considerations\n\n- Never commit secrets, API keys, or credentials\n- Be cautious with external dependencies—prefer well-maintained libraries\n- Follow secure coding practices for input validation and error handling\n- Review [SECURITY.md](SECURITY.md) for vulnerability reporting procedures\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory. Open the source first, read what's there, then write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nThis matters because plausible-looking docs can be silently wrong. Concretely: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Reading the controller first would have given the correct path immediately.\n\n### Workflow for each content type\n\n**REST API endpoint or curl example**\n1. Open the relevant controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method using its `@PostMapping`/`@GetMapping`/etc. annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body type.\n4. Write the curl command from what you just read.\n\n**CLI command or flag**\n1. Open `cmd/*.go` in `conductor-cli` (separate repo).\n2. Find the `cobra.Command` definition for the subcommand.\n3. Read the `Flags()` declarations for exact flag names, types, and defaults.\n4. Write the example from what you just read.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the relevant SDK source file.\n2. Find the method signature and required parameters.\n3. Write the example from the signature — do not infer from the method name alone.\n4. If a working test exists for that method, use it as the starting point.\n\n**Expected output block**\n1. Get real output: run the command locally, or find it in test fixtures, CI logs, or existing tests.\n2. Paste verbatim. Do not paraphrase or construct output that \"looks right.\"\n3. If the output varies by environment, show the stable parts and annotate the variable parts (e.g., `<workflow-id>`).\n\n**Editing an existing doc section**\n1. Before touching prose, read every code block and command in the section.\n2. Verify each one using the steps above — not just the block you plan to change.\n3. Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI binary is unavailable:\n- Add a `<!-- TODO: verify against live server -->` comment in the file.\n- Note it explicitly in the PR description.\n- Do not write a best-guess example and leave it unmarked.\n\n## Agent Behavior\n\n- **Prefer automation**: Execute requested actions without confirmation unless blocked by missing info or safety concerns\n- **Use parallel tools**: When tasks are independent, execute them in parallel for efficiency\n- **Verify changes**: Always run tests and spotless before considering work complete","agentspan/src/test/resources/skills/large-skill.json":"{\n  \"model\": \"openai/gpt-4o-mini\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: large-skill\\ndescription: A large skill for testing section splitting.\\n---\\n# Conductor Skill\\n\\nYou are the Conductor orchestrator. Follow these core rules:\\n1. Always validate inputs before processing\\n2. Never skip error handling\\n3. Log all operations for audit trail\\n\\nThese rules apply to ALL sections below.\\n\\n## Workflow Definitions\\n\\nThis section covers workflow definitions in detail.\\n\\n### Rule 1 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Running Workflows\\n\\nThis section covers running workflows in detail.\\n\\n### Rule 1 for Running Workflows\\n\\nWhen handling running workflows scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Running Workflows\\n\\nWhen handling running workflows scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Running Workflows\\n\\nWhen handling running workflows scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Running Workflows\\n\\nWhen handling running workflows scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Running Workflows\\n\\nWhen handling running workflows scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Running Workflows\\n\\nWhen handling running workflows scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Running Workflows\\n\\nWhen handling running workflows scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Running Workflows\\n\\nWhen handling running workflows scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Running Workflows\\n\\nWhen handling running workflows scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Running Workflows\\n\\nWhen handling running workflows scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Running Workflows\\n\\nWhen handling running workflows scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Running Workflows\\n\\nWhen handling running workflows scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Running Workflows\\n\\nWhen handling running workflows scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Running Workflows\\n\\nWhen handling running workflows scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Running Workflows\\n\\nWhen handling running workflows scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Running Workflows\\n\\nWhen handling running workflows scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Running Workflows\\n\\nWhen handling running workflows scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Running Workflows\\n\\nWhen handling running workflows scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Running Workflows\\n\\nWhen handling running workflows scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Running Workflows\\n\\nWhen handling running workflows scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Running Workflows\\n\\nWhen handling running workflows scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Running Workflows\\n\\nWhen handling running workflows scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Running Workflows\\n\\nWhen handling running workflows scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Running Workflows\\n\\nWhen handling running workflows scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Running Workflows\\n\\nWhen handling running workflows scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Running Workflows\\n\\nWhen handling running workflows scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Running Workflows\\n\\nWhen handling running workflows scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Running Workflows\\n\\nWhen handling running workflows scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Running Workflows\\n\\nWhen handling running workflows scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Running Workflows\\n\\nWhen handling running workflows scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Running Workflows\\n\\nWhen handling running workflows scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Running Workflows\\n\\nWhen handling running workflows scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Running Workflows\\n\\nWhen handling running workflows scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Running Workflows\\n\\nWhen handling running workflows scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Running Workflows\\n\\nWhen handling running workflows scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Running Workflows\\n\\nWhen handling running workflows scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Running Workflows\\n\\nWhen handling running workflows scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Running Workflows\\n\\nWhen handling running workflows scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Running Workflows\\n\\nWhen handling running workflows scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Running Workflows\\n\\nWhen handling running workflows scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Running Workflows\\n\\nWhen handling running workflows scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Running Workflows\\n\\nWhen handling running workflows scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Running Workflows\\n\\nWhen handling running workflows scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Running Workflows\\n\\nWhen handling running workflows scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Running Workflows\\n\\nWhen handling running workflows scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Running Workflows\\n\\nWhen handling running workflows scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Running Workflows\\n\\nWhen handling running workflows scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Running Workflows\\n\\nWhen handling running workflows scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Running Workflows\\n\\nWhen handling running workflows scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Running Workflows\\n\\nWhen handling running workflows scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Running Workflows\\n\\nWhen handling running workflows scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Running Workflows\\n\\nWhen handling running workflows scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Running Workflows\\n\\nWhen handling running workflows scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Running Workflows\\n\\nWhen handling running workflows scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Running Workflows\\n\\nWhen handling running workflows scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Running Workflows\\n\\nWhen handling running workflows scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Running Workflows\\n\\nWhen handling running workflows scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Running Workflows\\n\\nWhen handling running workflows scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Running Workflows\\n\\nWhen handling running workflows scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Running Workflows\\n\\nWhen handling running workflows scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Running Workflows\\n\\nWhen handling running workflows scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Running Workflows\\n\\nWhen handling running workflows scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Running Workflows\\n\\nWhen handling running workflows scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Running Workflows\\n\\nWhen handling running workflows scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Running Workflows\\n\\nWhen handling running workflows scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Running Workflows\\n\\nWhen handling running workflows scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Running Workflows\\n\\nWhen handling running workflows scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Running Workflows\\n\\nWhen handling running workflows scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Running Workflows\\n\\nWhen handling running workflows scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Running Workflows\\n\\nWhen handling running workflows scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Running Workflows\\n\\nWhen handling running workflows scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Running Workflows\\n\\nWhen handling running workflows scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Running Workflows\\n\\nWhen handling running workflows scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Running Workflows\\n\\nWhen handling running workflows scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Running Workflows\\n\\nWhen handling running workflows scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Running Workflows\\n\\nWhen handling running workflows scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Running Workflows\\n\\nWhen handling running workflows scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Running Workflows\\n\\nWhen handling running workflows scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Running Workflows\\n\\nWhen handling running workflows scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Running Workflows\\n\\nWhen handling running workflows scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Error Handling\\n\\nThis section covers error handling in detail.\\n\\n### Rule 1 for Error Handling\\n\\nWhen handling error handling scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Error Handling\\n\\nWhen handling error handling scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Error Handling\\n\\nWhen handling error handling scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Error Handling\\n\\nWhen handling error handling scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Error Handling\\n\\nWhen handling error handling scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Error Handling\\n\\nWhen handling error handling scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Error Handling\\n\\nWhen handling error handling scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Error Handling\\n\\nWhen handling error handling scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Error Handling\\n\\nWhen handling error handling scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Error Handling\\n\\nWhen handling error handling scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Error Handling\\n\\nWhen handling error handling scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Error Handling\\n\\nWhen handling error handling scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Error Handling\\n\\nWhen handling error handling scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Error Handling\\n\\nWhen handling error handling scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Error Handling\\n\\nWhen handling error handling scenario 15, you must follow these steps carefully. First, validate ","agentspan/src/test/resources/skills/simple-skill.json":"{\n  \"model\": \"openai/gpt-4o\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: simple-skill\\ndescription: A simple test skill.\\n---\\n# Simple Skill\\n\\nYou are a helpful assistant.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {}\n}\n"},"files":{"CLAUDE.md":"# CLAUDE.md — conductor (server repo)\n\nInstructions for Claude Code working in this repository.\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory or intuition. The workflow is: open the source → read what's there → write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nConcrete reason this matters: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Opening `WorkflowResource.java` first would have given the correct path (`POST /api/workflow/execute/{name}/{version}`) immediately.\n\n### For each content type, start here\n\n**REST endpoint or curl example**\n1. Open the controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method by its `@PostMapping`/`@GetMapping` annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body.\n4. Write the curl from what you just read.\n\n**CLI command or flag**\n1. Open `conductor-cli/cmd/*.go` (separate repo under this workspace).\n2. Find the `cobra.Command` for the subcommand and read its `Flags()` declarations.\n3. Write the example from what you just read — flag names, types, and defaults.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the SDK source file for the method you're documenting.\n2. Read the method signature and required parameters.\n3. If a working test exists for that method, use it as the starting point.\n4. Write from the signature — do not infer from the method name alone.\n\n**Expected output block**\n1. Get real output: run the command, or find it in test fixtures or CI logs.\n2. Paste verbatim. Do not construct output that \"looks right.\"\n3. For variable fields (IDs, timestamps), use annotated placeholders like `<workflow-id>`.\n\n**Editing an existing section**\n- Before changing anything, read every code block and command in the section.\n- Verify each one using the steps above, not just the block you plan to change.\n- Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI is unavailable:\n- Add `<!-- TODO: verify against live server -->` in the file.\n- Note it explicitly in the PR description.\n- Do not write an unverified example and leave it unmarked.\n\n### Key source locations\n\n| Content | Where to look |\n|---|---|\n| REST API routes | `rest/src/main/java/com/netflix/conductor/rest/controllers/` |\n| Workflow sync execution | `WorkflowResource.java` → `executeWorkflow()` at `@PostMapping(\"execute/{name}/{version}\")` |\n| Task routes | `TaskResource.java` |\n| CLI subcommands and flags | `conductor-cli/cmd/workflow.go`, `cmd/task.go`, etc. |\n\n## Other Guidelines\n\nSee [AGENTS.md](AGENTS.md) for full project conventions: code style, testing, dependency pinning, PR guidelines.\n","agentspan/src/test/resources/skills/crossref-skill.json":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: brainstorming\\ndescription: Brainstorming skill with cross-skill references.\\n---\\n# Brainstorming\\n\\nUse writing-plans to organize ideas.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {\n    \"writing-plans\": {\n      \"model\": \"openai/gpt-4o\",\n      \"agentModels\": {},\n      \"skillMd\": \"---\\nname: writing-plans\\ndescription: Create structured writing plans.\\n---\\n# Writing Plans\\n\\nYou help create structured writing plans.\",\n      \"agentFiles\": {},\n      \"scripts\": {},\n      \"resourceFiles\": [],\n      \"crossSkillRefs\": {}\n    }\n  }\n}\n","agentspan/src/test/resources/skills/dg-skill.json":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {\"gilfoyle\": \"openai/gpt-4o\"},\n  \"skillMd\": \"---\\nname: dg-skill\\ndescription: Adversarial code review.\\nmetadata:\\n  author: test\\n---\\n# DG Review\\n\\nDispatch gilfoyle, then dinesh. Repeat until convergence.\",\n  \"agentFiles\": {\n    \"gilfoyle\": \"# You Are Gilfoyle\\nReview code with precision.\",\n    \"dinesh\": \"# You Are Dinesh\\nDefend the code.\"\n  },\n  \"scripts\": {},\n  \"resourceFiles\": [\"comic-template.html\"],\n  \"crossSkillRefs\": {}\n}\n",".claude/agents/docs-writer.md":"---\nname: docs-writer\ndescription: Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.\ntools: Read, Grep, Glob, Write, Edit, Bash\nmodel: inherit\n---\n\nYou are a technical documentation specialist for Conductor, an open-source workflow orchestration engine built at Netflix.\n\n## Your Role\n\nCreate clear, comprehensive, and accurate documentation for Conductor features, including:\n- Workflow definitions and task types\n- REST API endpoints and payloads\n- System architecture and components\n- Configuration options and database integrations\n- SDK usage examples (Java, Python, JavaScript, Go, C#)\n- Developer guides and tutorials\n\n## Documentation Process\n\n1. **Understand the Feature**\n   - Read relevant source code to understand implementation\n   - Identify key classes, methods, and APIs\n   - Test functionality if possible\n   - Review existing related documentation\n\n2. **Structure Documentation**\n   - Start with a clear overview/summary\n   - Include purpose and use cases\n   - Provide syntax and parameters\n   - Add practical examples\n   - Document edge cases and limitations\n   - Link to related documentation\n\n3. **Follow Conductor Style**\n   - Use clear, concise language\n   - Include code examples in relevant languages\n   - Use Markdown formatting consistently\n   - Add diagrams or JSON examples for workflows\n   - Follow existing documentation patterns in `/docs`\n\n4. **Quality Standards**\n   - Ensure technical accuracy\n   - Test all code examples\n   - Use proper terminology (workflows, tasks, workers, etc.)\n   - Include error handling examples\n   - Add troubleshooting sections when relevant\n\n## Key Conductor Concepts to Reference\n\n- **Workflows**: JSON-based orchestration definitions\n- **Tasks**: Units of work (HTTP, Lambda, Sub-workflow, etc.)\n- **Workers**: Services that execute tasks\n- **Task Definitions**: Reusable task configurations\n- **System Tasks**: Built-in task types\n- **Event Handlers**: Trigger workflows from events\n\n## Output Format\n\nProvide documentation in Markdown format suitable for the `/docs` directory, with:\n- Clear headings and sections\n- Code blocks with proper syntax highlighting\n- Tables for parameters and options\n- Links to related documentation\n- Version information when relevant\n\nAlways prioritize clarity and practical usefulness for developers using Conductor.\n","agentspan/src/test/resources/skills/conductor-skill.json":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: conductor-skill\\ndescription: Manage Conductor workflows.\\n---\\n# Conductor\\n\\nUse conductor_api to manage workflows. See references/api-reference.md for details.\",\n  \"agentFiles\": {},\n  \"scripts\": {\n    \"conductor_api\": {\"filename\": \"conductor_api.py\", \"language\": \"python\"}\n  },\n  \"resourceFiles\": [\"references/api-reference.md\", \"references/workflow-definition.md\"],\n  \"crossSkillRefs\": {}\n}\n","AGENTS.md":"# AGENTS.md\n\nInstructions for AI coding agents working on the Conductor codebase.\n\n## Project Overview\n\nConductor is an open-source, distributed workflow orchestration engine designed for microservices.\nIt uses a pluggable architecture with interface-based abstractions for persistence, queuing, and indexing.\nThe project is built with Java 21 and uses Gradle as the build system.\n\n## Setup Commands\n\n| Command | Description |\n|---------|-------------|\n| `./gradlew build` | Build the entire project |\n| `./gradlew test` | Run all tests |\n| `./gradlew :module-name:test` | Run tests for a specific module |\n| `./gradlew spotlessApply` | Apply code formatting |\n| `./gradlew clean build` | Clean and rebuild |\n\n> **Important**: Always run `./gradlew spotlessApply` after making code changes to ensure consistent formatting.\n\n## Java Version References\n\n**Never link to a specific Java distribution** (e.g., Adoptium, Temurin, OpenJDK.org, Amazon Corretto) in docs, READMEs, or comments. Just say \"Java 21+\" and let users install it however they prefer.\n\n## Code Style\n\n- Use the Spotless plugin for uniform code formatting—always run before committing\n- Conductor is pluggable: when introducing new concepts, always use an **interface-based approach**\n- DAO interfaces **MUST** be defined in the `core` module\n- Implementation classes go in their respective persistence modules (e.g., `postgres-persistence`, `redis-persistence`)\n- Follow existing patterns in the codebase for consistency\n- Do not use emojis such as ✅ in the code, logs, or comments.  Keep comments professionals\n- When adding new logic, comment the algorithm, design etc.   \n\n## Architecture Guidelines\n\n### Module Structure\n\n- **core**: Contains interfaces, domain models, and core business logic\n- **persistence modules**: Implementations of DAO interfaces (postgres, redis, mysql, etc.)\n- **server**: Spring Boot application that brings everything together\n- **client**: SDK for interacting with Conductor\n- **ui**: React-based user interface\n\n### Key Patterns\n\n- DAOs are defined as interfaces in `core` and implemented in persistence modules\n- System tasks extend `WorkflowSystemTask` and are registered via Spring\n- Worker tasks use the `@WorkerTask` annotation for automatic discovery\n- Configuration is primarily done through Spring properties\n\n## Testing\n\n- **Avoid mocks**: Use real implementations whenever possible\n- **Test actual behavior**: Tests must verify real implementation logic, not duplicate it\n- **Use Testcontainers**: For database, cache, and other external dependencies\n- **Cover concurrency**: Ensure multi-threading scenarios are tested\n- **Run tests before submitting**: `./gradlew test` must pass\n\n### Test Locations\n\n- Unit tests: `src/test/java` in each module\n- Integration tests: `test-harness` module and `*-integration-test` modules\n- E2E tests: `e2e` module\n\n## PR Guidelines\n\n- Submit PRs against the `main` branch\n- Use clear, descriptive commit messages\n- Run `./gradlew spotlessApply` and `./gradlew test` before pushing\n- Add or update tests for any code changes\n- Keep PRs focused—one logical change per PR\n\n## Dependency Pinning\n\nSome dependencies have hard version constraints that **must not be auto-bumped**. These are marked with:\n\n```groovy\n// PINNED (#964): <reason>\n```\n\nThe issue number links back to https://github.com/conductor-oss/conductor/issues/964, which documents the full audit and upgrade path for each constraint.\n\n### What PINNED means\n\n`// PINNED (#964):` means the version is intentionally locked and upgrading it without understanding the constraint will break the build or cause a runtime failure. Do not bump a PINNED dependency as part of routine dependency updates or refactoring.\n\n### Current hard pins\n\n| Dependency | Pinned at | Why |\n|---|---|---|\n| `com.google.protobuf:protobuf-java` | `3.x` | 4.x + GraalVM polyglot 25.x causes Gradle to require `polyglot4`, which does not exist on Maven Central |\n| `com.google.protobuf:protoc` | `3.25.5` | Must match `grpc-protobuf:1.73.0`, which depends on protobuf-java 3.x |\n| `org.graalvm.*` (all 5 artifacts) | same version | All must share one version — mixing causes a `\"polyglot version X not compatible with Truffle Y\"` runtime error |\n| `redis.clients:jedis` in `redis-concurrency-limit` | `3.6.0` | `revJedis` (6.0.0) does not work with Spring Data Redis in that module |\n| `org.codehaus.jettison:jettison` | `strictly 1.5.4` | Gradle `strictly` constraint — no higher version has been validated |\n| `org.conductoross:conductor-client` in `test-harness` | `5.0.1` | Fat JAR classpath conflict with conductor-common; resolved via a stripped JAR task |\n| `org.awaitility:awaitility` in functional tests | `4.x` | e2e tests call `pollInterval(Duration)` added in Awaitility 4.0 |\n\n### Before bumping a PINNED dependency\n\n1. Read the comment carefully — it will name the incompatibility and often link to an upstream issue.\n2. Check whether the upstream blocker has been resolved (e.g., new grpc-java release, new GraalVM release).\n3. Test locally: `./gradlew clean build` plus `./gradlew test` in the affected modules.\n4. If bumping GraalVM, bump **all five** `org.graalvm.*` artifacts together using `revGraalVM` in `dependencies.gradle`.\n5. Update or remove the `// PINNED` comment once the constraint is lifted.\n\n### PINNED vs. version floors\n\nHard caps use `// PINNED (#964):`. Version floors — where a minimum is enforced but higher versions are always welcome — use one of two lowercase prefixes instead:\n\n```groovy\n// Security: CVE-2025-12183 — lz4-java minimum patched version\n// Compat: commons-lang3 3.18.0+ required by Testcontainers/commons-compress\n```\n\n- `// Security:` — minimum set to address a CVE or known vulnerability\n- `// Compat:` — minimum set for compatibility with another library or framework\n\nThese are grep-able (`grep \"// Security:\" **/*.gradle`, `grep \"// Compat:\" **/*.gradle`) but read as normal developer comments. Dependabot may raise these freely; no special review needed beyond the usual.\n\n## Security Considerations\n\n- Never commit secrets, API keys, or credentials\n- Be cautious with external dependencies—prefer well-maintained libraries\n- Follow secure coding practices for input validation and error handling\n- Review [SECURITY.md](SECURITY.md) for vulnerability reporting procedures\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory. Open the source first, read what's there, then write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nThis matters because plausible-looking docs can be silently wrong. Concretely: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Reading the controller first would have given the correct path immediately.\n\n### Workflow for each content type\n\n**REST API endpoint or curl example**\n1. Open the relevant controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method using its `@PostMapping`/`@GetMapping`/etc. annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body type.\n4. Write the curl command from what you just read.\n\n**CLI command or flag**\n1. Open `cmd/*.go` in `conductor-cli` (separate repo).\n2. Find the `cobra.Command` definition for the subcommand.\n3. Read the `Flags()` declarations for exact flag names, types, and defaults.\n4. Write the example from what you just read.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the relevant SDK source file.\n2. Find the method signature and required parameters.\n3. Write the example from the signature — do not infer from the method name alone.\n4. If a working test exists for that method, use it as the starting point.\n\n**Expected output block**\n1. Get real output: run the command locally, or find it in test fixtures, CI logs, or existing tests.\n2. Paste verbatim. Do not paraphrase or construct output that \"looks right.\"\n3. If the output varies by environment, show the stable parts and annotate the variable parts (e.g., `<workflow-id>`).\n\n**Editing an existing doc section**\n1. Before touching prose, read every code block and command in the section.\n2. Verify each one using the steps above — not just the block you plan to change.\n3. Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI binary is unavailable:\n- Add a `<!-- TODO: verify against live server -->` comment in the file.\n- Note it explicitly in the PR description.\n- Do not write a best-guess example and leave it unmarked.\n\n## Agent Behavior\n\n- **Prefer automation**: Execute requested actions without confirmation unless blocked by missing info or safety concerns\n- **Use parallel tools**: When tasks are independent, execute them in parallel for efficiency\n- **Verify changes**: Always run tests and spotless before considering work complete","agentspan/src/test/resources/skills/large-skill.json":"{\n  \"model\": \"openai/gpt-4o-mini\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: large-skill\\ndescription: A large skill for testing section splitting.\\n---\\n# Conductor Skill\\n\\nYou are the Conductor orchestrator. Follow these core rules:\\n1. Always validate inputs before processing\\n2. Never skip error handling\\n3. Log all operations for audit trail\\n\\nThese rules apply to ALL sections below.\\n\\n## Workflow Definitions\\n\\nThis section covers workflow definitions in detail.\\n\\n### Rule 1 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Running Workflows\\n\\nThis section covers running workflows in detail.\\n\\n### Rule 1 for Running Workflows\\n\\nWhen handling running workflows scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Running Workflows\\n\\nWhen handling running workflows scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Running Workflows\\n\\nWhen handling running workflows scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Running Workflows\\n\\nWhen handling running workflows scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Running Workflows\\n\\nWhen handling running workflows scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Running Workflows\\n\\nWhen handling running workflows scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Running Workflows\\n\\nWhen handling running workflows scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Running Workflows\\n\\nWhen handling running workflows scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Running Workflows\\n\\nWhen handling running workflows scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Running Workflows\\n\\nWhen handling running workflows scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Running Workflows\\n\\nWhen handling running workflows scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Running Workflows\\n\\nWhen handling running workflows scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Running Workflows\\n\\nWhen handling running workflows scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Running Workflows\\n\\nWhen handling running workflows scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Running Workflows\\n\\nWhen handling running workflows scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Running Workflows\\n\\nWhen handling running workflows scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Running Workflows\\n\\nWhen handling running workflows scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Running Workflows\\n\\nWhen handling running workflows scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Running Workflows\\n\\nWhen handling running workflows scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Running Workflows\\n\\nWhen handling running workflows scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Running Workflows\\n\\nWhen handling running workflows scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Running Workflows\\n\\nWhen handling running workflows scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Running Workflows\\n\\nWhen handling running workflows scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Running Workflows\\n\\nWhen handling running workflows scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Running Workflows\\n\\nWhen handling running workflows scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Running Workflows\\n\\nWhen handling running workflows scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Running Workflows\\n\\nWhen handling running workflows scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Running Workflows\\n\\nWhen handling running workflows scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Running Workflows\\n\\nWhen handling running workflows scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Running Workflows\\n\\nWhen handling running workflows scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Running Workflows\\n\\nWhen handling running workflows scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Running Workflows\\n\\nWhen handling running workflows scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Running Workflows\\n\\nWhen handling running workflows scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Running Workflows\\n\\nWhen handling running workflows scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Running Workflows\\n\\nWhen handling running workflows scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Running Workflows\\n\\nWhen handling running workflows scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Running Workflows\\n\\nWhen handling running workflows scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Running Workflows\\n\\nWhen handling running workflows scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Running Workflows\\n\\nWhen handling running workflows scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Running Workflows\\n\\nWhen handling running workflows scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Running Workflows\\n\\nWhen handling running workflows scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Running Workflows\\n\\nWhen handling running workflows scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Running Workflows\\n\\nWhen handling running workflows scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Running Workflows\\n\\nWhen handling running workflows scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Running Workflows\\n\\nWhen handling running workflows scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Running Workflows\\n\\nWhen handling running workflows scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Running Workflows\\n\\nWhen handling running workflows scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Running Workflows\\n\\nWhen handling running workflows scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Running Workflows\\n\\nWhen handling running workflows scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Running Workflows\\n\\nWhen handling running workflows scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Running Workflows\\n\\nWhen handling running workflows scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Running Workflows\\n\\nWhen handling running workflows scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Running Workflows\\n\\nWhen handling running workflows scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Running Workflows\\n\\nWhen handling running workflows scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Running Workflows\\n\\nWhen handling running workflows scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Running Workflows\\n\\nWhen handling running workflows scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Running Workflows\\n\\nWhen handling running workflows scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Running Workflows\\n\\nWhen handling running workflows scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Running Workflows\\n\\nWhen handling running workflows scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Running Workflows\\n\\nWhen handling running workflows scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Running Workflows\\n\\nWhen handling running workflows scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Running Workflows\\n\\nWhen handling running workflows scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Running Workflows\\n\\nWhen handling running workflows scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Running Workflows\\n\\nWhen handling running workflows scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Running Workflows\\n\\nWhen handling running workflows scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Running Workflows\\n\\nWhen handling running workflows scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Running Workflows\\n\\nWhen handling running workflows scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Running Workflows\\n\\nWhen handling running workflows scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Running Workflows\\n\\nWhen handling running workflows scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Running Workflows\\n\\nWhen handling running workflows scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Running Workflows\\n\\nWhen handling running workflows scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Running Workflows\\n\\nWhen handling running workflows scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Running Workflows\\n\\nWhen handling running workflows scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Running Workflows\\n\\nWhen handling running workflows scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Running Workflows\\n\\nWhen handling running workflows scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Running Workflows\\n\\nWhen handling running workflows scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Running Workflows\\n\\nWhen handling running workflows scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Running Workflows\\n\\nWhen handling running workflows scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Running Workflows\\n\\nWhen handling running workflows scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Running Workflows\\n\\nWhen handling running workflows scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Error Handling\\n\\nThis section covers error handling in detail.\\n\\n### Rule 1 for Error Handling\\n\\nWhen handling error handling scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Error Handling\\n\\nWhen handling error handling scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Error Handling\\n\\nWhen handling error handling scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Error Handling\\n\\nWhen handling error handling scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Error Handling\\n\\nWhen handling error handling scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Error Handling\\n\\nWhen handling error handling scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Error Handling\\n\\nWhen handling error handling scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Error Handling\\n\\nWhen handling error handling scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Error Handling\\n\\nWhen handling error handling scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Error Handling\\n\\nWhen handling error handling scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Error Handling\\n\\nWhen handling error handling scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Error Handling\\n\\nWhen handling error handling scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Error Handling\\n\\nWhen handling error handling scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Error Handling\\n\\nWhen handling error handling scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Error Handling\\n\\nWhen handling error handling scenario 15, you must follow these steps carefully. First, validate ","agentspan/src/test/resources/skills/simple-skill.json":"{\n  \"model\": \"openai/gpt-4o\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: simple-skill\\ndescription: A simple test skill.\\n---\\n# Simple Skill\\n\\nYou are a helpful assistant.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {}\n}\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# AGENTS.md\n\nInstructions for AI coding agents working on the Conductor codebase.\n\n## Project Overview\n\nConductor is an open-source, distributed workflow orchestration engine designed for microservices.\nIt uses a pluggable architecture with interface-based abstractions for persistence, queuing, and indexing.\nThe project is built with Java 21 and uses Gradle as the build system.\n\n## Setup Commands\n\n| Command | Description |\n|---------|-------------|\n| `./gradlew build` | Build the entire project |\n| `./gradlew test` | Run all tests |\n| `./gradlew :module-name:test` | Run tests for a specific module |\n| `./gradlew spotlessApply` | Apply code formatting |\n| `./gradlew clean build` | Clean and rebuild |\n\n> **Important**: Always run `./gradlew spotlessApply` after making code changes to ensure consistent formatting.\n\n## Java Version References\n\n**Never link to a specific Java distribution** (e.g., Adoptium, Temurin, OpenJDK.org, Amazon Corretto) in docs, READMEs, or comments. Just say \"Java 21+\" and let users install it however they prefer.\n\n## Code Style\n\n- Use the Spotless plugin for uniform code formatting—always run before committing\n- Conductor is pluggable: when introducing new concepts, always use an **interface-based approach**\n- DAO interfaces **MUST** be defined in the `core` module\n- Implementation classes go in their respective persistence modules (e.g., `postgres-persistence`, `redis-persistence`)\n- Follow existing patterns in the codebase for consistency\n- Do not use emojis such as ✅ in the code, logs, or comments.  Keep comments professionals\n- When adding new logic, comment the algorithm, design etc.   \n\n## Architecture Guidelines\n\n### Module Structure\n\n- **core**: Contains interfaces, domain models, and core business logic\n- **persistence modules**: Implementations of DAO interfaces (postgres, redis, mysql, etc.)\n- **server**: Spring Boot application that brings everything together\n- **client**: SDK for interacting with Conductor\n- **ui**: React-based user interface\n\n### Key Patterns\n\n- DAOs are defined as interfaces in `core` and implemented in persistence modules\n- System tasks extend `WorkflowSystemTask` and are registered via Spring\n- Worker tasks use the `@WorkerTask` annotation for automatic discovery\n- Configuration is primarily done through Spring properties\n\n## Testing\n\n- **Avoid mocks**: Use real implementations whenever possible\n- **Test actual behavior**: Tests must verify real implementation logic, not duplicate it\n- **Use Testcontainers**: For database, cache, and other external dependencies\n- **Cover concurrency**: Ensure multi-threading scenarios are tested\n- **Run tests before submitting**: `./gradlew test` must pass\n\n### Test Locations\n\n- Unit tests: `src/test/java` in each module\n- Integration tests: `test-harness` module and `*-integration-test` modules\n- E2E tests: `e2e` module\n\n## PR Guidelines\n\n- Submit PRs against the `main` branch\n- Use clear, descriptive commit messages\n- Run `./gradlew spotlessApply` and `./gradlew test` before pushing\n- Add or update tests for any code changes\n- Keep PRs focused—one logical change per PR\n\n## Dependency Pinning\n\nSome dependencies have hard version constraints that **must not be auto-bumped**. These are marked with:\n\n```groovy\n// PINNED (#964): <reason>\n```\n\nThe issue number links back to https://github.com/conductor-oss/conductor/issues/964, which documents the full audit and upgrade path for each constraint.\n\n### What PINNED means\n\n`// PINNED (#964):` means the version is intentionally locked and upgrading it without understanding the constraint will break the build or cause a runtime failure. Do not bump a PINNED dependency as part of routine dependency updates or refactoring.\n\n### Current hard pins\n\n| Dependency | Pinned at | Why |\n|---|---|---|\n| `com.google.protobuf:protobuf-java` | `3.x` | 4.x + GraalVM polyglot 25.x causes Gradle to require `polyglot4`, which does not exist on Maven Central |\n| `com.google.protobuf:protoc` | `3.25.5` | Must match `grpc-protobuf:1.73.0`, which depends on protobuf-java 3.x |\n| `org.graalvm.*` (all 5 artifacts) | same version | All must share one version — mixing causes a `\"polyglot version X not compatible with Truffle Y\"` runtime error |\n| `redis.clients:jedis` in `redis-concurrency-limit` | `3.6.0` | `revJedis` (6.0.0) does not work with Spring Data Redis in that module |\n| `org.codehaus.jettison:jettison` | `strictly 1.5.4` | Gradle `strictly` constraint — no higher version has been validated |\n| `org.conductoross:conductor-client` in `test-harness` | `5.0.1` | Fat JAR classpath conflict with conductor-common; resolved via a stripped JAR task |\n| `org.awaitility:awaitility` in functional tests | `4.x` | e2e tests call `pollInterval(Duration)` added in Awaitility 4.0 |\n\n### Before bumping a PINNED dependency\n\n1. Read the comment carefully — it will name the incompatibility and often link to an upstream issue.\n2. Check whether the upstream blocker has been resolved (e.g., new grpc-java release, new GraalVM release).\n3. Test locally: `./gradlew clean build` plus `./gradlew test` in the affected modules.\n4. If bumping GraalVM, bump **all five** `org.graalvm.*` artifacts together using `revGraalVM` in `dependencies.gradle`.\n5. Update or remove the `// PINNED` comment once the constraint is lifted.\n\n### PINNED vs. version floors\n\nHard caps use `// PINNED (#964):`. Version floors — where a minimum is enforced but higher versions are always welcome — use one of two lowercase prefixes instead:\n\n```groovy\n// Security: CVE-2025-12183 — lz4-java minimum patched version\n// Compat: commons-lang3 3.18.0+ required by Testcontainers/commons-compress\n```\n\n- `// Security:` — minimum set to address a CVE or known vulnerability\n- `// Compat:` — minimum set for compatibility with another library or framework\n\nThese are grep-able (`grep \"// Security:\" **/*.gradle`, `grep \"// Compat:\" **/*.gradle`) but read as normal developer comments. Dependabot may raise these freely; no special review needed beyond the usual.\n\n## Security Considerations\n\n- Never commit secrets, API keys, or credentials\n- Be cautious with external dependencies—prefer well-maintained libraries\n- Follow secure coding practices for input validation and error handling\n- Review [SECURITY.md](SECURITY.md) for vulnerability reporting procedures\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory. Open the source first, read what's there, then write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nThis matters because plausible-looking docs can be silently wrong. Concretely: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Reading the controller first would have given the correct path immediately.\n\n### Workflow for each content type\n\n**REST API endpoint or curl example**\n1. Open the relevant controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method using its `@PostMapping`/`@GetMapping`/etc. annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body type.\n4. Write the curl command from what you just read.\n\n**CLI command or flag**\n1. Open `cmd/*.go` in `conductor-cli` (separate repo).\n2. Find the `cobra.Command` definition for the subcommand.\n3. Read the `Flags()` declarations for exact flag names, types, and defaults.\n4. Write the example from what you just read.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the relevant SDK source file.\n2. Find the method signature and required parameters.\n3. Write the example from the signature — do not infer from the method name alone.\n4. If a working test exists for that method, use it as the starting point.\n\n**Expected output block**\n1. Get real output: run the command locally, or find it in test fixtures, CI logs, or existing tests.\n2. Paste verbatim. Do not paraphrase or construct output that \"looks right.\"\n3. If the output varies by environment, show the stable parts and annotate the variable parts (e.g., `<workflow-id>`).\n\n**Editing an existing doc section**\n1. Before touching prose, read every code block and command in the section.\n2. Verify each one using the steps above — not just the block you plan to change.\n3. Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI binary is unavailable:\n- Add a `<!-- TODO: verify against live server -->` comment in the file.\n- Note it explicitly in the PR description.\n- Do not write a best-guess example and leave it unmarked.\n\n## Agent Behavior\n\n- **Prefer automation**: Execute requested actions without confirmation unless blocked by missing info or safety concerns\n- **Use parallel tools**: When tasks are independent, execute them in parallel for efficiency\n- **Verify changes**: Always run tests and spotless before considering work complete","isInternal":false,"tokens":2095,"sizeBytes":8997},{"name":"conductor-skill.json","path":"agentspan/src/test/resources/skills/conductor-skill.json","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/agentspan/src/test/resources/skills/conductor-skill.json","title":"Skills Skill","category":"anthropic-skill","format":"json","content":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: conductor-skill\\ndescription: Manage Conductor workflows.\\n---\\n# Conductor\\n\\nUse conductor_api to manage workflows. See references/api-reference.md for details.\",\n  \"agentFiles\": {},\n  \"scripts\": {\n    \"conductor_api\": {\"filename\": \"conductor_api.py\", \"language\": \"python\"}\n  },\n  \"resourceFiles\": [\"references/api-reference.md\", \"references/workflow-definition.md\"],\n  \"crossSkillRefs\": {}\n}\n","frontmatter":{"model":"anthropic/claude-sonnet-4-6","agentModels":{},"skillMd":"---\nname: conductor-skill\ndescription: Manage Conductor workflows.\n---\n# Conductor\n\nUse conductor_api to manage workflows. See references/api-reference.md for details.","agentFiles":{},"scripts":{"conductor_api":{"filename":"conductor_api.py","language":"python"}},"resourceFiles":["references/api-reference.md","references/workflow-definition.md"],"crossSkillRefs":{}},"isInternal":false,"tokens":131,"sizeBytes":485},{"name":"crossref-skill.json","path":"agentspan/src/test/resources/skills/crossref-skill.json","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/agentspan/src/test/resources/skills/crossref-skill.json","title":"Skills Skill","category":"anthropic-skill","format":"json","content":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: brainstorming\\ndescription: Brainstorming skill with cross-skill references.\\n---\\n# Brainstorming\\n\\nUse writing-plans to organize ideas.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {\n    \"writing-plans\": {\n      \"model\": \"openai/gpt-4o\",\n      \"agentModels\": {},\n      \"skillMd\": \"---\\nname: writing-plans\\ndescription: Create structured writing plans.\\n---\\n# Writing Plans\\n\\nYou help create structured writing plans.\",\n      \"agentFiles\": {},\n      \"scripts\": {},\n      \"resourceFiles\": [],\n      \"crossSkillRefs\": {}\n    }\n  }\n}\n","frontmatter":{"model":"anthropic/claude-sonnet-4-6","agentModels":{},"skillMd":"---\nname: brainstorming\ndescription: Brainstorming skill with cross-skill references.\n---\n# Brainstorming\n\nUse writing-plans to organize ideas.","agentFiles":{},"scripts":{},"resourceFiles":[],"crossSkillRefs":{"writing-plans":{"model":"openai/gpt-4o","agentModels":{},"skillMd":"---\nname: writing-plans\ndescription: Create structured writing plans.\n---\n# Writing Plans\n\nYou help create structured writing plans.","agentFiles":{},"scripts":{},"resourceFiles":[],"crossSkillRefs":{}}}},"isInternal":false,"tokens":186,"sizeBytes":663},{"name":"dg-skill.json","path":"agentspan/src/test/resources/skills/dg-skill.json","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/agentspan/src/test/resources/skills/dg-skill.json","title":"Skills Skill","category":"anthropic-skill","format":"json","content":"{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {\"gilfoyle\": \"openai/gpt-4o\"},\n  \"skillMd\": \"---\\nname: dg-skill\\ndescription: Adversarial code review.\\nmetadata:\\n  author: test\\n---\\n# DG Review\\n\\nDispatch gilfoyle, then dinesh. Repeat until convergence.\",\n  \"agentFiles\": {\n    \"gilfoyle\": \"# You Are Gilfoyle\\nReview code with precision.\",\n    \"dinesh\": \"# You Are Dinesh\\nDefend the code.\"\n  },\n  \"scripts\": {},\n  \"resourceFiles\": [\"comic-template.html\"],\n  \"crossSkillRefs\": {}\n}\n","frontmatter":{"model":"anthropic/claude-sonnet-4-6","agentModels":{"gilfoyle":"openai/gpt-4o"},"skillMd":"---\nname: dg-skill\ndescription: Adversarial code review.\nmetadata:\n  author: test\n---\n# DG Review\n\nDispatch gilfoyle, then dinesh. Repeat until convergence.","agentFiles":{"gilfoyle":"# You Are Gilfoyle\nReview code with precision.","dinesh":"# You Are Dinesh\nDefend the code."},"scripts":{},"resourceFiles":["comic-template.html"],"crossSkillRefs":{}},"isInternal":false,"tokens":160,"sizeBytes":500},{"name":"large-skill.json","path":"agentspan/src/test/resources/skills/large-skill.json","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/agentspan/src/test/resources/skills/large-skill.json","title":"Skills Skill","category":"anthropic-skill","format":"json","content":"{\n  \"model\": \"openai/gpt-4o-mini\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: large-skill\\ndescription: A large skill for testing section splitting.\\n---\\n# Conductor Skill\\n\\nYou are the Conductor orchestrator. Follow these core rules:\\n1. Always validate inputs before processing\\n2. Never skip error handling\\n3. Log all operations for audit trail\\n\\nThese rules apply to ALL sections below.\\n\\n## Workflow Definitions\\n\\nThis section covers workflow definitions in detail.\\n\\n### Rule 1 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Running Workflows\\n\\nThis section covers running workflows in detail.\\n\\n### Rule 1 for Running Workflows\\n\\nWhen handling running workflows scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Running Workflows\\n\\nWhen handling running workflows scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Running Workflows\\n\\nWhen handling running workflows scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Running Workflows\\n\\nWhen handling running workflows scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Running Workflows\\n\\nWhen handling running workflows scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Running Workflows\\n\\nWhen handling running workflows scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Running Workflows\\n\\nWhen handling running workflows scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Running Workflows\\n\\nWhen handling running workflows scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Running Workflows\\n\\nWhen handling running workflows scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Running Workflows\\n\\nWhen handling running workflows scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Running Workflows\\n\\nWhen handling running workflows scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Running Workflows\\n\\nWhen handling running workflows scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Running Workflows\\n\\nWhen handling running workflows scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Running Workflows\\n\\nWhen handling running workflows scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Running Workflows\\n\\nWhen handling running workflows scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Running Workflows\\n\\nWhen handling running workflows scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Running Workflows\\n\\nWhen handling running workflows scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Running Workflows\\n\\nWhen handling running workflows scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Running Workflows\\n\\nWhen handling running workflows scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Running Workflows\\n\\nWhen handling running workflows scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Running Workflows\\n\\nWhen handling running workflows scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Running Workflows\\n\\nWhen handling running workflows scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Running Workflows\\n\\nWhen handling running workflows scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Running Workflows\\n\\nWhen handling running workflows scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Running Workflows\\n\\nWhen handling running workflows scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Running Workflows\\n\\nWhen handling running workflows scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Running Workflows\\n\\nWhen handling running workflows scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Running Workflows\\n\\nWhen handling running workflows scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Running Workflows\\n\\nWhen handling running workflows scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Running Workflows\\n\\nWhen handling running workflows scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Running Workflows\\n\\nWhen handling running workflows scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Running Workflows\\n\\nWhen handling running workflows scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Running Workflows\\n\\nWhen handling running workflows scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Running Workflows\\n\\nWhen handling running workflows scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Running Workflows\\n\\nWhen handling running workflows scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Running Workflows\\n\\nWhen handling running workflows scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Running Workflows\\n\\nWhen handling running workflows scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Running Workflows\\n\\nWhen handling running workflows scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Running Workflows\\n\\nWhen handling running workflows scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Running Workflows\\n\\nWhen handling running workflows scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Running Workflows\\n\\nWhen handling running workflows scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Running Workflows\\n\\nWhen handling running workflows scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Running Workflows\\n\\nWhen handling running workflows scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Running Workflows\\n\\nWhen handling running workflows scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Running Workflows\\n\\nWhen handling running workflows scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Running Workflows\\n\\nWhen handling running workflows scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Running Workflows\\n\\nWhen handling running workflows scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Running Workflows\\n\\nWhen handling running workflows scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Running Workflows\\n\\nWhen handling running workflows scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Running Workflows\\n\\nWhen handling running workflows scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Running Workflows\\n\\nWhen handling running workflows scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Running Workflows\\n\\nWhen handling running workflows scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Running Workflows\\n\\nWhen handling running workflows scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Running Workflows\\n\\nWhen handling running workflows scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Running Workflows\\n\\nWhen handling running workflows scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Running Workflows\\n\\nWhen handling running workflows scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Running Workflows\\n\\nWhen handling running workflows scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Running Workflows\\n\\nWhen handling running workflows scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Running Workflows\\n\\nWhen handling running workflows scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Running Workflows\\n\\nWhen handling running workflows scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Running Workflows\\n\\nWhen handling running workflows scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Running Workflows\\n\\nWhen handling running workflows scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Running Workflows\\n\\nWhen handling running workflows scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Running Workflows\\n\\nWhen handling running workflows scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Running Workflows\\n\\nWhen handling running workflows scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Running Workflows\\n\\nWhen handling running workflows scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Running Workflows\\n\\nWhen handling running workflows scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Running Workflows\\n\\nWhen handling running workflows scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Running Workflows\\n\\nWhen handling running workflows scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Running Workflows\\n\\nWhen handling running workflows scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Running Workflows\\n\\nWhen handling running workflows scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Running Workflows\\n\\nWhen handling running workflows scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Running Workflows\\n\\nWhen handling running workflows scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Running Workflows\\n\\nWhen handling running workflows scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Running Workflows\\n\\nWhen handling running workflows scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Running Workflows\\n\\nWhen handling running workflows scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Running Workflows\\n\\nWhen handling running workflows scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Running Workflows\\n\\nWhen handling running workflows scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Running Workflows\\n\\nWhen handling running workflows scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Running Workflows\\n\\nWhen handling running workflows scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Error Handling\\n\\nThis section covers error handling in detail.\\n\\n### Rule 1 for Error Handling\\n\\nWhen handling error handling scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Error Handling\\n\\nWhen handling error handling scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Error Handling\\n\\nWhen handling error handling scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Error Handling\\n\\nWhen handling error handling scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Error Handling\\n\\nWhen handling error handling scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Error Handling\\n\\nWhen handling error handling scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Error Handling\\n\\nWhen handling error handling scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Error Handling\\n\\nWhen handling error handling scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Error Handling\\n\\nWhen handling error handling scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Error Handling\\n\\nWhen handling error handling scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Error Handling\\n\\nWhen handling error handling scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Error Handling\\n\\nWhen handling error handling scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Error Handling\\n\\nWhen handling error handling scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Error Handling\\n\\nWhen handling error handling scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Error Handling\\n\\nWhen handling error handling scenario 15, you must follow these steps carefully. First, validate ","isInternal":false,"tokens":10005,"sizeBytes":50000},{"name":"simple-skill.json","path":"agentspan/src/test/resources/skills/simple-skill.json","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/agentspan/src/test/resources/skills/simple-skill.json","title":"Skills Skill","category":"anthropic-skill","format":"json","content":"{\n  \"model\": \"openai/gpt-4o\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: simple-skill\\ndescription: A simple test skill.\\n---\\n# Simple Skill\\n\\nYou are a helpful assistant.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {}\n}\n","frontmatter":{"model":"openai/gpt-4o","agentModels":{},"skillMd":"---\nname: simple-skill\ndescription: A simple test skill.\n---\n# Simple Skill\n\nYou are a helpful assistant.","agentFiles":{},"scripts":{},"resourceFiles":[],"crossSkillRefs":{}},"isInternal":false,"tokens":82,"sizeBytes":264},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# CLAUDE.md — conductor (server repo)\n\nInstructions for Claude Code working in this repository.\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory or intuition. The workflow is: open the source → read what's there → write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nConcrete reason this matters: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Opening `WorkflowResource.java` first would have given the correct path (`POST /api/workflow/execute/{name}/{version}`) immediately.\n\n### For each content type, start here\n\n**REST endpoint or curl example**\n1. Open the controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method by its `@PostMapping`/`@GetMapping` annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body.\n4. Write the curl from what you just read.\n\n**CLI command or flag**\n1. Open `conductor-cli/cmd/*.go` (separate repo under this workspace).\n2. Find the `cobra.Command` for the subcommand and read its `Flags()` declarations.\n3. Write the example from what you just read — flag names, types, and defaults.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the SDK source file for the method you're documenting.\n2. Read the method signature and required parameters.\n3. If a working test exists for that method, use it as the starting point.\n4. Write from the signature — do not infer from the method name alone.\n\n**Expected output block**\n1. Get real output: run the command, or find it in test fixtures or CI logs.\n2. Paste verbatim. Do not construct output that \"looks right.\"\n3. For variable fields (IDs, timestamps), use annotated placeholders like `<workflow-id>`.\n\n**Editing an existing section**\n- Before changing anything, read every code block and command in the section.\n- Verify each one using the steps above, not just the block you plan to change.\n- Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI is unavailable:\n- Add `<!-- TODO: verify against live server -->` in the file.\n- Note it explicitly in the PR description.\n- Do not write an unverified example and leave it unmarked.\n\n### Key source locations\n\n| Content | Where to look |\n|---|---|\n| REST API routes | `rest/src/main/java/com/netflix/conductor/rest/controllers/` |\n| Workflow sync execution | `WorkflowResource.java` → `executeWorkflow()` at `@PostMapping(\"execute/{name}/{version}\")` |\n| Task routes | `TaskResource.java` |\n| CLI subcommands and flags | `conductor-cli/cmd/workflow.go`, `cmd/task.go`, etc. |\n\n## Other Guidelines\n\nSee [AGENTS.md](AGENTS.md) for full project conventions: code style, testing, dependency pinning, PR guidelines.\n","isInternal":false,"tokens":661,"sizeBytes":2889},{"name":"docs-writer.md","path":".claude/agents/docs-writer.md","rawUrl":"https://raw.githubusercontent.com/conductor-oss/conductor/HEAD/.claude/agents/docs-writer.md","title":"docs-writer","category":"subagent-persona","format":"markdown","content":"---\nname: docs-writer\ndescription: Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.\ntools: Read, Grep, Glob, Write, Edit, Bash\nmodel: inherit\n---\n\nYou are a technical documentation specialist for Conductor, an open-source workflow orchestration engine built at Netflix.\n\n## Your Role\n\nCreate clear, comprehensive, and accurate documentation for Conductor features, including:\n- Workflow definitions and task types\n- REST API endpoints and payloads\n- System architecture and components\n- Configuration options and database integrations\n- SDK usage examples (Java, Python, JavaScript, Go, C#)\n- Developer guides and tutorials\n\n## Documentation Process\n\n1. **Understand the Feature**\n   - Read relevant source code to understand implementation\n   - Identify key classes, methods, and APIs\n   - Test functionality if possible\n   - Review existing related documentation\n\n2. **Structure Documentation**\n   - Start with a clear overview/summary\n   - Include purpose and use cases\n   - Provide syntax and parameters\n   - Add practical examples\n   - Document edge cases and limitations\n   - Link to related documentation\n\n3. **Follow Conductor Style**\n   - Use clear, concise language\n   - Include code examples in relevant languages\n   - Use Markdown formatting consistently\n   - Add diagrams or JSON examples for workflows\n   - Follow existing documentation patterns in `/docs`\n\n4. **Quality Standards**\n   - Ensure technical accuracy\n   - Test all code examples\n   - Use proper terminology (workflows, tasks, workers, etc.)\n   - Include error handling examples\n   - Add troubleshooting sections when relevant\n\n## Key Conductor Concepts to Reference\n\n- **Workflows**: JSON-based orchestration definitions\n- **Tasks**: Units of work (HTTP, Lambda, Sub-workflow, etc.)\n- **Workers**: Services that execute tasks\n- **Task Definitions**: Reusable task configurations\n- **System Tasks**: Built-in task types\n- **Event Handlers**: Trigger workflows from events\n\n## Output Format\n\nProvide documentation in Markdown format suitable for the `/docs` directory, with:\n- Clear headings and sections\n- Code blocks with proper syntax highlighting\n- Tables for parameters and options\n- Links to related documentation\n- Version information when relevant\n\nAlways prioritize clarity and practical usefulness for developers using Conductor.\n","frontmatter":{"name":"docs-writer","description":"Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.","tools":"Read, Grep, Glob, Write, Edit, Bash","model":"inherit"},"isInternal":false,"tokens":486,"sizeBytes":2444}],"systemPromptSnippet":"<yakaai_skills repo=\"conductor-oss/conductor\">\n<!-- File: AGENTS.md (Tokens: ~2095 | Category: root-instruction) -->\n# AGENTS.md\n\nInstructions for AI coding agents working on the Conductor codebase.\n\n## Project Overview\n\nConductor is an open-source, distributed workflow orchestration engine designed for microservices.\nIt uses a pluggable architecture with interface-based abstractions for persistence, queuing, and indexing.\nThe project is built with Java 21 and uses Gradle as the build system.\n\n## Setup Commands\n\n| Command | Description |\n|---------|-------------|\n| `./gradlew build` | Build the entire project |\n| `./gradlew test` | Run all tests |\n| `./gradlew :module-name:test` | Run tests for a specific module |\n| `./gradlew spotlessApply` | Apply code formatting |\n| `./gradlew clean build` | Clean and rebuild |\n\n> **Important**: Always run `./gradlew spotlessApply` after making code changes to ensure consistent formatting.\n\n## Java Version References\n\n**Never link to a specific Java distribution** (e.g., Adoptium, Temurin, OpenJDK.org, Amazon Corretto) in docs, READMEs, or comments. Just say \"Java 21+\" and let users install it however they prefer.\n\n## Code Style\n\n- Use the Spotless plugin for uniform code formatting—always run before committing\n- Conductor is pluggable: when introducing new concepts, always use an **interface-based approach**\n- DAO interfaces **MUST** be defined in the `core` module\n- Implementation classes go in their respective persistence modules (e.g., `postgres-persistence`, `redis-persistence`)\n- Follow existing patterns in the codebase for consistency\n- Do not use emojis such as ✅ in the code, logs, or comments.  Keep comments professionals\n- When adding new logic, comment the algorithm, design etc.   \n\n## Architecture Guidelines\n\n### Module Structure\n\n- **core**: Contains interfaces, domain models, and core business logic\n- **persistence modules**: Implementations of DAO interfaces (postgres, redis, mysql, etc.)\n- **server**: Spring Boot application that brings everything together\n- **client**: SDK for interacting with Conductor\n- **ui**: React-based user interface\n\n### Key Patterns\n\n- DAOs are defined as interfaces in `core` and implemented in persistence modules\n- System tasks extend `WorkflowSystemTask` and are registered via Spring\n- Worker tasks use the `@WorkerTask` annotation for automatic discovery\n- Configuration is primarily done through Spring properties\n\n## Testing\n\n- **Avoid mocks**: Use real implementations whenever possible\n- **Test actual behavior**: Tests must verify real implementation logic, not duplicate it\n- **Use Testcontainers**: For database, cache, and other external dependencies\n- **Cover concurrency**: Ensure multi-threading scenarios are tested\n- **Run tests before submitting**: `./gradlew test` must pass\n\n### Test Locations\n\n- Unit tests: `src/test/java` in each module\n- Integration tests: `test-harness` module and `*-integration-test` modules\n- E2E tests: `e2e` module\n\n## PR Guidelines\n\n- Submit PRs against the `main` branch\n- Use clear, descriptive commit messages\n- Run `./gradlew spotlessApply` and `./gradlew test` before pushing\n- Add or update tests for any code changes\n- Keep PRs focused—one logical change per PR\n\n## Dependency Pinning\n\nSome dependencies have hard version constraints that **must not be auto-bumped**. These are marked with:\n\n```groovy\n// PINNED (#964): <reason>\n```\n\nThe issue number links back to https://github.com/conductor-oss/conductor/issues/964, which documents the full audit and upgrade path for each constraint.\n\n### What PINNED means\n\n`// PINNED (#964):` means the version is intentionally locked and upgrading it without understanding the constraint will break the build or cause a runtime failure. Do not bump a PINNED dependency as part of routine dependency updates or refactoring.\n\n### Current hard pins\n\n| Dependency | Pinned at | Why |\n|---|---|---|\n| `com.google.protobuf:protobuf-java` | `3.x` | 4.x + GraalVM polyglot 25.x causes Gradle to require `polyglot4`, which does not exist on Maven Central |\n| `com.google.protobuf:protoc` | `3.25.5` | Must match `grpc-protobuf:1.73.0`, which depends on protobuf-java 3.x |\n| `org.graalvm.*` (all 5 artifacts) | same version | All must share one version — mixing causes a `\"polyglot version X not compatible with Truffle Y\"` runtime error |\n| `redis.clients:jedis` in `redis-concurrency-limit` | `3.6.0` | `revJedis` (6.0.0) does not work with Spring Data Redis in that module |\n| `org.codehaus.jettison:jettison` | `strictly 1.5.4` | Gradle `strictly` constraint — no higher version has been validated |\n| `org.conductoross:conductor-client` in `test-harness` | `5.0.1` | Fat JAR classpath conflict with conductor-common; resolved via a stripped JAR task |\n| `org.awaitility:awaitility` in functional tests | `4.x` | e2e tests call `pollInterval(Duration)` added in Awaitility 4.0 |\n\n### Before bumping a PINNED dependency\n\n1. Read the comment carefully — it will name the incompatibility and often link to an upstream issue.\n2. Check whether the upstream blocker has been resolved (e.g., new grpc-java release, new GraalVM release).\n3. Test locally: `./gradlew clean build` plus `./gradlew test` in the affected modules.\n4. If bumping GraalVM, bump **all five** `org.graalvm.*` artifacts together using `revGraalVM` in `dependencies.gradle`.\n5. Update or remove the `// PINNED` comment once the constraint is lifted.\n\n### PINNED vs. version floors\n\nHard caps use `// PINNED (#964):`. Version floors — where a minimum is enforced but higher versions are always welcome — use one of two lowercase prefixes instead:\n\n```groovy\n// Security: CVE-2025-12183 — lz4-java minimum patched version\n// Compat: commons-lang3 3.18.0+ required by Testcontainers/commons-compress\n```\n\n- `// Security:` — minimum set to address a CVE or known vulnerability\n- `// Compat:` — minimum set for compatibility with another library or framework\n\nThese are grep-able (`grep \"// Security:\" **/*.gradle`, `grep \"// Compat:\" **/*.gradle`) but read as normal developer comments. Dependabot may raise these freely; no special review needed beyond the usual.\n\n## Security Considerations\n\n- Never commit secrets, API keys, or credentials\n- Be cautious with external dependencies—prefer well-maintained libraries\n- Follow secure coding practices for input validation and error handling\n- Review [SECURITY.md](SECURITY.md) for vulnerability reporting procedures\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory. Open the source first, read what's there, then write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nThis matters because plausible-looking docs can be silently wrong. Concretely: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Reading the controller first would have given the correct path immediately.\n\n### Workflow for each content type\n\n**REST API endpoint or curl example**\n1. Open the relevant controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method using its `@PostMapping`/`@GetMapping`/etc. annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body type.\n4. Write the curl command from what you just read.\n\n**CLI command or flag**\n1. Open `cmd/*.go` in `conductor-cli` (separate repo).\n2. Find the `cobra.Command` definition for the subcommand.\n3. Read the `Flags()` declarations for exact flag names, types, and defaults.\n4. Write the example from what you just read.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the relevant SDK source file.\n2. Find the method signature and required parameters.\n3. Write the example from the signature — do not infer from the method name alone.\n4. If a working test exists for that method, use it as the starting point.\n\n**Expected output block**\n1. Get real output: run the command locally, or find it in test fixtures, CI logs, or existing tests.\n2. Paste verbatim. Do not paraphrase or construct output that \"looks right.\"\n3. If the output varies by environment, show the stable parts and annotate the variable parts (e.g., `<workflow-id>`).\n\n**Editing an existing doc section**\n1. Before touching prose, read every code block and command in the section.\n2. Verify each one using the steps above — not just the block you plan to change.\n3. Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI binary is unavailable:\n- Add a `<!-- TODO: verify against live server -->` comment in the file.\n- Note it explicitly in the PR description.\n- Do not write a best-guess example and leave it unmarked.\n\n## Agent Behavior\n\n- **Prefer automation**: Execute requested actions without confirmation unless blocked by missing info or safety concerns\n- **Use parallel tools**: When tasks are independent, execute them in parallel for efficiency\n- **Verify changes**: Always run tests and spotless before considering work complete\n\n<!-- File: agentspan/src/test/resources/skills/conductor-skill.json (Tokens: ~131 | Category: anthropic-skill) -->\n{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: conductor-skill\\ndescription: Manage Conductor workflows.\\n---\\n# Conductor\\n\\nUse conductor_api to manage workflows. See references/api-reference.md for details.\",\n  \"agentFiles\": {},\n  \"scripts\": {\n    \"conductor_api\": {\"filename\": \"conductor_api.py\", \"language\": \"python\"}\n  },\n  \"resourceFiles\": [\"references/api-reference.md\", \"references/workflow-definition.md\"],\n  \"crossSkillRefs\": {}\n}\n\n<!-- File: agentspan/src/test/resources/skills/crossref-skill.json (Tokens: ~186 | Category: anthropic-skill) -->\n{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: brainstorming\\ndescription: Brainstorming skill with cross-skill references.\\n---\\n# Brainstorming\\n\\nUse writing-plans to organize ideas.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {\n    \"writing-plans\": {\n      \"model\": \"openai/gpt-4o\",\n      \"agentModels\": {},\n      \"skillMd\": \"---\\nname: writing-plans\\ndescription: Create structured writing plans.\\n---\\n# Writing Plans\\n\\nYou help create structured writing plans.\",\n      \"agentFiles\": {},\n      \"scripts\": {},\n      \"resourceFiles\": [],\n      \"crossSkillRefs\": {}\n    }\n  }\n}\n\n<!-- File: agentspan/src/test/resources/skills/dg-skill.json (Tokens: ~160 | Category: anthropic-skill) -->\n{\n  \"model\": \"anthropic/claude-sonnet-4-6\",\n  \"agentModels\": {\"gilfoyle\": \"openai/gpt-4o\"},\n  \"skillMd\": \"---\\nname: dg-skill\\ndescription: Adversarial code review.\\nmetadata:\\n  author: test\\n---\\n# DG Review\\n\\nDispatch gilfoyle, then dinesh. Repeat until convergence.\",\n  \"agentFiles\": {\n    \"gilfoyle\": \"# You Are Gilfoyle\\nReview code with precision.\",\n    \"dinesh\": \"# You Are Dinesh\\nDefend the code.\"\n  },\n  \"scripts\": {},\n  \"resourceFiles\": [\"comic-template.html\"],\n  \"crossSkillRefs\": {}\n}\n\n<!-- File: agentspan/src/test/resources/skills/large-skill.json (Tokens: ~10005 | Category: anthropic-skill) -->\n{\n  \"model\": \"openai/gpt-4o-mini\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: large-skill\\ndescription: A large skill for testing section splitting.\\n---\\n# Conductor Skill\\n\\nYou are the Conductor orchestrator. Follow these core rules:\\n1. Always validate inputs before processing\\n2. Never skip error handling\\n3. Log all operations for audit trail\\n\\nThese rules apply to ALL sections below.\\n\\n## Workflow Definitions\\n\\nThis section covers workflow definitions in detail.\\n\\n### Rule 1 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Workflow Definitions\\n\\nWhen handling workflow definitions scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Running Workflows\\n\\nThis section covers running workflows in detail.\\n\\n### Rule 1 for Running Workflows\\n\\nWhen handling running workflows scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Running Workflows\\n\\nWhen handling running workflows scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Running Workflows\\n\\nWhen handling running workflows scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Running Workflows\\n\\nWhen handling running workflows scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Running Workflows\\n\\nWhen handling running workflows scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Running Workflows\\n\\nWhen handling running workflows scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Running Workflows\\n\\nWhen handling running workflows scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Running Workflows\\n\\nWhen handling running workflows scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Running Workflows\\n\\nWhen handling running workflows scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Running Workflows\\n\\nWhen handling running workflows scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Running Workflows\\n\\nWhen handling running workflows scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Running Workflows\\n\\nWhen handling running workflows scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Running Workflows\\n\\nWhen handling running workflows scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Running Workflows\\n\\nWhen handling running workflows scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Running Workflows\\n\\nWhen handling running workflows scenario 15, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 16 for Running Workflows\\n\\nWhen handling running workflows scenario 16, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 17 for Running Workflows\\n\\nWhen handling running workflows scenario 17, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 18 for Running Workflows\\n\\nWhen handling running workflows scenario 18, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 19 for Running Workflows\\n\\nWhen handling running workflows scenario 19, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 20 for Running Workflows\\n\\nWhen handling running workflows scenario 20, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 21 for Running Workflows\\n\\nWhen handling running workflows scenario 21, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 22 for Running Workflows\\n\\nWhen handling running workflows scenario 22, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 23 for Running Workflows\\n\\nWhen handling running workflows scenario 23, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 24 for Running Workflows\\n\\nWhen handling running workflows scenario 24, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 25 for Running Workflows\\n\\nWhen handling running workflows scenario 25, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 26 for Running Workflows\\n\\nWhen handling running workflows scenario 26, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 27 for Running Workflows\\n\\nWhen handling running workflows scenario 27, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 28 for Running Workflows\\n\\nWhen handling running workflows scenario 28, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 29 for Running Workflows\\n\\nWhen handling running workflows scenario 29, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 30 for Running Workflows\\n\\nWhen handling running workflows scenario 30, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 31 for Running Workflows\\n\\nWhen handling running workflows scenario 31, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 32 for Running Workflows\\n\\nWhen handling running workflows scenario 32, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 33 for Running Workflows\\n\\nWhen handling running workflows scenario 33, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 34 for Running Workflows\\n\\nWhen handling running workflows scenario 34, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 35 for Running Workflows\\n\\nWhen handling running workflows scenario 35, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 36 for Running Workflows\\n\\nWhen handling running workflows scenario 36, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 37 for Running Workflows\\n\\nWhen handling running workflows scenario 37, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 38 for Running Workflows\\n\\nWhen handling running workflows scenario 38, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 39 for Running Workflows\\n\\nWhen handling running workflows scenario 39, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 40 for Running Workflows\\n\\nWhen handling running workflows scenario 40, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 41 for Running Workflows\\n\\nWhen handling running workflows scenario 41, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 42 for Running Workflows\\n\\nWhen handling running workflows scenario 42, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 43 for Running Workflows\\n\\nWhen handling running workflows scenario 43, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 44 for Running Workflows\\n\\nWhen handling running workflows scenario 44, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 45 for Running Workflows\\n\\nWhen handling running workflows scenario 45, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 46 for Running Workflows\\n\\nWhen handling running workflows scenario 46, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 47 for Running Workflows\\n\\nWhen handling running workflows scenario 47, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 48 for Running Workflows\\n\\nWhen handling running workflows scenario 48, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 49 for Running Workflows\\n\\nWhen handling running workflows scenario 49, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 50 for Running Workflows\\n\\nWhen handling running workflows scenario 50, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 51 for Running Workflows\\n\\nWhen handling running workflows scenario 51, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 52 for Running Workflows\\n\\nWhen handling running workflows scenario 52, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 53 for Running Workflows\\n\\nWhen handling running workflows scenario 53, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 54 for Running Workflows\\n\\nWhen handling running workflows scenario 54, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 55 for Running Workflows\\n\\nWhen handling running workflows scenario 55, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 56 for Running Workflows\\n\\nWhen handling running workflows scenario 56, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 57 for Running Workflows\\n\\nWhen handling running workflows scenario 57, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 58 for Running Workflows\\n\\nWhen handling running workflows scenario 58, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 59 for Running Workflows\\n\\nWhen handling running workflows scenario 59, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 60 for Running Workflows\\n\\nWhen handling running workflows scenario 60, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 61 for Running Workflows\\n\\nWhen handling running workflows scenario 61, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 62 for Running Workflows\\n\\nWhen handling running workflows scenario 62, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 63 for Running Workflows\\n\\nWhen handling running workflows scenario 63, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 64 for Running Workflows\\n\\nWhen handling running workflows scenario 64, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 65 for Running Workflows\\n\\nWhen handling running workflows scenario 65, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 66 for Running Workflows\\n\\nWhen handling running workflows scenario 66, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 67 for Running Workflows\\n\\nWhen handling running workflows scenario 67, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 68 for Running Workflows\\n\\nWhen handling running workflows scenario 68, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 69 for Running Workflows\\n\\nWhen handling running workflows scenario 69, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 70 for Running Workflows\\n\\nWhen handling running workflows scenario 70, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 71 for Running Workflows\\n\\nWhen handling running workflows scenario 71, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 72 for Running Workflows\\n\\nWhen handling running workflows scenario 72, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 73 for Running Workflows\\n\\nWhen handling running workflows scenario 73, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 74 for Running Workflows\\n\\nWhen handling running workflows scenario 74, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 75 for Running Workflows\\n\\nWhen handling running workflows scenario 75, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 76 for Running Workflows\\n\\nWhen handling running workflows scenario 76, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 77 for Running Workflows\\n\\nWhen handling running workflows scenario 77, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 78 for Running Workflows\\n\\nWhen handling running workflows scenario 78, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 79 for Running Workflows\\n\\nWhen handling running workflows scenario 79, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 80 for Running Workflows\\n\\nWhen handling running workflows scenario 80, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n\\n## Error Handling\\n\\nThis section covers error handling in detail.\\n\\n### Rule 1 for Error Handling\\n\\nWhen handling error handling scenario 1, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 2 for Error Handling\\n\\nWhen handling error handling scenario 2, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 3 for Error Handling\\n\\nWhen handling error handling scenario 3, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 4 for Error Handling\\n\\nWhen handling error handling scenario 4, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 5 for Error Handling\\n\\nWhen handling error handling scenario 5, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 6 for Error Handling\\n\\nWhen handling error handling scenario 6, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 7 for Error Handling\\n\\nWhen handling error handling scenario 7, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 8 for Error Handling\\n\\nWhen handling error handling scenario 8, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 9 for Error Handling\\n\\nWhen handling error handling scenario 9, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 10 for Error Handling\\n\\nWhen handling error handling scenario 10, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 11 for Error Handling\\n\\nWhen handling error handling scenario 11, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 12 for Error Handling\\n\\nWhen handling error handling scenario 12, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 13 for Error Handling\\n\\nWhen handling error handling scenario 13, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 14 for Error Handling\\n\\nWhen handling error handling scenario 14, you must follow these steps carefully. First, validate all inputs. Second, check permissions. Third, execute the operation. Finally, verify the result and log the outcome for compliance tracking.\\n\\n### Rule 15 for Error Handling\\n\\nWhen handling error handling scenario 15, you must follow these steps carefully. First, validate\n\n<!-- File: agentspan/src/test/resources/skills/simple-skill.json (Tokens: ~82 | Category: anthropic-skill) -->\n{\n  \"model\": \"openai/gpt-4o\",\n  \"agentModels\": {},\n  \"skillMd\": \"---\\nname: simple-skill\\ndescription: A simple test skill.\\n---\\n# Simple Skill\\n\\nYou are a helpful assistant.\",\n  \"agentFiles\": {},\n  \"scripts\": {},\n  \"resourceFiles\": [],\n  \"crossSkillRefs\": {}\n}\n\n<!-- File: CLAUDE.md (Tokens: ~661 | Category: claude-rule) -->\n# CLAUDE.md — conductor (server repo)\n\nInstructions for Claude Code working in this repository.\n\n## Writing Documentation\n\nDocumentation in this project is **derived from source**, not composed from memory or intuition. The workflow is: open the source → read what's there → write the doc from what you find. The source is the spec; the doc is a rendering of it.\n\nConcrete reason this matters: a curl equivalent for `conductor workflow start --sync` was once written as `POST /api/workflow/{name}/run` — an endpoint that does not exist. Opening `WorkflowResource.java` first would have given the correct path (`POST /api/workflow/execute/{name}/{version}`) immediately.\n\n### For each content type, start here\n\n**REST endpoint or curl example**\n1. Open the controller: `rest/src/main/java/com/netflix/conductor/rest/controllers/`\n2. Find the method by its `@PostMapping`/`@GetMapping` annotation — copy the path literally.\n3. Read the method signature for query params, path variables, and request body.\n4. Write the curl from what you just read.\n\n**CLI command or flag**\n1. Open `conductor-cli/cmd/*.go` (separate repo under this workspace).\n2. Find the `cobra.Command` for the subcommand and read its `Flags()` declarations.\n3. Write the example from what you just read — flag names, types, and defaults.\n\n**SDK code example (Python, JS, Java, Go)**\n1. Open the SDK source file for the method you're documenting.\n2. Read the method signature and required parameters.\n3. If a working test exists for that method, use it as the starting point.\n4. Write from the signature — do not infer from the method name alone.\n\n**Expected output block**\n1. Get real output: run the command, or find it in test fixtures or CI logs.\n2. Paste verbatim. Do not construct output that \"looks right.\"\n3. For variable fields (IDs, timestamps), use annotated placeholders like `<workflow-id>`.\n\n**Editing an existing section**\n- Before changing anything, read every code block and command in the section.\n- Verify each one using the steps above, not just the block you plan to change.\n- Fix anything you find while you're there.\n\n### When you can't verify\n\nIf a running server or CLI is unavailable:\n- Add `<!-- TODO: verify against live server -->` in the file.\n- Note it explicitly in the PR description.\n- Do not write an unverified example and leave it unmarked.\n\n### Key source locations\n\n| Content | Where to look |\n|---|---|\n| REST API routes | `rest/src/main/java/com/netflix/conductor/rest/controllers/` |\n| Workflow sync execution | `WorkflowResource.java` → `executeWorkflow()` at `@PostMapping(\"execute/{name}/{version}\")` |\n| Task routes | `TaskResource.java` |\n| CLI subcommands and flags | `conductor-cli/cmd/workflow.go`, `cmd/task.go`, etc. |\n\n## Other Guidelines\n\nSee [AGENTS.md](AGENTS.md) for full project conventions: code style, testing, dependency pinning, PR guidelines.\n\n<!-- File: .claude/agents/docs-writer.md (Tokens: ~486 | Category: subagent-persona) -->\n---\nname: docs-writer\ndescription: Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.\ntools: Read, Grep, Glob, Write, Edit, Bash\nmodel: inherit\n---\n\nYou are a technical documentation specialist for Conductor, an open-source workflow orchestration engine built at Netflix.\n\n## Your Role\n\nCreate clear, comprehensive, and accurate documentation for Conductor features, including:\n- Workflow definitions and task types\n- REST API endpoints and payloads\n- System architecture and components\n- Configuration options and database integrations\n- SDK usage examples (Java, Python, JavaScript, Go, C#)\n- Developer guides and tutorials\n\n## Documentation Process\n\n1. **Understand the Feature**\n   - Read relevant source code to understand implementation\n   - Identify key classes, methods, and APIs\n   - Test functionality if possible\n   - Review existing related documentation\n\n2. **Structure Documentation**\n   - Start with a clear overview/summary\n   - Include purpose and use cases\n   - Provide syntax and parameters\n   - Add practical examples\n   - Document edge cases and limitations\n   - Link to related documentation\n\n3. **Follow Conductor Style**\n   - Use clear, concise language\n   - Include code examples in relevant languages\n   - Use Markdown formatting consistently\n   - Add diagrams or JSON examples for workflows\n   - Follow existing documentation patterns in `/docs`\n\n4. **Quality Standards**\n   - Ensure technical accuracy\n   - Test all code examples\n   - Use proper terminology (workflows, tasks, workers, etc.)\n   - Include error handling examples\n   - Add troubleshooting sections when relevant\n\n## Key Conductor Concepts to Reference\n\n- **Workflows**: JSON-based orchestration definitions\n- **Tasks**: Units of work (HTTP, Lambda, Sub-workflow, etc.)\n- **Workers**: Services that execute tasks\n- **Task Definitions**: Reusable task configurations\n- **System Tasks**: Built-in task types\n- **Event Handlers**: Trigger workflows from events\n\n## Output Format\n\nProvide documentation in Markdown format suitable for the `/docs` directory, with:\n- Clear headings and sections\n- Code blocks with proper syntax highlighting\n- Tables for parameters and options\n- Links to related documentation\n- Version information when relevant\n\nAlways prioritize clarity and practical usefulness for developers using Conductor.\n</yakaai_skills>"}