chore(motoko): sync caffeinelabs/skills ee8e3dd

[marc0olo]

Syncs caffeinelabs/skills e6277b7 → ee8e3dd.

Upstream changed what counts as a pending migration. It used to mean a migration created in the current build. It now means a migration that has not been applied yet. The edit and freeze rules follow from that: a pending migration gets edited, and an applied one is frozen. The rewording covers all four Motoko skills (writing-motoko, migrating-motoko-actors, troubleshooting-motoko-migrations, reviewing-motoko plus references/state-and-persistence.md). No upstream files were added or removed, and no icskills-owned sections were affected. .claude/upstream.md has the new commit and upstream versions.

New eval migrating-motoko-actors #9: a migration written in an earlier session and never deployed is still pending, so the next change is folded into it and does not go in a second file.

This sync leaves a few unchanged upstream lines that still say to always add a new migration file. They contradict the new rule, so I filed them upstream as caffeinelabs/skills#15 rather than patching them here.

Eval results (new case 9, with baseline)

WITH skill: 3/3 passed
  ✅ Edits the existing `20260929_101500.mo` to add `tags` alongside `priority`, instead of creating a second migration file
  ✅ Explains the file is still pending because it was never applied (deployed), so it is not frozen even though it was written in an earlier session
  ✅ Notes that at most one pending migration is allowed (`check-limit = 1`), so a second file would be rejected

WITHOUT skill: 2/3 passed
  ✅ Edits the existing `20260929_101500.mo` ...
  ✅ Explains the file is still pending ...
  ❌ Notes that at most one pending migration is allowed (`check-limit = 1`), so a second file would be rejected

Closes #408

[github-actions]

Skill Validation Report

Project Checks

✓ Project checks passed for 4 skills (0 warnings)

[Copilot]

Copilot review overview

🟡 Changes recommended

Several unchanged instructions still mandate new files or describe all migrations as frozen, contradicting the new pending-migration behavior.

Review effort: Balanced
Findings: 3 · 1

Open (4)

• Make new migration file creation conditional · New
• Distinguish editable pending migrations from applied history · New
• Avoid creating duplicate files for undeployed migrations · New
• Replace date-dependent regression wording · New

What changed in this PR

Synchronizes Motoko migration guidance with upstream’s deployment-based definition of pending migrations.

Changes:

• Clarifies pending versus applied migration rules.
• Adds an eval for undeployed migrations from earlier sessions.
• Updates upstream tracking metadata.

File	Description
skills/​writing-motoko/​SKILL.md	Updates migration freeze terminology.
skills/​migrating-motoko-actors/​SKILL.md	Revises pending migration guidance.
skills/​troubleshooting-motoko-migrations/​SKILL.md	Clarifies editable pending migrations.
skills/​reviewing-motoko/​SKILL.md	Updates migration review criteria.
skills/​reviewing-motoko/​references/​state-and-persistence.md	Revises applied-migration guidance.
evaluations/​migrating-motoko-actors.json	Adds the undeployed-migration regression case.
.claude/​upstream.md	Records the new upstream commit and versions.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.