chore: update ama invite link

Author: didinele

apps/website/next.config.mjs

@@ -50,14 +50,19 @@ export default {
 			{
 				source: '/invites/ama',
 				destination:
-					'https://discord.com/oauth2/authorize?client_id=1427232824854970409&permissions=274878024704&scope=applications.commands%20bot',
-				permanent: true,
+					'https://discord.com/oauth2/authorize?client_id=872022469081448489&permissions=274878024704&scope=applications.commands%20bot',
+				// Deliberately a 302, unlike every other redirect here: this one's destination just changed from
+				// the canary application to the public one, and the previous 301 is cached in the browser of
+				// anyone who used it during the canary window. Keeping it non-permanent means a further change
+				// (or the eventual flip back to `true`) actually reaches those users. Restore `permanent: true`
+				// once the canary application is retired -- see docs/prod-branch.md.
+				permanent: false,
 			},
 			{
 				source: '/invites/modmail',
 				destination:
-					'https://discord.com/oauth2/authorize?client_id=1530137759304515647&permissions=360777370624&scope=applications.commands%20bot',
-				permanent: true,
+					'https://discord.com/oauth2/authorize?client_id=981971797480210523&permissions=360777370624&scope=applications.commands%20bot',
+				permanent: false,
 			},
 			{
 				source: '/kofi',