Skip to content

fix: complete memory activation after init self-heal #581

Description

@LeXwDeX

Why

The memory audit on main cd055eb reproduces an activation gap left after #415: with a real git project, a non-empty AGENTS.md and no initialization stamp, the first /memory on self-heals the stamp but returns Memory remains off without enabling memory. Existing self-heal tests only call statusReason, so all 113 memory tests pass while this user path fails.

Scope

Complete activation in the same request after initialization self-healing. Preserve uninitialized-project and unavailable-model gates. Review and validate the memory subsystem on the current main baseline.

Approach

Add a public setEnabled regression covering the first invocation and persisted configuration, then continue configuration resolution after a successful self-heal. Verify memory persistence, admission, identity migration, search, provider wire and server composition using Bun 1.3.14. Carry the verified fix through dev and main before debug/prerelease and stable release validation.

Acceptance

  • The first /memory on enables memory when AGENTS.md provides initialization evidence.
  • Persisted configuration and status agree with the command response.
  • Projects with no initialization evidence remain blocked and off does not enable them.
  • Memory regression tests and required current-head CI pass.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions