Fix repo-memory folder path to use branch name and update glob pattern matching

[Copilot]

The push_repo_memory.cjs script was constructing the destination path using the memory ID instead of the branch name, causing all repo-memory branches to store files at memory/default/ regardless of their actual branch name. Additionally, file-glob patterns were being validated against artifact-relative paths instead of branch-relative paths.

Changes:

• Updated push_repo_memory.cjs line 248 to use branchName instead of memoryId:

  // Before: files always stored at memory/default/
  const destMemoryPath = path.join(workspaceDir, "memory", memoryId);
  
  // After: files stored at branch name path
  const destMemoryPath = path.join(workspaceDir, branchName);

• Updated glob pattern matching in push_repo_memory.cjs to test against the full branch-relative path:

  // Now tests patterns against "memory/code-metrics/file.json" 
  // instead of just "file.json"
  const branchRelativePath = path.join(branchName, relativeFilePath).replace(/\\/g, "/");

• Updated file-glob patterns in 21 workflow files to include the full branch path structure:

  • *.json → memory/code-metrics/*.json
  • metrics/** → memory/meta-orchestrators/metrics/**
  • Campaign patterns updated to include branch prefix

• Updated docs/src/content/docs/reference/memory.md to document that file-glob patterns must include the full branch path

Impact:

Branch Name	Old Path	New Path	Glob Pattern Example
memory/code-metrics	memory/default/	memory/code-metrics/	memory/code-metrics/*.json
memory/audit-workflows	memory/default/	memory/audit-workflows/	memory/audit-workflows/*.json

This makes the folder structure semantically aligned with the branch naming convention and ensures glob patterns correctly validate files at their actual storage location within the branch.

Testing:

• ✅ All 126 workflows compiled successfully
• ✅ JavaScript tests pass (50 tests in push_repo_memory.test.cjs)
• ✅ Go unit tests pass
• ✅ Glob pattern matching correctly validates branch-relative paths

Original prompt

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

Make sure the matching account for the relative folder created for the memory

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pelikhan]

@copilot Glob match must account for memory/id folder path

[Copilot]

@copilot Glob match must account for memory/id folder path

Fixed in commit 325f9af. The glob pattern matching now accounts for the full branch path structure. Updated push_repo_memory.cjs to test patterns against the branch-relative path (e.g., "memory/code-metrics/file.json") and updated all workflow file-glob patterns to include the branch path.