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

[AztecBot]

Summary

Implements Steps 1 and 2 of the issue-reporting v1 plan we've been discussing:

• Adds a new "Get help & report issues" page at /developers/support (docs/docs-developers/support.md) with a decision tree for: ask-first channels (Discord, Forum), reproducible bugs (GitHub bug_report.yml), Noir compiler bugs (noir-lang/noir), feature requests (feature_request.yml), docs issues, operator/node issues, and security disclosures (Cantina bounty, GitHub PVR, security@aztec.foundation). The security section is called out at the top of the page and again as its own section so a builder cannot miss it before filing publicly.
• Wires the page into the developer sidebar (sidebars-developer.js) so it shows up alongside the getting-started pages.
• Surfaces support in the navbar Resources dropdown and in the footer Community section (docusaurus.config.js).
• Removes the airtable.com/appMhZd7lsZS3v27R/pagxWYAHYYrnrrXmm/form signup gate from the two places it appears (the navbar Resources dropdown and the homepage QuickLinks), and replaces it with a direct https://discord.gg/aztec invite plus a link to the new support page.
• Adds a direct Aztec Discord link to the footer Community section, which previously listed Forum + Noir Discord + X but not the main Aztec Discord at all.
• Adds a :::tip Need help? admonition to the bottom of the two getting-started pages (getting_started_on_local_network.md, getting_started_on_testnet.md) and the Aztec overview, pointing at the new support page.

Why

External builders today have no signposted path from docs.aztec.network to "if you hit a bug, do X". The footer doesn't even surface the main Aztec Discord, and the navbar's "Join community" link routes through an Airtable signup form rather than going directly to Discord. This means:

• First-time builders bypass the documented bug-reporting flow entirely (the open from-community issues on this repo are all self-filed without any docs-side guidance).
• Security-sensitive bugs are at risk of being filed publicly because there is no gate prompting the reporter to consider it.
• Discord is hidden behind a friction step that has no moderation value for an open developer community.

This PR adds the missing signposts. It does not change any of the existing issue templates, labels, or triage process: it only makes the existing paths discoverable.

Test plan

• yarn and yarn start from docs/ and confirm the dev server boots without warnings.
• Visit /developers/support and confirm the page renders, the decision-tree table is readable, and the security warning admonition is visible at the top.
• Confirm the "Get help" entry appears in the developer sidebar.
• Open the Resources navbar dropdown and confirm: "Get help & report issues" (internal link), "Discord", "Forum", "X/Twitter" are present, and "Join community" / Airtable URL are gone.
• Confirm the footer Community section now lists "Get help & report issues", "Forum", "Discord", "Noir Discord", "X (Twitter)".
• On the homepage, confirm the Resources section now shows a "Get help & report issues" QuickLink in place of the old "Join the Community" Airtable card.
• On both getting_started_on_local_network and getting_started_on_testnet, confirm the "Need help?" tip block renders at the bottom and the link to ./support.md works.
• yarn build succeeds and produces no broken-link errors (the new internal links /developers/support, ./support.md, and the existing discord.gg/aztec invite are all reachable).

Follow-ups (not in this PR)

These were also in the v1 plan but are scoped to separate PRs so this one stays focused:

• New operator_issue.yml issue template with node-specific fields.
• "Is this a security issue?" gate on bug_report.yml.
• Label additions (P-medium, P-low, S-needs-repro, O-labs / O-wonderland / O-nethermind, etc.).
• A aztec-starter config.yml that redirects issues to this repo.

Once those land, the support page already references them by name, so the page will stay accurate without further edits.

Notes for reviewers

• The description: front-matter field on support.md follows the repo's docs style guide (under 160 chars, active voice).
• Headings use sentence case throughout, no em-dashes in prose, and second-person voice per docs/CLAUDE.md.
• The Discord verification level should be set to at least "Medium" before merging this if Discord member-screening relied on the Airtable form for spam control. The change moves the public docs link to a direct invite; if Discord's built-in screening is not on, the open server may see a brief uptick in low-effort joiners.

---

Created by claudebox · group: slackbot

[critesjosh]

Add the pages to the version-v4.3.0 docs instead of 4.2

[critesjosh]

Suggested change

	- **PXE, wallet, CLI**: `aztec`, `aztec-wallet`, `aztec.js`, `bb.js`, sandbox.
	- **PXE, wallet, CLI**: `aztec`, `aztec-wallet`, `aztec.js`, `bb.js`, local network.

[critesjosh]

Historically we have discouraged typo fixes because it encourages low effort AI generated PRs that are more trouble to review than to just fix. Maybe we encourage typo issues instead, and automatically tag @AztecProtocol/devrel

[critesjosh]

It says to use email if PVR is not available in the first sentence, then says to use PVR in the second.

[critesjosh]

May be worth adding a link to discord at the top of this sub-heading? I know you link to them above, but if I click on the Operator support link in the table above, i jump straight here without seeing the discord link section. Another alternative could be to put the discord link section above the decision tree table