Skip to content

docs: clarify single-tenant scope, refresh exec-plan#5

Merged
mortik merged 1 commit into
mainfrom
docs/single-tenant-scope
May 28, 2026
Merged

docs: clarify single-tenant scope, refresh exec-plan#5
mortik merged 1 commit into
mainfrom
docs/single-tenant-scope

Conversation

@mortik
Copy link
Copy Markdown
Member

@mortik mortik commented May 27, 2026

Summary

  • README: explicit scope note that yards-bot is for the Fleetyards Discord only. Anything we want available to other Star Citizen servers (slash-command lookups, release announcements, etc.) belongs in a separate, future, public bot in its own repo.
  • README: drop the now-stale "Server Members Intent required" line — v1 doesn't use the privileged GuildMembers intent.
  • exec-plan: same scope clarification, mark steps 2–5 as done with the actual PR refs, and replace the "privileged intent" risk with the real footgun we hit live (Partials.User on remove).

No code changes.

Test plan

  • No code touched; nothing to test beyond reading the diff.

… reality

- README: state that the bot is Fleetyards-only (bot_public is already false)
  and that multi-tenant Star Citizen features belong in a future separate bot.
- README: drop the stale "Server Members Intent required" line — v1 doesn't
  use the privileged GuildMembers intent.
- exec-plan: same scope clarification, plus reflect what actually shipped
  (steps 2-5 done, the privileged intent isn't needed, Partials.User is the
  real footgun on the remove path).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mortik mortik merged commit 9ac5d09 into main May 28, 2026
1 check passed
@mortik mortik deleted the docs/single-tenant-scope branch May 28, 2026 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant