Expose uv in workspace for awf

[github-actions]

Summary

• copy the installed uv binary into a workspace-visible bin directory after setup
• add the workspace bin directory to GITHUB_PATH so the awf container can resolve uv on PATH
• place the updated fragment under github/workflows/gh-aw-fragments/ per workflow-edit guardrails (maintainers should sync to .github/workflows/gh-aw-fragments/runtime-setup.md and recompile lockfiles)

Testing

• make lint

Related: #137

• Fixes Uv not in path after setup #137

AI generated by Issue Assistant

[github-actions]

Summary: CI failed in Verify compiled workflows because make compile leaves the working tree dirty with updated .github/workflows/gh-aw-*.lock.yml files.

Evidence (source change requiring a recompile):

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

  - name: Expose uv in workspace
    if: hashFiles('pyproject.toml', 'uv.lock') != ''
    ...

Recommended fix:

1. Run make compile.
2. Commit the regenerated .github/workflows/gh-aw-*.lock.yml files.

Tests: Not run locally (CI failure based on workflow logs).

---

What is this? | From workflow: PR Checks Fixer

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

CI failed in Verify compiled workflows because make compile left the working tree dirty (lock files changed and a new .github/workflows/trigger-release-update.yml was generated), so the compiled workflows are out of date.

Recommended fix: run make compile and commit the resulting .github/workflows/*.lock.yml updates plus the generated trigger workflow (and any other updated workflow files such as agentics-maintenance.yml).

Tests: not run locally (failure reproduced from workflow logs).

---

What is this? | From workflow: PR Checks Fixer

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.