docs: add support page, surface Discord, remove Airtable signup gate

docs/developer_versioned_docs/version-v4.2.0/support.md

@@ -0,0 +1,128 @@
+---
+title: Get help and report issues
+sidebar_position: 5
+description: Where to ask questions, report bugs, request features, and disclose security issues for the Aztec stack.
+---
+
+This page tells you where to go when something does not work, when you want to file a bug, when you have a feature idea, or when you have found a possible security issue. Pick the section that matches your situation.
+
+:::warning Security issues are different
+If your issue involves loss of funds, key or seed disclosure, leakage of private notes, a way to forge or replay transactions, or anything you suspect could harm users, **do not open a public GitHub issue or post in Discord**. Use the [security disclosure process](#security-issues) instead.
+:::
+
+## Quick decision tree
+
+| Your situation | Where to go |
+| --- | --- |
+| Possible security issue (funds, keys, privacy, exploit) | [Security disclosure](#security-issues) |
+| You are not sure if the bug is real, or you cannot reproduce it yet | [Ask first: Forum or Discord](#ask-first-forum-and-discord) |
+| You have a reproducible bug in `aztec-packages` (PXE, aztec.js, aztec-nr, sandbox, CLI, AVM, barretenberg, L1 contracts) | [File a bug on GitHub](#file-a-bug) |
+| You have a Noir compiler or language bug | [Noir issues on `noir-lang/noir`](https://github.com/noir-lang/noir/issues) |
+| You have a feature request or enhancement idea | [File a feature request](#feature-requests) |
+| You are running a node, sequencer, or prover and hit an operator problem | [Operator support](#operator-and-node-issues) |
+| You want to suggest a documentation change | [File a docs issue](#documentation-issues) |
+
+## Ask first: Forum and Discord
+
+If you are not yet sure whether your problem is a real bug or a configuration issue, start in the community channels. You can often get a faster answer there, and the team can help you build a minimal reproduction before you open a GitHub issue.
+
+- [Aztec Discord](https://discord.gg/aztec): real-time chat, best for quick questions, syntax issues, and configuration help.
+- [Aztec Forum](https://forum.aztec.network): long-form Q&A, best for design discussions, complex bug reports, and conversations you want indexed and searchable.
+- [Noir Discord](https://discord.com/invite/JtqzkdeQ6G): the dedicated Noir community.
+
+Once you have a clear reproduction, the right next step is to file a GitHub issue using the form below.
+
+## File a bug
+
+Reproducible bugs in the Aztec stack belong on GitHub. Use the bug template, which automatically labels your issue and helps a maintainer triage it.
+
+[Open a new bug report](https://github.com/AztecProtocol/aztec-packages/issues/new?template=bug_report.yml)
+
+### What a high-quality bug report includes
+
+The template asks for these, and your issue will be triaged faster if you provide all of them.
+
+1. **Aztec version**, for example `0.85.0-alpha-testnet.2`. Use `aztec-up list` if you are not sure.
+2. **What you were trying to do**, in one or two sentences.
+3. **A minimal, runnable reproduction**. A code snippet that compiles, or a link to a public repo branch, is much more useful than prose. If your reproduction is large, please trim it before filing.
+4. **Expected vs. actual behavior**.
+5. **Environment**: operating system, Node.js version, and browser if relevant.
+6. **Logs and errors**: the failing block, ideally with `LOG_LEVEL=debug` for the module that failed.
+7. **What you already tried**: workarounds, version downgrades, related issues you read.
+
+### Where bugs in specific components go
+
+All of the components below live in [`AztecProtocol/aztec-packages`](https://github.com/AztecProtocol/aztec-packages), so use the bug template above and let triage attach the component label.
+
+- **PXE, wallet, CLI**: `aztec`, `aztec-wallet`, `aztec.js`, `bb.js`, sandbox.
+- **Aztec.nr framework**: the `aztec-nr` smart contract framework.
+- **Protocol circuits or protocol specs**: the rollup, kernels, and other circuits.
+- **Barretenberg, AVM, L1 contracts**: the prover backend, the Aztec Virtual Machine, and the Ethereum-side rollup contracts.
+
+For the **Noir compiler** or the Noir language itself, file on [`noir-lang/noir`](https://github.com/noir-lang/noir/issues) instead.
+
+## Feature requests
+
+Use the feature request template for new functionality, enhancements to existing components, or proposed changes to the developer experience.
+
+[Open a feature request](https://github.com/AztecProtocol/aztec-packages/issues/new?template=feature_request.yml)
+
+Include:
+
+- The problem you are trying to solve.
+- A concrete example or use case, if you have one.
+- Why this is impactful: what is unblocked or made easier if it ships.
+
+## Documentation issues
+
+If something in the docs is wrong, outdated, or missing, you have two good options.
+
+- **Open an issue** with the bug template and quote the URL and paragraph that needs fixing.
+- **Open a pull request** directly. Every docs page in this site has an "Edit this page" link at the bottom that takes you to the right file in [`docs-developers/`](https://github.com/AztecProtocol/aztec-packages/tree/next/docs/docs-developers).
+
+Small typo fixes are welcome as direct PRs without an issue first. For larger restructures, open an issue so a maintainer can confirm the direction before you write the change.
+
+## Operator and node issues
+
+If you are running a node, sequencer, or prover and you hit an operational problem (sync failures, missed proposals, prover crashes, deployment errors), please include the following alongside the standard bug-report fields:
+
+- **Network** (mainnet, testnet, devnet, or local).
+- **Role** (validator, prover, RPC node).
+- **Block height at failure** and approximate UTC timestamp.
+- **Hardware**: CPU model, RAM, disk type and size.
+- **Container runtime and image version**.
+- **Configuration** (your `config.json` or environment block, with secrets redacted).
+- **Logs**: the last few hundred lines around the failure, with sensitive keys redacted.
+
+Operator-specific guides live in the [Operate section](/operate/operators).
+
+## Security issues
+
+**Do not open a public GitHub issue for a suspected vulnerability.** Public disclosure can put users at risk before a fix is available.
+
+Use one of the following, in order of preference:
+
+1. **[Aztec Network Bug Bounty on Cantina](https://cantina.xyz/bounties/80e74370-10d8-4e52-8e4b-7294deb7c9ee)** if the issue is in scope of the bounty program.
+2. **[GitHub Private Vulnerability Reporting (PVR)](https://github.com/AztecProtocol/aztec-packages/security/advisories/new)** for any other suspected vulnerability. Go to the "Security" tab of the repository and click "Report a vulnerability".
+3. **Email `security@aztec.foundation`** if PVR is not available to you. Please do not include the exploit details or steps to reproduce in the email body, send those through PVR.
+
+If you believe a vulnerability is being actively exploited or has severe impact (loss of funds, key compromise, or broad user impact), mark the report as **CRITICAL** in the PVR or email subject.
+
+See the full [security policy](https://github.com/AztecProtocol/aztec-packages/blob/next/SECURITY.md) for more.
+
+## What happens after you file
+
+When you file a GitHub issue using one of the templates above, it is automatically tagged so the team can triage it. A maintainer will:
+
+1. Confirm the component the issue belongs to.
+2. Set a priority based on impact.
+3. Ask follow-up questions if the report is missing a reproduction or context.
+4. Route the issue to the owning team.
+
+The fastest way to a fix is a small, runnable reproduction. If you can attach one, please do.
+
+## See also
+
+- [`CONTRIBUTING.md`](https://github.com/AztecProtocol/aztec-packages/blob/next/CONTRIBUTING.md) for contribution guidelines.
+- [`SECURITY.md`](https://github.com/AztecProtocol/aztec-packages/blob/next/SECURITY.md) for the full security disclosure policy.
+- The [Aztec project board](https://github.com/orgs/AztecProtocol/projects/22) for in-flight work.

docs/developer_versioned_sidebars/version-v4.2.0-sidebars.json

@@ -21,6 +21,11 @@
       "type": "doc",
       "id": "ai_tooling"
     },
+    {
+      "type": "doc",
+      "id": "support",
+      "label": "Get help"
+    },
     {
       "type": "link",
       "label": "Aztec Starter Repository",

docs/docs-developers/getting_started_on_local_network.md

@@ -266,3 +266,7 @@ Want to build something cool on Aztec?
 - Check out the [Token Contract Tutorial](./docs/tutorials/contract_tutorials/token_contract.md) for a beginner tutorial, or jump into more advanced ones
 - Ready for a live network? Try [deploying on testnet](./getting_started_on_testnet.md)
 - Start on your own thing and check out the How To Guides to help you!
+
+:::tip Need help?
+If something does not work, see the [support guide](./support.md). It tells you when to ask in [Discord](https://discord.gg/aztec) or the [forum](https://forum.aztec.network), when to [open a GitHub issue](https://github.com/AztecProtocol/aztec-packages/issues/new?template=bug_report.yml), and how to disclose security issues responsibly.
+:::

docs/docs-developers/getting_started_on_testnet.md

@@ -205,3 +205,7 @@ For complete testnet technical details including contract addresses and network
 - Check out the [Tutorials](./docs/tutorials/contract_tutorials/counter_contract.md) for building more complex contracts
 - Learn about [paying fees](./docs/aztec-js/how_to_pay_fees.md) with different methods
 - Explore [Aztec Playground](https://play.aztec.network/) for an interactive development experience
+
+:::tip Need help?
+If something does not work, see the [support guide](./support.md). It tells you when to ask in [Discord](https://discord.gg/aztec) or the [forum](https://forum.aztec.network), when to [open a GitHub issue](https://github.com/AztecProtocol/aztec-packages/issues/new?template=bug_report.yml), and how to disclose security issues responsibly.
+:::

docs/docs-developers/overview.md

@@ -92,3 +92,7 @@ As Aztec has native account abstraction, accounts do not automatically have a si
 ## Noir
 
 Noir is a zero-knowledge domain specific language used for writing smart contracts for the Aztec network. It is also possible to write circuits with Noir that can be verified on or offchain. For more in-depth docs into the features of Noir, go to the [Noir website](https://noir-lang.org/).
+
+:::tip Need help?
+If something does not work, or you are not sure where to ask, see the [support guide](./support.md). It explains the right channel for questions, bug reports, feature requests, and security disclosures.
+:::

docs/docs-developers/support.md

@@ -0,0 +1,128 @@
+---
+title: Get help and report issues
+sidebar_position: 5
+description: Where to ask questions, report bugs, request features, and disclose security issues for the Aztec stack.
+---
+
+This page tells you where to go when something does not work, when you want to file a bug, when you have a feature idea, or when you have found a possible security issue. Pick the section that matches your situation.
+
+:::warning Security issues are different
+If your issue involves loss of funds, key or seed disclosure, leakage of private notes, a way to forge or replay transactions, or anything you suspect could harm users, **do not open a public GitHub issue or post in Discord**. Use the [security disclosure process](#security-issues) instead.
+:::
+
+## Quick decision tree
+
+| Your situation | Where to go |
+| --- | --- |
+| Possible security issue (funds, keys, privacy, exploit) | [Security disclosure](#security-issues) |
+| You are not sure if the bug is real, or you cannot reproduce it yet | [Ask first: Forum or Discord](#ask-first-forum-and-discord) |
+| You have a reproducible bug in `aztec-packages` (PXE, aztec.js, aztec-nr, sandbox, CLI, AVM, barretenberg, L1 contracts) | [File a bug on GitHub](#file-a-bug) |
+| You have a Noir compiler or language bug | [Noir issues on `noir-lang/noir`](https://github.com/noir-lang/noir/issues) |
+| You have a feature request or enhancement idea | [File a feature request](#feature-requests) |
+| You are running a node, sequencer, or prover and hit an operator problem | [Operator support](#operator-and-node-issues) |
+| You want to suggest a documentation change | [File a docs issue](#documentation-issues) |
+
+## Ask first: Forum and Discord
+
+If you are not yet sure whether your problem is a real bug or a configuration issue, start in the community channels. You can often get a faster answer there, and the team can help you build a minimal reproduction before you open a GitHub issue.
+
+- [Aztec Discord](https://discord.gg/aztec): real-time chat, best for quick questions, syntax issues, and configuration help.
+- [Aztec Forum](https://forum.aztec.network): long-form Q&A, best for design discussions, complex bug reports, and conversations you want indexed and searchable.
+- [Noir Discord](https://discord.com/invite/JtqzkdeQ6G): the dedicated Noir community.
+
+Once you have a clear reproduction, the right next step is to file a GitHub issue using the form below.
+
+## File a bug
+
+Reproducible bugs in the Aztec stack belong on GitHub. Use the bug template, which automatically labels your issue and helps a maintainer triage it.
+
+[Open a new bug report](https://github.com/AztecProtocol/aztec-packages/issues/new?template=bug_report.yml)
+
+### What a high-quality bug report includes
+
+The template asks for these, and your issue will be triaged faster if you provide all of them.
+
+1. **Aztec version**, for example `0.85.0-alpha-testnet.2`. Use `aztec-up list` if you are not sure.
+2. **What you were trying to do**, in one or two sentences.
+3. **A minimal, runnable reproduction**. A code snippet that compiles, or a link to a public repo branch, is much more useful than prose. If your reproduction is large, please trim it before filing.
+4. **Expected vs. actual behavior**.
+5. **Environment**: operating system, Node.js version, and browser if relevant.
+6. **Logs and errors**: the failing block, ideally with `LOG_LEVEL=debug` for the module that failed.
+7. **What you already tried**: workarounds, version downgrades, related issues you read.
+
+### Where bugs in specific components go
+
+All of the components below live in [`AztecProtocol/aztec-packages`](https://github.com/AztecProtocol/aztec-packages), so use the bug template above and let triage attach the component label.
+
+- **PXE, wallet, CLI**: `aztec`, `aztec-wallet`, `aztec.js`, `bb.js`, sandbox.
+- **Aztec.nr framework**: the `aztec-nr` smart contract framework.
+- **Protocol circuits or protocol specs**: the rollup, kernels, and other circuits.
+- **Barretenberg, AVM, L1 contracts**: the prover backend, the Aztec Virtual Machine, and the Ethereum-side rollup contracts.
+
+For the **Noir compiler** or the Noir language itself, file on [`noir-lang/noir`](https://github.com/noir-lang/noir/issues) instead.
+
+## Feature requests
+
+Use the feature request template for new functionality, enhancements to existing components, or proposed changes to the developer experience.
+
+[Open a feature request](https://github.com/AztecProtocol/aztec-packages/issues/new?template=feature_request.yml)
+
+Include:
+
+- The problem you are trying to solve.
+- A concrete example or use case, if you have one.
+- Why this is impactful: what is unblocked or made easier if it ships.
+
+## Documentation issues
+
+If something in the docs is wrong, outdated, or missing, you have two good options.
+
+- **Open an issue** with the bug template and quote the URL and paragraph that needs fixing.
+- **Open a pull request** directly. Every docs page in this site has an "Edit this page" link at the bottom that takes you to the right file in [`docs-developers/`](https://github.com/AztecProtocol/aztec-packages/tree/next/docs/docs-developers).
+
+Small typo fixes are welcome as direct PRs without an issue first. For larger restructures, open an issue so a maintainer can confirm the direction before you write the change.
+
+## Operator and node issues
+
+If you are running a node, sequencer, or prover and you hit an operational problem (sync failures, missed proposals, prover crashes, deployment errors), please include the following alongside the standard bug-report fields:
+
+- **Network** (mainnet, testnet, devnet, or local).
+- **Role** (validator, prover, RPC node).
+- **Block height at failure** and approximate UTC timestamp.
+- **Hardware**: CPU model, RAM, disk type and size.
+- **Container runtime and image version**.
+- **Configuration** (your `config.json` or environment block, with secrets redacted).
+- **Logs**: the last few hundred lines around the failure, with sensitive keys redacted.
+
+Operator-specific guides live in the [Operate section](/operate/operators).
+
+## Security issues
+
+**Do not open a public GitHub issue for a suspected vulnerability.** Public disclosure can put users at risk before a fix is available.
+
+Use one of the following, in order of preference:
+
+1. **[Aztec Network Bug Bounty on Cantina](https://cantina.xyz/bounties/80e74370-10d8-4e52-8e4b-7294deb7c9ee)** if the issue is in scope of the bounty program.
+2. **[GitHub Private Vulnerability Reporting (PVR)](https://github.com/AztecProtocol/aztec-packages/security/advisories/new)** for any other suspected vulnerability. Go to the "Security" tab of the repository and click "Report a vulnerability".
+3. **Email `security@aztec.foundation`** if PVR is not available to you. Please do not include the exploit details or steps to reproduce in the email body, send those through PVR.
+
+If you believe a vulnerability is being actively exploited or has severe impact (loss of funds, key compromise, or broad user impact), mark the report as **CRITICAL** in the PVR or email subject.
+
+See the full [security policy](https://github.com/AztecProtocol/aztec-packages/blob/next/SECURITY.md) for more.
+
+## What happens after you file
+
+When you file a GitHub issue using one of the templates above, it is automatically tagged so the team can triage it. A maintainer will:
+
+1. Confirm the component the issue belongs to.
+2. Set a priority based on impact.
+3. Ask follow-up questions if the report is missing a reproduction or context.
+4. Route the issue to the owning team.
+
+The fastest way to a fix is a small, runnable reproduction. If you can attach one, please do.
+
+## See also
+
+- [`CONTRIBUTING.md`](https://github.com/AztecProtocol/aztec-packages/blob/next/CONTRIBUTING.md) for contribution guidelines.
+- [`SECURITY.md`](https://github.com/AztecProtocol/aztec-packages/blob/next/SECURITY.md) for the full security disclosure policy.
+- The [Aztec project board](https://github.com/orgs/AztecProtocol/projects/22) for in-flight work.

docs/docs/index.mdx

@@ -203,14 +203,14 @@ privacy, check out the [foundational topics](/developers/docs/foundational-topic
 />
 
 <QuickLink
-  title="Join the Community"
-  description="Connect with other builders"
-  link="https://airtable.com/appMhZd7lsZS3v27R/pagxWYAHYYrnrrXmm/form"
+  title="Get help & report issues"
+  description="Where to ask questions, file bugs, and disclose security issues"
+  link="/developers/support"
   icon={
     <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2">
-      <path d="M17 21v-2a4 4 0 00-4-4H5a4 4 0 00-4 4v2" />
-      <circle cx="9" cy="7" r="4" />
-      <path d="M23 21v-2a4 4 0 00-3-3.87M16 3.13a4 4 0 010 7.75" />
+      <circle cx="12" cy="12" r="10" />
+      <path d="M9.09 9a3 3 0 015.83 1c0 2-3 3-3 3" />
+      <line x1="12" y1="17" x2="12.01" y2="17" />
     </svg>
   }
 />