These documents are the source of truth for changing the Skill package. The root README remains user-facing.
Run after every promoted Atom or shared workflow change:
npm run check
npm test
npm run models:validate
npm run models:routing-validate
npm run docs:validate
npm run maintainers:validate
npm run skills:intake -- validate <slug>
npm run web:build
git diff --check
Validate every changed Skill independently:
python3 ~/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/<slug>
An execution route is not Ready merely because its schema parses. When execution is authorized, verify new WeShop routes with one representative, low-cardinality run, poll the accepted executionId to terminal state, inspect the declared invariants, and record the evidence in handoff.md. Do not make a paid run merely to complete intake.
User installations can opt into the background updater documented in the root README. It follows only stable vX.Y.Z releases and ignores untagged changes and prerelease-style tags.
Before publishing, update package.json and package-lock.json to the next semantic version. Open Actions → Publish stable release → Run workflow, enter the identical vX.Y.Z tag, and run it from the intended commit on main. The workflow rejects a tag/package mismatch, validates the runtime tarball, publishes the same version to npm, then creates the GitHub tag and Release. Do not push the stable tag or publish npm manually during ordinary releases; a retry may continue only when that exact npm version already exists.