AgentCache 0.3.1

📊 Harness & Diagnostics: Reframed as an honest improvement roadmap

Experiment Report Reframing

The experiment harness report is now framed as an honest diagnostic to find where agentcache is weak vs naive/blobless approaches, not a marketing sheet. The report now leads with "Where agentcache has holes (improvement targets)":

1. Cold-start bundle penalty (the #1 structural hole): agentcache's bootstrap bundle scales with history depth, making it catastrophic vs blobless on deep-history repos:

   • git.git: 105.6 MiB cold vs 440.8 KiB blobless → 245×
   • cpython: 116.5 MiB vs 171× worse
   • go: 85.4 MiB vs 68× worse
   • django: 39.1 MiB vs 74× worse
   • Engineering target: partial-history / lazy / on-demand bundle construction.

2. Marginal warm wins on lean code repos: fd 12.4%, ripgrep 17.4%, codex 23.1%, redis 24.8%. On these, agentcache barely beats blobless even at steady state.

3. Impractical break-evens (warm passes before agentcache repays cold cost vs blobless): fd ~715, git ~682, cpython ~541, go ~148. For these, blobless is the correct default.

4. Per-commit hook overhead: real operational cost — go.git 15s, cookbook 7.3s, cpython 6.5s — that naive/blobless don't carry.

Each experiment now includes a cold-start table across all three approaches (naive/blobless/agentcache) with plainly visible bundle penalties, and verdict prose is neutral (no ✓).

Web UI: Unified Recent Activity Feed

• Left-hand nav "Runs" is now a unified "Recent Activity" feed showing recent experiments alongside raw tests, type-badged and routed to the correct detail view.
• Experiments feed shows all experiment variants with experiment links.

Earlier in the 0.3.x line

• Graceful cache-taint detection + fallback
• Hook vs GitHub Action warm-method comparison

---

No agentcache-core API changes since 0.3.0. This release is harness/docs/UI polish that enables honest iteration on the cold-bundle and hook-overhead targets.

Generated with Amplifier