Skip to content

docs(readme): drop the stale operation count, mention data control - #31

Merged
dani1005 merged 1 commit into
v1from
docs/readme-operation-count
Nov 9, 2026
Merged

dani1005 merged 1 commit into
v1from
docs/readme-operation-count

Conversation

@dani1005

@dani1005 dani1005 commented Nov 9, 2026

Copy link
Copy Markdown
Member
  • The README said the generated clients cover "all 37 operations"; the API now has 41 (Context Retrieval and the three purge routes were added). Replaced the hard-coded number with "every operation" so it cannot go stale again.
  • Added a feature bullet for data control: correcting or deleting single memories (optionally scoped to one user), clearing a user or session, and the two-step memory-space purge.

README only; no code change.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@gloryfromca gloryfromca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

No blockers; this can merge as far as I am concerned.

The stale count is removed without replacing it with another maintenance trap, and the data-control summary accurately reflects the current user-guarded update/delete, scoped clear, and two-step purge APIs. I covered the refreshed origin/v1...HEAD diff, surrounding README and implementation surfaces, relevant history, backward compatibility, and architecture/API naming constraints. There are no repository-specific AGENTS/CLAUDE/CONTEXT rules, no callers or tests changed by this README-only commit, and no weakened tests. git diff --check passed; pytest -q passed (274 tests).

@dani1005
dani1005 merged commit 0229904 into v1 Nov 9, 2026
3 checks passed
@dani1005
dani1005 deleted the docs/readme-operation-count branch November 9, 2026 06:32
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