gh-aw binary not present in runner working directory for portfolio-analyst

[heaversm]

gh-aw binary is not present in the runner's working directory. The setup action installs scripts to /opt/gh-aw/actions/ but doesn't place a gh-aw CLI binary in the workspace.

Environment

• gh-aw version: 0.50.7 (upgraded from 0.47.4)
• Engine: claude
• Repository: private

Steps to reproduce

1. gh aw add-wizard https://github.com/github/gh-aw/blob/v0.45.5/.github/workflows/portfolio-analyst.md
2. Workflow installs and triggers automatically
3. Workflow run fails

Errors

Run 1 (v0.47.4)

The activation job fails during "Interpolate variables and render templates":

Runtime import file not found:
aw/imports/github/gh-aw/852cb06ad52958b402ed982b69957ffc57ca0619/.github_workflows_shared_reporting.md

The import files referenced in the workflow were not committed to the repo during add-wizard.

Run 2 (v0.50.7, after manually adding import files)

Import issue resolved, but the agent job fails at the "Download logs" step:

./gh-aw: No such file or directory

The workflow step runs ./gh-aw logs --start-date -30d ... but the gh-aw binary is not present in the
runner's working directory. The setup action installs scripts to /opt/gh-aw/actions/ but doesn't place a
gh-aw CLI binary in the workspace.

Expected behavior

The add-wizard command should:

1. Include all required import files in the PR it creates
2. The workflow should have access to the gh-aw CLI during execution

[pelikhan]

Ensure that the agentic-workflows tool uses the container MCP in release mode.

[heaversm]

1. Import files not included by add-wizard: The add command should bundle shared imports but didn't in earlier versions. It worked in v0.52.1, so this may be fixed now(?)

2. ./gh-aw relative path in the step — The workflow template uses ./gh-aw logs but the binary isn't placed in the working directory. The lock file compiler now adds a step to copy it to /opt/gh-aw/gh-aw, but the pre-agent step still references ./gh-aw. This is still a bug in the workflow template itself.

3. trial can't resolve imports — Trial mode re-fetches from the source repo and fails because shared imports aren't at the expected path. This makes trial broken for any workflow with imports.

End result:

• v0.52.1 fixed the import bundling
• The ./gh-aw relative path in the steps: block may still fail (you'll know after the run)
• trial mode doesn't work for workflows with imports

From Claude Code:

Exactly as we suspected — the ./gh-aw: No such file or directory bug from your original issue. The steps: block runs ./gh-aw logs before the agent job installs the binary.

This is a bug in the portfolio-analyst workflow template itself — it references ./gh-aw in a pre-agent step, but the binary only gets installed later in the agent job. You should update your GitHub
issue with this confirmation: the container MCP fix worked, but the steps: section still uses a relative path to a binary that doesn't exist at that point in the workflow.

The fix would need to come from the gh-aw maintainers — either making the steps: block use the installed binary path, or installing gh-aw earlier in the workflow. This isn't something you can work
around locally since the steps: block is baked into the lock file by the compiler.