mateclaw/.github/pull_request_template.md
matevip 74928d615d feat(memory): Dream v2 Phase 1 — lifecycle mediator foundation
Wire memory-facing events (turn-started, turn-completed, session-ended,
memory-written) through a single MemoryLifecycleMediator so
MemoryProvider implementations can hook into the agent conversational
flow without spreading side-effects across the runtime.

Ten atomic steps shipped under feat/dream-v2-p1-lifecycle:

- A.1 + A.2: MemoryLifecycleMediator class + TurnContext value object
- A.3: TurnStartedEvent / TurnCompletedEvent domain events
- A.4: MemoryLifecycleEventListener bean for Spring event plumbing
- A.5: MemoryProvider.onMemoryWrite default method (backward compatible)
- A.7: wire the mediator into AgentService at the right hook points
- A.8: LifecycleFlagGuardTest — feature flag must gate every hook
- A.9: MemoryLifecycleMediatorTest — unit coverage per hook
- A.10: LifecycleRecallCountIT — F4 regression across the stack

Feature flags (all default OFF; enable per phase after staging):
- mate.memory.lifecycle-mediator-enabled
- mate.memory.dream.focused-enabled
- mate.memory.dream.archive-enabled

This is Phase 1 foundation only — focused-dream and archive-dream
providers arrive in later phases.
2026-04-20 17:31:21 +08:00

558 B

Dream v2 PR Checklist

  • Only modifies current Phase scope; no future Phase undecided designs introduced
  • Feature flag defaults to off
  • scripts/rfc-lint.sh passes locally
  • New Flyway migrations exist in both h2/ and mysql/ directories
  • New @Scheduled cron expressions documented in application.yml with stagger rationale
  • Phase 1 PR: recall_count / daily_count regression test passes
  • Phase 3 PR: mate_fact two-write-path SQL-level guard test passes

Related RFC: