Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@site/src/components/ContactForm.astro`:
- Around line 111-116: The submission currently proceeds when grecaptcha is
undefined, so update the submit handler in ContactForm.astro to detect when
typeof grecaptcha === "undefined" and stop the submission flow: prevent the form
submit/return early, set a visible error message (reuse the component's existing
form error state/UI) informing the user that reCAPTCHA failed to load and they
should retry or disable blockers, and do not call
form.querySelector("#captchaResponse") or proceed to send data; ensure the check
occurs before the grecaptcha.execute call and references grecaptcha,
captchaInput and the form submit handler to locate where to add this
early-return and UI error display.
- Around line 112-113: The TypeScript compiler complains about the global
grecaptcha used in ContactForm.astro; add a proper type declaration for
grecaptcha to satisfy strict TS. Either install the `@types/grecaptcha` dev
package (npm install --save-dev `@types/grecaptcha`) or add a local declaration
file (e.g., env.d.ts) that declares the global grecaptcha with ready and execute
signatures so the call to grecaptcha.execute(...) in ContactForm.astro is typed
and the build error is resolved.

In `@site/src/layouts/Base.astro`:
- Around line 72-73: Extract the hard-coded reCAPTCHA site key into a single
shared constant (for example PUBLIC_RECAPTCHA_SITE_KEY) and reference that
constant in both Base.astro and ContactForm.astro; implement it by placing the
key in an environment variable exposed to the client (e.g., via
import.meta.env.PUBLIC_RECAPTCHA_SITE_KEY) or a shared config module, then
replace the inline literal in Base.astro's script src and the literal used in
ContactForm.astro (line ~113) with the shared variable (e.g., use
?render=${PUBLIC_RECAPTCHA_SITE_KEY}) so updates happen in one place.
- Around line 67-69: The Base.astro layout currently wraps the page slot in
<main> causing any slotted <footer> (Footer component) to be nested inside
<main>; update Base.astro so <main> contains only the primary <slot /> and
render the Footer component as a sibling after </main> in Base.astro, then
remove Footer usage from individual pages that currently slot it (so pages only
provide main content to the slot). Ensure you reference the layout's <main> and
the Footer component when making the change so the Footer is no longer nested
inside <main>.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@site/src/components/ContactForm.astro`:
- Around line 116-127: The current reCAPTCHA logic calls grecaptcha.execute
without waiting for grecaptcha.ready and proceeds if the `#captchaResponse` input
is missing; change it to call grecaptcha.ready() first (use
grecaptcha.ready(async () => { ... })) before calling
grecaptcha.execute(siteKey, { action: "contact" }), ensure you immediately
error/return if form.dataset.recaptchaKey is falsy or if
form.querySelector("#captchaResponse") returns null (do not continue
submission), and keep the existing errorMsg update/focus when
readiness/token/getting the captcha input fails so submission fails closed;
reference grecaptcha.ready, grecaptcha.execute, form.dataset.recaptchaKey, and
captchaInput/#captchaResponse to find the code to modify.

In `@site/src/layouts/Base.astro`:
- Around line 75-76: Add an optional prop to Base.astro's Props interface named
enableRecaptcha?: boolean, wrap the existing reCAPTCHA script element in a
conditional that only renders when enableRecaptcha is true (e.g.,
{enableRecaptcha && <script ...>}), and update index.astro to pass
enableRecaptcha={true} when rendering Base so only the page that contains
ContactForm loads the third‑party reCAPTCHA script; leave other pages unchanged
(do not pass the prop or pass false).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@site/src/components/ContactForm.astro`:
- Line 125: The grecaptcha.ready() await can hang indefinitely; wrap the
existing await new Promise<void>((resolve) => grecaptcha.ready(() =>
resolve())); in a timeout guard (e.g., Promise.race between the grecaptcha.ready
promise and a setTimeout that resolves/rejects after a short interval) so the
wait fails fast if reCAPTCHA never becomes ready, then handle the timeout path
in the ContactForm.astro submit flow (stop the "Sending..." state and surface an
error message). Ensure you reference the grecaptcha.ready wrapper and the submit
handler in ContactForm.astro when adding the timeout and the error handling.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@site/src/components/ContactForm.astro`:
- Around line 125-128: The Promise.race timer created with setTimeout should be
cleared when grecaptcha.ready resolves to avoid a lingering timeout; modify the
block around grecaptcha.ready()/Promise.race to assign the timeout to a variable
(e.g., const timer = setTimeout(...)) and call clearTimeout(timer) inside the
grecaptcha.ready resolve path (the resolver passed to new Promise that calls
grecaptcha.ready), ensuring the timeout is cancelled when grecaptcha.ready wins;
keep the existing reject path for the timeout so it still rejects if
grecaptcha.ready doesn't fire.