Stale Discord invite in learning/README.md points at an unrelated server

[kalepail]

Summary

learning/README.md line 181 links the Stellar Discord as https://discord.gg/stellar:

| **Discord** | [discord.gg/stellar](https://discord.gg/stellar) |

That vanity code no longer belongs to Stellar. It now resolves to a guild named Wraith Studio, and the invite lands in a channel named security-trap. The correct invite is https://discord.gg/stellardev.

The rest of this repository is already correct — README.md, building-with-ai/README.md, openzeppelin/README.md, stellar-quest/instructions.md, and fca00c/instructions.md all use stellardev. This is a single stale line, and both the link text and the href need updating.

Evidence

Live probes against the Discord invites API on 2026-08-25:

GET https://discord.com/api/v10/invites/stellar?with_counts=true
  guild_id 1035847967111913522 · "Wraith Studio" · vanity_url_code "stellar"
  4055 members · landing channel "security-trap"

GET https://discord.com/api/v10/invites/stellardev?with_counts=true
  guild_id 897514728459468821 · "Stellar Developers" · vanity_url_code "stellardev"
  32774 members

Both codes report a vanity_url_code, so both are current vanity claims and neither is a stale redirect. developers.stellar.org and its static/llms.txt both use stellardev.

Why a link checker will not catch this

A released Discord vanity code can be claimed by any guild that reaches the required boost level. The old code therefore returns a live 200 destination instead of a 404, so ordinary link checking passes. For known-canonical links, an unexpected destination is worth treating as a failure.

Blast radius

Small, and I want to be precise about it because my first pass was not. A GitHub code search for discord.gg/stellar across the stellar org returns 41 files, but that is a substring match and discord.gg/stellar is a prefix of the correct discord.gg/stellardev. After fetching and checking all 41, the stale code survives in three lines across two repositories:

• stellar/ecosystem-resources → learning/README.md:181 (this issue)
• stellar/stellar-dev-skill → skills/standards/resources.md:233 and README.md:126 — The Discord invite in the standards skill now points at an unrelated server stellar-dev-skill#113

No other repository in the org is affected.

Suggested fix

| **Discord** | [discord.gg/stellardev](https://discord.gg/stellardev) |

---

Reported from Stellar Raven eval maintenance (finding sk-020).

[kalepail]

Two updates to the blast-radius paragraph above, after independent verification.

1. The stellar-dev-skill half is already fixed. PR #114 merged at 2026-08-25T20:41:22Z (merge commit db82b5de) and corrected both lines. learning/README.md:181 in this repository is now the only remaining occurrence on a default branch anywhere in the stellar org that I can find.

2. One correction to "No other repository in the org is affected". That was based on public default branches only. Independent review found three further occurrences in stellar/stellar.org-website, all inside component examples and tests rather than user-facing links:

packages/stellar-ui/components/SocialLinks/SocialLinks.test.ts:10
packages/stellar-ui/components/SocialLinks/SocialLinks.tsx:48   (JSDoc example)
packages/stellar-ui/components/SocialLinks/SocialLinks.test.ts:35

Those are sample data, not published links, so they are low priority — but they would propagate if anyone copied the example. Stale copies also survive on four stellar-dev-skill feature branches and on skills.stellar.org/pr/ preview paths, which are outside any default branch.

Nothing here changes the fix for this repository: learning/README.md:181 still needs discord.gg/stellardev, and it is now the last public one.

[kaankacar]

🤖 Automated message from Kaan's Automated Triage Bot.

Triggered by the upstream Stellar Dev Skill switching its Discord invite to the stellardev vanity code (stellar/stellar-dev-skill@b78983c, merged in db82b5d), which this repo's resources list mirrors. Verified that discord.gg/stellardev is the current developer invite against the official docs (developers.stellar.org/docs/validators/tier-1-orgs) and the canonical Dev Skill resources list, and confirmed learning/README.md:181 was the last remaining discord.gg/stellar line here — both the link text and the href were stale, and both are now updated.

Merged in #10 (fb61f4e); main now reads [discord.gg/stellardev](https://discord.gg/stellardev). Closing — the stellar-dev-skill half of the blast radius is tracked separately in stellar/stellar-dev-skill#113.