[lionellbriones]

Motivation and Context

Agents on other machines could not follow the Web3Auth stack upgrade, because those steps lived in a personal skill. The published migration skill now includes them, so one skill covers a plain Torus CLI migration and an EMBED-573 upgrade.

Jira Link

https://consensyssoftware.atlassian.net/browse/EMBED-573

Description

• Add the nine-step stack upgrade to migrating-to-torus-cli. A plain migration still follows Inspect, Migrate, Monorepos, and Verify.
• Ship reference.md with the CODEOWNERS, Dependabot, and .npmrc tables.
• Step 3 and step 5 read this skill. Shared tooling installs the @toruslabs/torus-scripts release that contains this skill, not a pinned 9.0.1.
• Link .cursor/skills/migrating-to-torus-cli/reference.md at the package file, the same way SKILL.md is already linked.

How has this been tested?

• packages/torus-scripts/test/contracts.test.mjs (7 passed), including the packed skill and reference
• vp fmt --check on the edited files

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• My code follows the code style of this project. (run lint)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Made with Cursor

---

Note

Low Risk
Documentation and published skill assets only; no runtime API or security behavior changes beyond packaging tests.

^{Reviewed by Cursor Bugbot for commit 06ad452. Bugbot is set up for automated code reviews on this repo. Configure here.}