[deep-report] Actually land the DeepReport repo-memory path fix from #51172 (closed without merged change; still 2-level path, still 1 commit [Content truncated due to length]

[github-actions]

This is a reopening with a concrete fix location, not a rediscovery. #51172 diagnosed the exact bug (slashless file-glob: ["*.md"] compiles to matchSubfolderRoot, which only matches paths exactly one directory deep) and was closed 2026-08-07 — but the GitHub API timeline shows it was closed directly with no linked merged PR (closed event, source: null), and the source file was never actually changed.

Confirmed still broken today (2026-08-10)

• .github/workflows/deep-report.md (current main) still tells the agent to read/write at:
  • Line 165: `/tmp/gh-aw/repo-memory/default/memory/deep-report/` (read)
  • Line 217: memory/deep-report/processed-discussions.json (read)
  • Line 247: `/tmp/gh-aw/repo-memory/default/memory/deep-report/` (write)
  • This is two directory levels under the repo-memory root (memory/ + deep-report/), which the slashless *.md glob (file-glob: ["*.md"] at line 76) does not match — it only matches one level (<dir>/<file>.md).
• file-glob is still ["*.md"] only — Fix DeepReport repo-memory persistence: depth-2 paths silently dropped by file glob #51172 said it would add "*.json" (needed for processed-discussions.json / extracted-tasks.json, referenced at lines 217/227) but that change is also not present.
• The memory/deep-report git branch (where this repo-memory is actually stored) has exactly one commit, e50c816, dated 2026-04-03, "Update repo memory from workflow run 23950425855" — despite this workflow running daily since then and multiple cycles (including 2026-08-07s DeepReport Intelligence Briefing - 2026-08-07 #51116) explicitly claiming to have "rewritten all four memory files with fresh data."

Fix

In .github/workflows/deep-report.md:

1. Change the read/write paths at lines 165, 217, 247 (and the mining-step reference at 227) from /tmp/gh-aw/repo-memory/default/memory/deep-report/ to /tmp/gh-aw/repo-memory/default/deep-report/ (drop the redundant memory/ prefix — the git branch is already named memory/deep-report via the repo-memory.branch-name frontmatter at line 74; the local folder path doesnt need to repeat it).
2. Add "*.json" to file-glob at line 76: file-glob: ["*.md", "*.json"].
3. Recompile: gh aw compile (or equivalent) to regenerate deep-report.lock.yml.
4. Verify next cycle: confirm the memory/deep-report branch gets a new commit dated after this fix lands — that is the only reliable signal this is actually fixed (see companion process issue on requiring verified evidence before closing this class of bug).

Data source

DeepReport Intelligence Briefing, 2026-08-10. Confirmed via direct read of .github/workflows/deep-report.md on main, git log on the checked-out memory/deep-report branch (1 commit total), and gh api repos/github/gh-aw/issues/51172/timeline (closed with no source PR).

Suggested Agent: deep-report maintainer / general code-quality agent
Estimated Effort: Quick (< 1 hour) — 3-line frontmatter/prompt change + recompile

Generated by 🔬 Deep Report · agent · 237.7 AIC · ⌖ 55.3 AIC · ⊞ 11.3K · ◷

• expires on Aug 12, 2026, 7:12 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I identified this as a strong candidate for automated resolution and requested assignment to the Copilot coding agent.

This looks isolated to the Deep Report workflow source and its compiled lockfile, with a concrete repro and fix location already documented.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · gpt54 · 4.86 AIC · ⌖ 6.47 AIC · ⊞ 10.5K · ◷