Repository navigation
chore(context7): sync to upstash/context7 4087030 - #16530
Conversation
Refresh the vendored find-docs and context7-cli baselines with update.sh --refresh-baseline and stamp upstream-version upstash/context7@4087030. Upstream's only change in both files swaps the /facebook/react example library ID for /reactjs/react.dev: upstash/context7 251c6c5 says /facebook/react now returns library_redirected and no docs. Take: the common-mistakes line in context/lookup.md and the seven lines in context/cli.md that used the old ID now use the new one. The Git Bash error line there is the same path rewrite applied to the new ID, not a re-run on Windows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
claude-security-review reviewed Security review: no security issues foundI read all 6 changed files in full. This pull request re-vendors What changes:
Instruction-surface lens: no standing instruction is deleted, narrowed or softened. The "do not include secrets, personal data, proprietary code… in queries" rule in Not touched by this diff:
No prior findings. This is a full review, not blocking only. critical-findings: 0 |
|
claude-review reviewed Code review: no findingsThis PR re-vendors I read the whole diff for all 6 changed files.
No plugin manifest changed, and nothing in the change can cause a charge. Verifier dropped 0 of 0 candidates. |
Refs: #16488
Summary
Re-vendors
/context7:lookupfor drift issue #16408. The row is apin=unknownvendored-copy row whose check isplugins/context7/skills/lookup/scripts/update.sh(run with no arguments byscripts/upstream-drift-vendored-report.sh). Its report showed both vendored baselines,vendor/find-docs/SKILL.mdandvendor/cli/SKILL.md, behind upstash/context7 master4087030ad2dc16578130e2dab1e48ba735f8ea38.update.sh --refresh-baselinerefreshed both and moved the frontmatter pin toupstream-version: upstash/context7@4087030ad2dc16578130e2dab1e48ba735f8ea38,synced: 2026-11-16.The only upstream content change in both files swaps the example library ID
/facebook/reactfor/reactjs/react.dev(two lines infind-docs, one incontext7-cli). The upstream commit that made it, upstash/context7@251c6c5, says/facebook/reactnow returnslibrary_redirected, so every example that used it printed a redirect notice and no docs. Disposition: take. It changes no skill's design, so no needs-human issue was filed.The PR carries no closing keyword for #16408: that issue is labeled needs-human, and the weekly drift run closes it once
update.shreads clean on the vendored content, which it now does.Fix
vendor/find-docs/SKILL.md,vendor/cli/SKILL.md: replaced byupdate.sh --refresh-baseline.SKILL.mdfrontmatter: the pin above, stamped by the same run.context/lookup.md"Common mistakes": the/prefix example uses/reactjs/react.dev.context/cli.md: the seven lines that used/facebook/react(the Git Bash gotcha and the composability examples) use/reactjs/react.dev. The quoted Git Bash error line is the same path rewrite applied to the new ID, not a re-run on Windows.context7(patch).The ID swap needs no pointer record under
.claude/rules/skill-bodies-state-current-rules.md: it is a usage example, not an upstream limit, default, version or error string that a decision rests on.Not changed: the eval samples under
plugins/context7/evals/lk-resolve-then-docs/samples/that contain/facebook/react. They are recorded sample transcripts for graders, not guidance, and editing them would change what the graders are tested against.Verification
Run in the worktree:
update.shafter the sync:find-docsandcontext7-clibothUpstream unchanged since last baseline. It still exits 1 locally forCLI version behind(installedctx70.10.0, npm latest 0.11.1). That is this machine's install, which this run does not upgrade (--fixrunsnpm install -g). No workflow under.github/workflows/and nothing inscripts/upstream-drift-vendored-report.shinstallsctx7(grep finds no match), so on the hostedubuntu-24.04runner the script should report the CLI as not installed, which is not drift. That the runner image ships noctx7of its own is UNVERIFIED.update.test.sh: all 20 checks passed.scripts/check-affected.sh --base origin/main --no-fetch: 16 passed, 2 skipped over 6 changed files.scripts/check-changelog-fragments.sh --check: all 6 fragments valid.scripts/check-vendor-version-bump.sh --check-bump origin/main: passed.scripts/check-cost-figures.sh --check: no cost figure outside baselined and exempt files.scripts/check-as-of-recheck.sh --check: every as-of date has a recheck trigger.Not rechecked: records whose triggers depend on the installed
ctx7version, not on the vendored skill content this sync moves. Each keeps its date.context/cli.md(verified against 0.9.0), thecontext/mcp.mdserver URL and header facts (trigger: installedctx7newer than 0.5.5), and thecontext/mcp.mdCLI-versus-MCP observation (trigger:ctx7minor version change). Rechecking them needsctx70.11.1 installed, and this run installs nothing globally. The plugin's model-graded evals were not run.Remaining
On #16488 after this pull request (it delivers the upstash/context7 re-vendor, drift issue #16408):
/context7:lookuprecords that still owe a recheck against an installedctx70.11.1:context/cli.md(verified against 0.9.0), thecontext/mcp.mdserver URL and header facts (trigger fired: installedctx7newer than 0.5.5), and thecontext/mcp.mdCLI-versus-MCP observation (trigger:ctx7minor version change).Related
🤖 Generated with Claude Code