Fix repo memory artifact path resolution in push_repo_memory.cjs

[Copilot]

The push_repo_memory job was failing to find downloaded artifacts because it incorrectly assumed a nested directory structure that doesn't exist.

Problem

When GitHub Actions uploads an artifact from /tmp/gh-aw/repo-memory/default, it stores files at the artifact root. On download to the same path, the script incorrectly looked for files at:

// Incorrect: assumed nested structure
const sourceMemoryPath = path.join(artifactDir, "memory", memoryId);
// Expected: /tmp/gh-aw/repo-memory/default/memory/default/ ❌

This path doesn't exist. The artifact content is directly at artifactDir.

Changes

• actions/setup/js/push_repo_memory.cjs: Changed line 41 to use artifactDir directly instead of constructing a nested path

// Correct: artifactDir IS the memory directory
const sourceMemoryPath = artifactDir;

This allows workflows using repo-memory (like daily-code-metrics) to successfully persist state to git branches.

Original prompt

Reference: https://github.com/githubnext/gh-aw/actions/runs/20541879130/job/59007544061#step:7:1

Investigate why the repo memory artifact was not found.

Custom agent used: debug-agentic-workflow
Debug and refine agentic workflows using gh-aw CLI tools - analyze logs, audit runs, and improve workflow performance

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.