oc-update

原文涵盖的主题

• Update Opchain
• Commands
• Plugins
• The managed AGENTS.md section
• Adding plugins and the duplicate guard
• /oc-update doctor
• Source checkout behavior
• Results and recovery

On first invocation, read references/orchestrator.md and follow its welcome protocol. Use the bundled updater for all version checks, downloads, installation, and verification. It needs Node.js 22.13+; consumer updates also need access to https://opchain.dev. Source checkout updates work offline. Resolve scripts/update.mjs relative to this loaded skill's directory; run it with the consuming repository as the working directory. Do not assume the user's repository contains Opchain's development scripts or package commands. First distinguish an update from a first installation. Check the consuming repo's .claude/skills, .agents/skills, and legacy .codex/skills for Opchain files. First recognize an Opchain source checkout: a Git root with skills/orchestrator.md, skills/oc-checkpoint-protocol/SKILL.md, and both scripts/sync-skill-bundles.mjs and scripts/sync-plugin-skills.mjs. The updater auto-detects this layout, including when the local skill links have not been created yet. Run it normally; source links are supported through this path. If an update/check request has no repo-local installation, report that fact and identify the host's plugin manager as the route for a global/plugin up

这里只展示节选，请以完整原文和当前要求为准。