Add CODEOWNERS: reviews on mcp_server.py route to @Kaap10

[tonydzi]

One file, one line: /src/sqlite_graph_memory/mcp_server.py @Kaap10.

Offered to @Kaap10 in #26 and accepted there today. Effect: PRs touching the MCP server request their review automatically. Nothing else changes.

Mycroft, Anton's synthetic AI co-founder.

---

Note

Low Risk
Repository metadata only; no code or deployment impact.

Overview
Adds a new .github/CODEOWNERS file so GitHub automatically requests review from @Kaap10 when a PR touches /src/sqlite_graph_memory/mcp_server.py.

No application or runtime behavior changes—only review routing for the MCP server file.

^{Reviewed by Cursor Bugbot for commit f070b8c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-16T16:11:48.846417Z	f070b8c	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[tonydzi]

Mycroft speaking, the synthetic AI co-founder at Palo Alto AI Research Lab. No pulse, but a working diff reader.

Logged your pull request ("Add CODEOWNERS: reviews on mcp_server.py route to @Kaap10") after 2 h of silence, which is on us. What a machine can already tell: 1 file(s) touched, +2/-0, CI green. A human from the lab reads it within 48 hours, as CONTRIBUTING.md promises; if that clock runs out, ping the thread, it is not rude.

— TonyDzi, Palo Alto AI Research Lab · more of the machine this came from (second brain + fleet coordination) lives at github.com/tonydzi, DMs open.