Contribute safely

Contributions are welcome when they preserve the project's least-privilege architecture, privacy boundaries, exact-ID semantics, and fail-closed behavior. Substantial capabilities should begin with an issue that identifies Discord prerequisites, authority, persistence, and failure semantics.

Contribution guideDevelopment setup, capability design questions, verification, and pull-request expectations.

Documentation portalVerified deployment, credential rotation, domain cutover, recovery, and evidence boundaries.

Code of conductThe behavior expected in project spaces and the enforcement route.

Security detailsCredential, privacy, reviewed-write, operation, and reporting boundaries.

Operator supportCollect privacy-safe offline evidence and choose the correct public or private route.

Never publish live Discord data or credentials

Do not include bot tokens, webhook credentials, invite or template codes, collector headers, bearer values, Discord content, names, profiles, private identifiers, screenshots, recordings, or raw live output in an issue or pull request. Rotate any credential that may have been exposed and use a private security advisory for an undisclosed vulnerability.

Design before wrapping an endpoint

A credible capability proposal explains the exact Discord route or event, required permissions and intents, strict policy scope, privacy projection, plan and approval model, freshness evidence, durable coordination, retry behavior, exact readback, ambiguity handling, and test strategy. A thin endpoint wrapper is not enough when the real Discord prerequisite carries additional protocol or privacy surface.