[system-prompt] add system_prompt_kit.md for MCP agent configuration

[Obsidian68]

Summary

• Created system_prompt_kit.md at project root — an agent-facing system prompt covering all 5 MCP tools (memory_write, memory_search, memory_read, memory_delete, memory_list) with parameters, response formats, and realistic examples
• 6 sections: Identity, When to Write, What to Never Write, How to Write, How to Search, Tool Reference
• Behavioral rules are short and strict, written for agent consumption
• Added System Prompt Kit section to README.md
• Added v1.3.0 entry to CHANGELOG.md

Known limitations

• Documentation only — no code changes on this branch
• MCP tools are documented from the branch-plan spec; actual MCP server implementation is on feat/mcp-server
• Examples use slug-style IDs and type: "memory" matching the current model defaults

Test plan

• All 5 MCP tools documented with parameters, response format, and examples
• Behavioral rules are short and strict, zero TODOs
• No code changes (documentation-only branch)
• README.md updated with system prompt kit section
• CHANGELOG.md updated with v1.3.0 entry

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c9d538d974

ℹ️ 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".

[chatgpt-codex-connector]

Remove claim that MCP tools are ready to use

This line says the prompt kit is "ready-to-use" for agents connecting via MCP, but this commit does not add any MCP server/tool implementation in src/ (repo-wide search only finds MCP references in docs/reference files). As written, users will follow this setup and then fail to call the documented tools, which is a functional documentation regression rather than a wording nit.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Avoid publishing 1.3.0 changelog before version bump

Adding a 1.3.0 release section here makes the published docs inconsistent with the actual shipped version, which remains 1.2.0 in both pyproject.toml and src/engram/__init__.py. Tooling and users that rely on the changelog for released versions can incorrectly assume 1.3.0 is available and includes MCP features.

Useful? React with 👍 / 👎.