Skip to content

Enforce memory maintainer scans - #2

Merged
jackysp merged 1 commit into
mainfrom
codex/memory-maintainer-enforcement
Aug 17, 2026
Merged

Enforce memory maintainer scans#2
jackysp merged 1 commit into
mainfrom
codex/memory-maintainer-enforcement

Conversation

@jackysp

@jackysp jackysp commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • pin the reserved memory maintainer to standard/chat, including preset reapplication
  • bind maintainer memory calls to the input namespace
  • require complete memory_list cursor traversal before mutations or a successful final response
  • document the runtime contract and add regression coverage

Why

The deployed maintainer inherited the server default model and returned an unverified report without calling memory_list. Maintenance runs need host-enforced enumeration instead of relying on prompt compliance alone.

Impact

Existing compatible schedules keep their enabled state, namespace payload, and cron configuration when the preset is reapplied. Maintainer runs that skip enumeration, cross namespaces, omit a returned cursor, or mutate before completing the scan now fail.

Validation

  • cargo test --workspace --all-targets — 52 passed, 1 ignored
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo fmt --all -- --check
  • git diff --check

@jackysp
jackysp marked this pull request as ready for review August 17, 2026 13:50
Copilot AI lite review requested due to automatic review settings August 17, 2026 13:50
@jackysp
jackysp merged commit 9d1e6a8 into main Aug 17, 2026
3 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants