docs(skills): pin the 1.2.1 release in the stash-cli and stash-edge skills

[auxesis]

This pull request moves three version pins in the agent skills from 1.2.0 to 1.2.1. It makes main pass its tests again.

The release-train test fails on main

stash copies the skills/ directory into its npm tarball, and the build does not rewrite the version literals inside it. So languages/typescript/packages/cli/src/__tests__/release-train.test.ts requires the stash-cli skill to pin the stash version in the tree.

Version Packages pull request #1020 moved stash and @cipherstash/stack to 1.2.1 on 2 October 2026. It left the skill pins at 1.2.0, because no CI ran on that pull request. That missing CI is part 1 of Linear issue CIP-4285. Since then, the test has failed on main, in Tests run 37071819999, and on every pull request based on it.

Three pins move to 1.2.1

• skills/stash-cli/SKILL.md: the bare-project one-shot, npx --package=stash@1.2.1 stash eql install.
• skills/stash-edge/SKILL.md: both npm:@cipherstash/stack@1.2.1/wasm-inline specifiers, in the Deno import and in the import map.

These are the same three lines that commit 1fcf7223 changed in #928 for 1.1.1, and that commit 4aaf7dca changed in #938 for 1.2.0.

This change has no changeset, by design

The pins have always moved inside the Version Packages pull request of the release they name, with no changeset of their own. A changeset here would start a stash 1.2.2 release only to correct a pin. That release would then need its own pin change, and the loop would repeat.

The published stash 1.2.1 ships skills that pin 1.2.0. That is acceptable, and the next stash release ships the correct pins.

A follow-up change for CIP-4285 makes the version step move these pins by itself, so that every Version Packages pull request carries them.

Checks

• release-train.test.ts: 20 tests pass.
• pnpm test:scripts: 62 files and 1,145 tests pass, with 1 skipped as on main.

Linked issues

This PR is part of #1044. It moved the skill pins that Version Packages PR #1020 missed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PaY5xYydZUWhv8Nex9Sw8a

[changeset-bot]

⚠️ No Changeset found

Latest commit: bfd21af

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[freshtonic]

Approved. The change is correct and minimal.

I examined these items:

• At this head, stash and @cipherstash/stack are both at 1.2.1 in languages/typescript/packages/*/package.json. The three changed pins now agree with those versions.
• No other stash@x.y.z or @cipherstash/stack@x.y.z pin stays in skills/. Thus the skill version pins loop in release-train.test.ts has no other target to fail on.
• CI on bfd21afd passes, which includes Run Tests on Node 22 and Node 24, Bun, and the Deno WASM E2E tests.

No changeset is correct here. A stash changeset that only moves a pin would start a 1.2.2 release, and that release would need a new pin change. The follow-up for CIP-4285, which makes the version step move these pins, is the correct permanent fix.