docs(orchestrator): Move the guide to a dedicated orchestrator/README.md file

[rm3l]

Description

Follow-up to #64 (comment)

Similar to the 'developer-lightspeed' structure, this would make it easy to find and super obvious as a starting place for the user.

Which issue(s) does this PR fix or relate to

—

PR acceptance criteria

• Tests
• Documentation

How to test changes / Special notes to the reviewer

Summary by Sourcery

Move the Orchestrator workflow guide into its own top-level README and update references accordingly

Enhancements:

• Relocate the orchestrator guide from docs/orchestrator-workflow-guide.md to orchestrator/README.md
• Refresh internal compose and example links in the moved guide to use correct relative paths
• Update the main README to point to the new orchestrator README location

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR centralizes the orchestrator workflow guide into a dedicated README by relocating the file and updating all relative links to reflect the new structure.

File-Level Changes

Change	Details	Files
Relocate orchestrator workflow guide to its own README	moved orchestrator-workflow-guide.md to orchestrator/README.md updated main README navigation link to point to the new orchestrator/README.md	orchestrator/docs/orchestrator-workflow-guide.md orchestrator/README.md README.md
Adjust relative paths within the relocated guide	fixed compose.yaml references to ../compose.yaml and ./compose.yaml as needed updated workflow-examples directory and README links to use './workflow-examples'	orchestrator/README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}