Uv not in path after setup

[strawgate]

Let's fix this, we currently run UV setup but it doesn't appear to be in the path when the agent tries to run UV, the agent has to do it by wrapping it in python ...

[github-actions]

The workflows install uv on the runner but run the agent inside the awf container without placing uv in a container-visible path, so uv won’t be on PATH for the agent unless it’s installed into the workspace. Recommend installing uv into a workspace path (or copying the binary there) and exporting that path before the agent step, then recompile the lock workflows.

Findings

• The runtime setup fragment only runs setup-uv (no explicit install dir or PATH wiring beyond the action defaults):

.github/workflows/gh-aw-fragments/runtime-setup.md:35-37
- name: Setup uv
  if: hashFiles('pyproject.toml', 'uv.lock') != ''
  uses: astral-sh/setup-uv@v5

• The agent runs inside the awf container after setup steps, with no explicit step to move uv into the workspace or a shared path:

.github/workflows/gh-aw-issue-triage.lock.yml:872-879
- name: Execute GitHub Copilot CLI
  run: |
    sudo -E awf ... --container-workdir "\$\{GITHUB_WORKSPACE}" ...

• The workflow shim imports the runtime setup fragment for all agentic workflows, so any fix should live there:

.github/workflows/gh-aw-issue-triage.md:3-6
imports:
  - gh-aw-fragments/elastic-tools.md
  - gh-aw-fragments/runtime-setup.md

Verification

No runtime tests executed; inspection only.

Detailed Action Plan

1. Update .github/workflows/gh-aw-fragments/runtime-setup.md:35-37 to install uv into a workspace-visible directory (e.g., set an UV_INSTALL_DIR under $\{\{ github.workspace }} if supported by setup-uv, or add a follow-up step that copies $(command -v uv) into a $\{\{ github.workspace }}/.gh-aw-tools/bin directory). Add that directory to GITHUB_PATH so subsequent steps (and the container) see it.
2. Recompile workflows (make compile) so all .github/workflows/gh-aw-*.lock.yml files include the updated runtime setup.
3. Validate in a test run by checking command -v uv and uv --version in a pre-agent step, then have the agent run uv --version to confirm the container sees it.

Related Items

Type	Link	Relevance
Issue	#117	Recent discussion about uv usage/behavior in workflows
File	.github/workflows/gh-aw-fragments/runtime-setup.md:35-37	Current setup-uv step definition
File	.github/workflows/gh-aw-issue-triage.lock.yml:872-879	awf container execution step

---

What is this? | From workflow: Issue Triage Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #137

[strawgate]

/ai make a pr

[github-actions]

PR created with the runtime-setup update.

Summary:

• Add a post-setup-uv step that copies the installed uv binary into a workspace-visible bin dir and appends it to GITHUB_PATH.
• Updated fragment is staged under github/workflows/gh-aw-fragments/runtime-setup.md per workflow-edit guardrails; please sync it to .github/workflows/gh-aw-fragments/runtime-setup.md and recompile lockfiles.

Testing:

• make lint

---

What is this? | From workflow: Issue Assistant

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #137