docs: memory action count 42 -> 44 across templates and docs#204
Conversation
…escriptions _VALID_ACTIONS in server_memory_tools.py carries 44 action strings (session_start_capture / session_end_consolidate landed after the docs were written). Fixes the long-standing template drift so generated CLAUDE.md/AGENTS.md blocks in consumer repos pick up the true count on next upgrade. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5a408cb42b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # TappsMCP Memory Reference | ||
|
|
||
| Complete reference for TappsMCP **shared brain memory** — **42 actions** when accessed via CLI or the `nlt-memory` MCP facade (TAP-3895). | ||
| Complete reference for TappsMCP **shared brain memory** — **44 actions** when accessed via CLI or the `nlt-memory` MCP facade (TAP-3895). |
There was a problem hiding this comment.
Document the two actions behind the new count
This reference now advertises 44 actions, but the action tables below still enumerate only 42 names; comparing the page to server_memory_tools._VALID_ACTIONS shows the unlisted actions are session_start_capture and session_end_consolidate. Readers and generated agents using this as the promised complete reference still have no parameter or lifecycle-status guidance for those two actions, so the count bump leaves the docs internally incomplete.
Useful? React with 👍 / 👎.
| - **tapps-research** - Look up library documentation and research best practices | ||
| - **tapps-security** - Run a comprehensive security audit with vulnerability scanning | ||
| - **tapps-memory** - Manage shared project memory (42 actions, cross-session) | ||
| - **tapps-memory** - Manage shared project memory (44 actions, cross-session) |
There was a problem hiding this comment.
Keep the generated medium template count consistent
In the medium AGENTS template this changed summary now says 44 actions, but the same template’s memory section still has ### Memory actions (42 total) earlier in the file. Since this template feeds consumer AGENTS.md content, tapps_init/tapps_upgrade will continue generating instructions with conflicting memory-action counts unless the source header/list is updated along with this bullet.
Useful? React with 👍 / 👎.
The tapps_memory dispatch table (_VALID_ACTIONS, server_memory_tools.py:51-105) carries 44 actions; templates and docs still said 42. Surfaced by the briefs code-truth audit (ReportLab PR #18). Consumer repos pick up the corrected count on next tapps upgrade.
🤖 Generated with Claude Code