Suggested test: copilot/repo-memory-basic

## Motivation

Several recent gh-aw PRs touch `repo-memory` behaviour (github/gh-aw#60789 temporary-ID substitution before persistence, github/gh-aw#60663 JSONL union-merge conflict policy). There is currently no `.github/workflows/test-*.md` exercising `tools.repo-memory` end-to-end — only `test-copilot-restore-memory-custom-job.md` covers `cache-memory` + `restore-memory` in a custom job, which is a different feature.

## Proposed test

- **Workflow file**: `test-copilot-repo-memory.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue` (report what was found/written in memory)
- **Variant**: standard

## Minimal test prompt sketch

Enable `tools.repo-memory: true` (or a scoped `branch-name`). Ask the agent to read any existing entry file under `/tmp/gh-aw/repo-memory-default/memory/default/`, append a new line noting the run number, and then create an issue summarizing what was read/written. Run twice across dispatches to confirm the branch persists and accumulates content (regression coverage for the union-merge/JSONL conflict policy would need concurrent runs, which is a stretch goal — start with a single-run smoke test).

## New fixtures or secrets needed

None — `repo-memory` auto-creates its own branch (e.g. `memory/default`) in `githubnext/gh-aw-test`; no new fixture repo required. `clean.sh` may need a follow-up note to prune stray `memory/*` branches, but that's out of scope for this issue.

## Notes

Distinct from `test-copilot-restore-memory-custom-job` (cache-memory + custom job `restore-memory:` flag). No open suggestion currently covers plain `repo-memory` usage; `copilot/cache-memory-concurrent-merge` (#15602) is about cache-memory concurrency, not repo-memory.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/34948148565) · copilot · auto · 151.2 AIC · ⌖ 5.93 AIC · ⊞ 8.4K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)

Create .github/workflows/test-copilot-repo-memory.md, using test-copilot-restore-memory-custom-job.md as the nearby example. Configure a workflow_dispatch copilot run with repo-memory enabled, have it read and append an entry under /tmp/gh-aw/repo-memory-default/memory/default/, and create an issue summarizing the result. Dispatch it twice; done means the memory branch persists and accumulates content without new fixtures or secrets.

Written by the indexing model from the issue text.