Switch discussion-task-miner from repo-memory to cache-memory

[Copilot]

Addresses three review comments on the discussion-task-miner workflow requesting migration from repo-memory to cache-memory, removal of the features block, and updated memory layout documentation.

Changes

• tools section: Replace repo-memory (with branch/file-glob config) with cache-memory: true
• features block: Remove copilot-requests: true entirely
• Memory layout: Update Step 1 and Step 6 to describe a single cache-memory JSON object instead of bash heredoc file-writes; update Output Requirements to reference cache-memory

# Before
tools:
  repo-memory:
    branch-name: memory/discussion-task-miner
    file-glob: ["memory/discussion-task-miner/*.json", ...]
    max-file-size: 102400

features:
  copilot-requests: true

# After
tools:
  cache-memory: true

The cache-memory JSON layout consolidates discussions_processed and extracted_tasks into a single object, replacing the previous multi-file approach.

---

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

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/github/gh-aw/git/ref/tags/v0.51.6
  • Triggering command: /usr/bin/gh gh api /repos/github/gh-aw/git/ref/tags/v0.51.6 --jq .object.sha (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)