Rebuild README.md for the Hexclave rebrand

.github/SECURITY.md

@@ -2,14 +2,14 @@
 
 ## Supported Versions
 
-Only the latest versions of Stack Auth's server and client packages are supported. We do not provide security updates for older versions.
+Only the latest versions of Hexclave's server and client packages are supported. We do not provide security updates for older versions.
 
-If you would like to get security consulting regarding older versions of on-prem or self-hosted deployments of Stack Auth, please [contact us](mailto:team@stack-auth.com).
+If you would like to get security consulting regarding older versions of on-prem or self-hosted deployments of Hexclave, please [contact us](mailto:team@hexclave.com).
 
 ## Reporting a Vulnerability
 
-Stack Auth practices [responsible disclosure](https://en.wikipedia.org/wiki/Coordinated_vulnerability_disclosure). This helps us protect our users, but requires your cooperation.
+Hexclave practices [responsible disclosure](https://en.wikipedia.org/wiki/Coordinated_vulnerability_disclosure). This helps us protect our users, but requires your cooperation.
 
-Please disclose security vulnerabilities responsibly by emailing us at security@stack-auth.com. In this case, we will get back to you within 96 hours, and aim to get a fix released as soon as possible. We will disclose the issue publicly after at most 90 days.
+Please disclose security vulnerabilities responsibly by emailing us at security@hexclave.com. In this case, we will get back to you within 96 hours, and aim to get a fix released as soon as possible. We will disclose the issue publicly after at most 90 days.
 
 Hence, we ask you not to publicize issues until the 90 days deadline is over. Also, please do not create GitHub issues with security vulnerabilities; instead, email us directly at the address above.

.github/workflows/table-of-contents.yaml

@@ -22,4 +22,4 @@ jobs:
       - uses: technote-space/toc-generator@9e238e7974de5fcf7b17b7acc54c896160dda0a3 # v4
         with:
           TOC_TITLE: ""
-          TARGET_PATHS: "README*.md,CONTRIBUTING.md"
+          TARGET_PATHS: "CONTRIBUTING.md"

CONTRIBUTING.md

@@ -1,8 +1,8 @@
-# Contributing to Stack Auth
+# Contributing to Hexclave
 
-Welcome to Stack Auth!
+Welcome to Hexclave!
 
-Due to the nature of authentication, this may not be the easiest project to contribute to, so if you are looking for projects to help gain programming experience, we may not be a great match. If you're looking for projects for beginners, check out [Awesome First PR Opportunities](https://github.com/MunGell/awesome-for-beginners).
+Due to the nature of user infrastructure, this may not be the easiest project to contribute to, so if you are looking for projects to help gain programming experience, we may not be a great match. If you're looking for projects for beginners, check out [Awesome First PR Opportunities](https://github.com/MunGell/awesome-for-beginners).
 
 ## Table of contents
 
@@ -19,18 +19,18 @@ Due to the nature of authentication, this may not be the easiest project to cont
 
 ## How to contribute
 
-If you think Stack Auth is a good fit for you, follow these steps:
+If you think Hexclave is a good fit for you, follow these steps:
 
-1. Join [our Discord](https://discord.stack-auth.com)
-2. [Use Stack Auth](https://docs.stack-auth.com/). The best way to understand the project is to use it. Build an application on top of Stack Auth, and post it on GitHub or write a blog post about how you built it. This also lets us assess your skills and understand where you could best help the project.
+1. Join [our Discord](https://discord.hexclave.com)
+2. [Use Hexclave](https://docs.hexclave.com/). The best way to understand the project is to use it. Build an application on top of Hexclave, and post it on GitHub or write a blog post about how you built it. This also lets us assess your skills and understand where you could best help the project.
 3. Give us feedback on Discord or GitHub; let us know where you got stuck, and which things you wish were easier. (We appreciate contributions most when they solve problems the authors encountered themselves in real usage.)
-4. Contribute to the [documentation](https://docs.stack-auth.com) and create examples & guides. This way, you can share your knowledge and expertise with everyone else who's just getting started.
-5. Only then, start [contributing to the codebase](README.md#-development--contribution). Coordinate with us on Discord beforehand to ensure we are not working on the same thing already, and to make sure a task is not more difficult than it seems.
+4. Contribute to the [documentation](https://docs.hexclave.com) and create examples & guides. This way, you can share your knowledge and expertise with everyone else who's just getting started.
+5. Only then, start [contributing to the codebase](README.md#contributing). Coordinate with us on Discord beforehand to ensure we are not working on the same thing already, and to make sure a task is not more difficult than it seems.
 
 
 ## Security & bug bounties
 
-For any security-related concerns & bug bounties, please email us at [security@stack-auth.com](mailto:security@stack-auth.com).
+For any security-related concerns & bug bounties, please email us at [security@hexclave.com](mailto:security@hexclave.com).
 
 ## Vibecoding setup
 
@@ -47,7 +47,7 @@ For vibecoding, it can help to have multiple parallel copies of the codebase ope
   eval "$(/path/to/direnv hook <bash|zsh>)"
   eval "$(/path/to/direnv export <bash|zsh>)"
   ```
-3. Now, create a `.envrc` file in the root of Stack Auth's codebase with the following content:
+3. Now, create a `.envrc` file in the root of Hexclave's codebase with the following content:
   ```sh
   # .envrc
   # make sure to install direnv and add it to your shell rc file (e.g. ~/.bashrc or ~/.zshrc)