docs: document collaboration routing

[salasebas]

Summary

• require English for repository content and collaboration
• route public requests and external collaboration through GitHub Issues
• route maintainer-initiated private planning through the private OpenAuth Linear team and rustauth project
• document the privacy boundary between Linear and GitHub

Why

Contributors and agents need an explicit language policy and a clear, privacy-aware rule for choosing the public or private planning system.

Impact

Documentation and collaboration guidance only; no runtime behavior changes.

Validation

• git diff --check
• Rust checks skipped because no Rust code changed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
rustauth-docs-site	Ignored		Jul 26, 2026 7:52pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fffe71b2ac

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Apply the private routing to skill operations

For maintainer-initiated private planning performed through a skill, this routing is contradicted by the unchanged instructions at lines 36–42, which still unconditionally direct both publishing and ticket fetching to GitHub. A skill following those more specific operational instructions can therefore disclose private planning in a public issue or fail to retrieve a Linear ticket; make those operations select Linear or GitHub using the privacy boundary defined here.

AGENTS.md reference: AGENTS.md:L136-L139

Useful? React with 👍 / 👎.