[deep-report] Extract shared MemoryEntryBase for CacheMemoryEntry/RepoMemoryEntry/DriveMemoryEntry

[github-actions]

Description

pkg/workflow has three memory-entry configuration structs that share the same 4-field core but are declared independently: CacheMemoryEntry, RepoMemoryEntry, and DriveMemoryEntry (each carrying Key/ID-equivalent, Description, Enabled/similar flag, and a retention/size-limit field, per source discussion). Because the three were authored separately as the memory backends were added one at a time, common fields have drifted slightly in naming even though they mean the same thing across backends.

Suggested Change

Extract a MemoryEntryBase struct in pkg/workflow covering the shared fields, and embed it in CacheMemoryEntry, RepoMemoryEntry, and DriveMemoryEntry, each adding only its backend-specific fields. This mirrors the pattern already used successfully for BaseMCPServerConfig and ToolUsageStatsBase elsewhere in the codebase.

Expected Impact

Prevents further naming drift across the three memory backends as new shared fields get added, and makes it obvious at a glance which fields are common vs. backend-specific.

Suggested Agent

New Agent / general-purpose Go refactor.

Estimated Effort

Medium (2 hours)

Data Source

DeepReport analysis 2026-08-28, source: Typist Go Type Consistency Analysis (discussion #56632), Cluster 4.

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 · 236.5 AIC · ⌖ 8.15 AIC · ⊞ 12.4K · ◷

• expires on Aug 30, 2026, 1:52 PM UTC-08:00

[github-actions]

This issue was automatically closed because it expired on 2026-08-30T21:52:26.734Z.

Closed by Workflow