[deep-report] Instrument repo-memory / cache-memory writes with size and retention telemetry

[github-actions]

Description

The arXiv Research discussion #57652 (2026-09-01) surfaced "Measure Before You Manage: Evaluating Agent Working Memory in Coding Agents," which recommends instrumenting memory systems with telemetry on the size, retention, and semantic role of stored objects. gh-aw already has two memory systems used across most report/audit workflows — pkg/workflow/repo_memory.go (repo-memory, git-branch-backed) and cache-memory — but neither currently emits structured logs about what gets written, how large it is, or how long it persists before being overwritten/pruned.

Expected Impact

Enables data-driven decisions about memory retention policy (e.g. why known_patterns.md/flagged_items.md under deep-report/ have grown past 70-90KB each per this cycle's own repo-memory listing) and would let future DeepReport cycles quantify memory growth/staleness instead of eyeballing file sizes.

Suggested Agent

New Agent, or an extension of an existing compiler-quality workflow (e.g. daily-compiler-quality) that already scans pkg/workflow/*.go for structural gaps.

Estimated Effort

Medium (1-4 hours) — add size/path/timestamp logging at the repo-memory and cache-memory write call sites in pkg/workflow/repo_memory.go and the cache-memory equivalent.

Data Source

DeepReport Intelligence Briefing — 2026-09-01 (window since briefing #57635), discussion #57652 (arXiv Research).

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• api.anthropic.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.anthropic.com"

See Network Configuration for more information.

Generated by 🔬 Deep Report · claude · agent · 143.5 AIC · ⌖ 14.4 AIC · ⊞ 12.4K · ◷

• expires on Sep 3, 2026, 4:47 AM UTC-08:00