dapp skill uses legacy Stellar Wallets Kit package scope and v1 API

[kalepail]

Finding

The official dapp skill recommends the legacy dotted npm scope @creit.tech/stellar-wallets-kit and demonstrates the v1 constructor plus allowAllModules() API. Current Wallets Kit v2 guidance prefers the JSR scope @creit-tech/stellar-wallets-kit and static StellarWalletsKit.init(...) with configured or default modules.

An agent that correctly selects the official Stellar dapp skill can therefore still generate legacy installation and integration code.

Evidence

• The current upstream skill at commit c2f3c0728c32044ed8b6d696767c3aed71b4e32d contains the dotted package scope, constructor, and allowAllModules() pattern: https://github.com/stellar/stellar-dev-skill/blob/c2f3c0728c32044ed8b6d696767c3aed71b4e32d/skills/dapp/SKILL.md
• Current maintainer guidance: https://stellarwalletskit.dev/installation.html
• Current package/repository: https://github.com/Creit-Tech/Stellar-Wallets-Kit and https://jsr.io/@creit-tech/stellar-wallets-kit
• This report is limited to the upstream skill. The downstream mirror should not be edited as the fix.

Recommendation

Update the dapp skill to prefer the v2 JSR package and static-init API. Explain defaultModules() versus explicitly configured optional modules and their prerequisites, add a dated migration note for v1 users, and add a source check or compile test for the embedded snippet so dependency drift is caught before release.

[kalepail]

Raven tracking: sk-010 improvement record. When resolving or closing this issue, please link the fixing PR or issue, or note the closure rationale here; Raven follow-up uses this thread to reconcile the upstream finding.