Fix repo-memory path validation: remove branch name nesting

[Copilot]

Campaign workflows were failing with path validation errors because files were being nested under a subdirectory matching the branch name instead of being placed at the branch root.

Error: File does not match allowed patterns: memory/campaigns/go-file-size-reduction-project64/metrics/2025-12-31.json
Error: Allowed patterns: go-file-size-reduction-project64/**

Changes

actions/setup/js/push_repo_memory.cjs

• Remove nested directory creation when copying files to checked-out branch
• Files now placed at branch root instead of ${workspaceDir}/${branchName}/

- const destMemoryPath = path.join(workspaceDir, branchName);
- fs.mkdirSync(destMemoryPath, { recursive: true });
+ const destMemoryPath = workspaceDir;

Impact

Before: Branch memory/campaigns contained memory/campaigns/go-file-size-reduction-project64/...
After: Branch memory/campaigns contains go-file-size-reduction-project64/...

Glob patterns now match correctly against relative paths from the artifact root, fixing validation failures in all workflows using branch-based repo-memory.

Original prompt

See campaign run: https://github.com/githubnext/gh-aw/actions/runs/20618086805/job/59214719890
Fix error by comparing relative paths as the pattern expects:
Error: File does not match allowed patterns: memory/campaigns/go-file-size-reduction-project64/metrics/2025-12-31.json
Error: Allowed patterns: go-file-size-reduction-project64/**

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.