Last week I fixed a bug in this repo's MCP server where .env was being loaded from a bare relative path — ".env" instead of something resolved against the file's own location. The failure mode was that an MCP client launches server.py as a subprocess with just a command and args, no cwd, so wherever the process happens to start determines whether the credentials load at all. I patched load_env() to resolve against os.path.dirname(os.path.abspath(__file__)) and moved on.
This week I was auditing the same file for something unrelated and found the exact same bug, unfixed, nineteen lines below the fix.
The second instance
server.py has an update_article MCP tool that fetches an article's current state before overwriting it, then writes an audit entry to a JSONL log — specifically so a bad write (wrong article_id, a hallucinated integer, whatever) leaves a trace instead of silently clobbering a live post. The log path was declared like this:
_ARTICLE_UPDATE_LOG = "logs/article_updates.jsonl"
