protowiki-update-codex

The Skill automates upgrading Wikimedia Codex packages in lockstep by bumping @wikimedia/codex, @wikimedia/codex-design-tokens, and @wikimedia/codex-icons simultaneously. It diffs upstream docs, propagates changes, refreshes vendored token snapshots, and runs verification.

Refreshing the vendored Codex design token snapshot is handled during the upgrade flow. The Skill updates the snapshot from @wikimedia/codex-design-tokens and runs verification to confirm integration with the latest design system version.

Propagating upstream Codex documentation changes into dependent skills is done by diffing the upstream design-codex repository. The Skill identifies documented updates and integrates them into codex-* skills to maintain consistency across the design system.

Yes, ProtoWiki requires upgrading @wikimedia/codex, @wikimedia/codex-design-tokens, and @wikimedia/codex-icons together. These tightly coupled packages must be bumped in lockstep to ensure consistency and up-to-date tooling across the design system.

Yes, you can verify Codex design system compatibility after upgrading dependencies. The Skill runs verification as part of its repeatable workflow, confirming that the dependency bump, token refresh, and documentation propagation maintain integration across Codex versions.

A Codex upgrade workflow needs a clear baseline and target version to provide a repeatable process with validation steps. This ensures the lockstep bump across the three packages maintains consistency and allows verification to confirm compatibility between starting and ending states.