fix(cloud-task): bundle a local skill tagged on the first message

[tatoalo]

Problem

starting a cloud task whose first message is a local-skill slash command failed, the skill's bundle was never uploaded, so the sandbox had no such skill.
The initial task-creation path did not resolved a typed local-skill command into the skill tag

Changes

resolve a leading local-skill slash command into a <skill …/> tag in the initial task-creation path, mirroring what the follow-up path already does

[tatoalo]

• fix(agent): apply local-skill context on the codex adapter #3058
• feat(skills): auto-bundle declared skill dependencies in cloud runs #3057
• fix(cloud-task): bundle a local skill tagged on the first message #3056 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit aad38ac.}

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(cloud-task): bundle a local skill ta..." | Re-trigger Greptile}

[github-actions]

Focused bug fix that adds skill-bundle resolution on first cloud message, mirroring the identical pattern already used in the session service host. Single implementation of the interface, tests cover the happy path and pass-through cases, and the one substantive bot review comment was addressed.

[greptile-apps]

_{Reviews (2): Last reviewed commit: "fix(cloud-task): bundle a local skill ta..." | Re-trigger Greptile}

[richardsolomou]

@tatoalo this is still happening for me on latest version