fix: align release MCP task root

[Ayleovelle]

Summary

• align the release MCP task root with the validated CI root
• keep embedded Fast Lane cache projections within the Windows path budget

Evidence

• release MCP projections were 245 and 241 characters (>240)
• CI-aligned projections are 239 and 235 characters
• the two exact failed tests now pass (2 passed)
• diff check passed

This completes the same root-cause correction surfaced by release run 32884992045.

Summary by Sourcery

Bug Fixes:

• Align the release MCP task root with the CI-validated path to keep generated cache paths within the Windows path-length limit.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the release MCP runtime root to match the CI-validated task root, reducing embedded Fast Lane cache projection lengths from over 240 characters to within the Windows path budget.

Flow diagram for the aligned release MCP task root

flowchart LR
    Temp[RUNNER_TEMP] --> ReleaseRoot[release MCP task root]
    ReleaseRoot --> Runtime[mcp-runtime]
    Runtime --> Caches[tmp, pycache, uv-cache]
    ReleaseRoot -. matches .-> CIRoot[CI-validated task root]
    Runtime --> Projection[Embedded Fast Lane cache projections]
    Projection --> Budget[Windows path length <= 240]

Loading

File-Level Changes

Change	Details	Files
Align the release workflow’s MCP task-local root with the CI-validated path to keep generated Windows paths within the 240-character limit.	Replace the release-specific temporary root directory name with the shared task root. Continue creating the temporary, pycache, and uv-cache projections beneath the corrected MCP runtime root.	.github/workflows/release.yml

---

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 - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

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.}