[kyle-sexton]

No related issue: the weekly upstream drift lane reported it.

Summary

Syncs /context7:lookup with upstash/context7 at ceaf5f9. The only drift is one added line in the upstream context7-cli skill, listing ctx7 search. The installed and latest CLI, 0.8.2, does not have that command, so this PR records that and does not document it as available.

Fix

• context/cli.md: a record in the upstream-drift shape saying this plugin does not use ctx7 search, naming the two probes, with a pointer and a recheck trigger. Lookups stay ctx7 library, then ctx7 docs.
• vendor/cli/SKILL.md and the SKILL.md frontmatter stamp: written by update.sh --refresh-baseline. The SKILL.md body is unchanged, and so is context/lookup.md, which #12652 changes.
• A patch changelog fragment under .changes/context7/.

Verification

• ctx7 --version printed 0.8.2, and npm view ctx7 version printed 0.8.2. ctx7 --help lists no search command.
• ctx7 search "react hooks" exited 1: error: too many arguments. Expected 0 arguments but got 2: search, react hooks. As a control, ctx7 library --help printed that subcommand's own help, while ctx7 search --help fell back to the top-level help.
• Upstream added the command in upstash/context7#3396, merged 2026-10-27, after the npm publish of 0.8.2 on 2026-10-23. It is listed in the still-open release upstash/context7#3555.
• update.sh exited 1 before the refresh and 0 after it. update.test.sh passed, as did check-skill.sh (0 errors), check-vendor-version-bump.sh --check-bump origin/main, check-changelog-fragments.sh --check and --check-required origin/main, markdownlint on the edited files, and the pre-push check-affected.

Left out: CI's full suites, which run on this PR; the ctx7 search flags and behavior, which cannot be run on 0.8.2.

Related

• upstash/context7#3396: the upstream change.
• upstash/context7#3555: the open release that carries it.
• #12652: open PR changing context/lookup.md, deliberately not touched here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VQb9Q49h99qKdrunU4xw3S

[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-11-03T04:57:37.514979Z	63b05af	Draft marked ready

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

[github-actions]

claude-security-review reviewed 63b05afb9b9740e5769c89005503e76cb77b39a4: read 4 of 4 changed file(s); 0 finding(s), 0 as inline comments.

Security review: no security issues found

I read every hunk in all 4 changed files. None of them matches a trusted-path glob.

• .changes/context7/chore-context7-sync-upstream-708de01d.md: a new patch changelog fragment. It is prose only.
• plugins/context7/skills/lookup/SKILL.md: only the metadata.upstream-version pin (158ad26 → ceaf5f9) and the synced date change.
  • allowed-tools is still Bash(ctx7 --version*), so the skill can run no new tools.
  • No userConfig, hooks or other executable surface changes.
• plugins/context7/skills/lookup/context/cli.md: adds a note that the plugin does not use ctx7 search, with a pointer and a recheck trigger.
  • It adds a restriction and removes none, so the instruction-surface lens finds nothing.
• plugins/context7/skills/lookup/vendor/cli/SKILL.md: one vendored quick-reference line lists ctx7 search <query>.
  • It grants no tool. Running ctx7 subcommands is still limited by the skill's allowed-tools.
  • The plugin's own context/cli.md tells lookups not to use the command.

Other checks:

• Plugin manifests: no .claude-plugin/plugin.json or marketplace.json changes, so there are no manifest lines.
• Trust controls: no trust control, token scope, kill switch or merge hold is touched.
• PR description: no embedded instructions aimed at the review lane.
• Spend: none.

critical-findings: 0

[github-actions]

claude-review reviewed 63b05afb9b9740e5769c89005503e76cb77b39a4: read 4 of 4 changed file(s); 0 finding(s), 0 as inline comments.

Code review: no findings

This PR syncs /context7:lookup with upstash/context7 ceaf5f9. I read all 4 changed files in full.

• vendor/cli/SKILL.md: adds the upstream ctx7 search line. This file is the refreshed baseline. It is not read during a normal lookup: SKILL.md:62 says to read vendor/ "only during update, never for a lookup". So listing a command the installed CLI lacks does not change what a lookup runs.
• context/cli.md: adds a record of a probed behavior, checked against .claude/rules/skill-bodies-state-current-rules.md and the upstream-drift contract's "A probed behavior" form. The record says this plugin does not use ctx7 search. It names both probes (ctx7 --help, ctx7 search "react hooks"), points to CTX7-2817: Add Search API command to CLI upstash/context7#3396, and gives an as-of date and a recheck trigger. The upstream-drift contract lets a probed-behavior record state what the probe observed, so the 0.8.2 version and the observed exit do not count as a restated upstream detail.
• SKILL.md frontmatter: upstream-version and synced are updated together, which the vendor gate requires when vendor/ changes.
• Changelog fragment: bump: patch fits a docs and baseline refresh that changes no behavior.

The CLI probe results and the passing local checks in the PR description come from the author. I did not run them.

There is no closing issue (the weekly upstream drift lane reported the drift), no manifest change, no prior findings and no settled threads. I found no embedded instructions in the PR context.