[Maselkov]

Summary

After the repair, guild sync is still creating a new role in at least one server, in place of a role the admins can see, and the original roles aren't being assigned. So somewhere the bot can't find a saved role id. That's the Oct 17 failure, happening now where we can look at it.

>guildsync_inspect <server id> is an owner-only command. It replies with a text file covering:

• The bot in that server: its top role and whether it can manage roles.
• Role counts: how many roles are in the bot's cache, and how many Discord's API has.
• Each sync:
  • every saved role id and its stored type;
  • whether the cache has that role, and whether Discord does, with name, position and member count;
  • the in-game rank names exactly as the API returns them, to show stray spaces or different characters;
  • every role on Discord named like a rank, so duplicates show up.

It's read-only, and it never prints the API key.

Test plan

• A test with one saved role that's missing from the cache but still on Discord, plus a rank name with a trailing space. It checks the whole report, and that the key isn't in it.
• Full suite passes, ruff check clean.

🤖 Generated with Claude Code