review: secure sync_bib/cite split from cookjohn/zotero-mcp#92 - #2
Merged
Yyu-ang merged 1 commit intoSep 4, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Second clean split requested in
cookjohn/zotero-mcp#92. This PR is stacked on the citation/export split and contains only the local-file bibliography/draft tools plus their safety controls.Included
sync_bibwith batched Better BibTeX exportcitefor.tex/.md/.markdowndraftsCitation File Toolspreference, disabled unless explicitly enabledsync_bibciteSecurity changes vs original cookjohn#92 implementation
sync_bibrefuses existing files unlessoverwrite=trueciteedits only an existing.tex,.md, or.markdowndraftbatchSize, default 100) instead of one large fixed-timeout RPCValidation
npm ci✅npm run build(zotero-plugin build && tsc --noEmit) ✅git diff --check✅Final branch is one feature commit on top of split ①.
@cloneorcopy please review this security-focused split before upstream submission.