Point the skill fetch at the renamed adapty-integration directory

[eandreeva-twr]

What

One functional line. The skills repo renamed its SDK skill directory, so RAW_BASE in src/lib/agent/skill-source.ts follows:

-  '.../adapty-sdk-integration-skill/main/skills/adapty-sdk-integration'
+  '.../adapty-sdk-integration-skill/main/skills/adapty-integration'

The repo name is unchanged — only the skill directory inside it moved — so the rest of the URL stays as-is. The other five edits are comments naming the skill.

⚠️ Merge order

RAW_BASE points at main of the skills repo. This PR must land after adaptyteam/adapty-skills#35 merges, or integrate/migrate will 404 on every run. Nothing else gates it.

Base branch

Targets integrate-command-prototype, not main — that is where src/lib/agent/ lives. Nothing here is on main or in any published version, which is why this rename costs one line instead of a deprecation.

Not verified

I did not typecheck: all seven changes are inside comments or one string literal, and the worktree has no node_modules. Worth a CI run rather than my word.

Worth considering separately

Fetching skill content from a hardcoded raw.githubusercontent.com URL at runtime means a future rename or move of that repo breaks every already-published CLI version — raw does not follow repo renames, and published tarballs can't be patched. There is already an ADAPTY_SKILL_DIR escape hatch for local dev; promoting the base to an env-overridable constant before this feature ships would remove that class of breakage. Out of scope here.

---

⛔ BLOCKED until the repo is renamed

These commits assume the GitHub repo has been renamed adaptyteam/adapty-sdk-integration-skill → adaptyteam/adapty-skills. That rename has not happened yet. Every updated URL here 404s until it does, so do not merge before the rename.

Rename steps (repo Settings → General → Repository name), then in whatever order:

1. Rename the repo on GitHub. Open PRs, branches and stars move with it; git and web traffic redirect from the old name indefinitely.
2. Never create anything at adaptyteam/adapty-sdk-integration-skill again — reusing the name permanently kills the redirect.
3. Re-register the skills.sh listing and the Context7 entry — both key on owner/repo, and the old slugs remain as stale duplicates that cannot be redirected.
4. Merge Point the skill fetch at the renamed adapty-integration directory #17 after the skills-repo PR. RAW_BASE is a raw.githubusercontent.com URL and raw does not follow repo renames.

What survives the rename with no action: existing claude plugin installs (git remotes follow the redirect), existing clones, and every published docs page slug — adapty-sdk-integration-skill* page ids are unrelated to the repo name and deliberately unchanged.