Fix action schema typing for intake form

[zz-plant]

Motivation

• Address TypeScript/ASTRO errors caused by importing z from the wrong place and the handler input being implicitly any in the intake action.
• Centralize the intake validation schema to avoid duplicated schema definitions and improve maintainability.

Description

• Replace the z import from astro:actions with the content schema export z from astro:content and add a dedicated intakeSchema constant.
• Use input: intakeSchema for the action and explicitly type the handler parameter as z.infer<typeof intakeSchema>.
• Small formatting tweak to the delay helper to align with project linting rules.
• Modified file: src/actions/index.ts.

Testing

• Ran bun run check and the full parallel check suite completed successfully (Lint, Unit Tests, Typecheck, Astro Check, Validate JSON, Validate Glossary all passed).

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	et3	1f46a6d	Commit Preview URL Branch Preview URL	Jan 15 2026, 05:09 AM

[gemini-code-assist]

Summary of Changes

Hello @zz-plant, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the intake form action by addressing critical TypeScript and Astro errors related to schema definition and implicit typing. It centralizes the validation schema for better organization and maintainability, ensuring robust type checking and adherence to project standards. The changes enhance the reliability and clarity of the intake form's backend logic.

Highlights

• Corrected Zod Import: The z import for schema definition was changed from astro:actions to astro:content to resolve TypeScript/Astro errors.
• Centralized Intake Schema: The intake form validation schema has been extracted into a dedicated intakeSchema constant, improving maintainability and preventing duplication.
• Explicit Handler Typing: The handler function's input parameter is now explicitly typed using z.infer<typeof intakeSchema>, enhancing type safety.
• Code Formatting: A minor formatting adjustment was applied to the setTimeout callback within the delay helper to align with project linting rules.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively addresses the typing issues in the intake form action by correcting the Zod import and explicitly typing the handler's input. Centralizing the validation schema into intakeSchema is a great improvement for maintainability. The changes are solid and improve the overall quality of the code. I've added a couple of suggestions: one to address a potential security concern with logging Personally Identifiable Information (PII), and another to improve maintainability by replacing a magic number with a named constant. Overall, great work!

[gemini-code-assist]

While this is acceptable for debugging, logging the entire input object, which contains Personally Identifiable Information (PII) like name and email, can be a security risk in a production environment. Consider logging only non-sensitive parts of the input or a confirmation message instead. For example: console.log('Received intake form submission from:', input.email);

[gemini-code-assist]

The delay duration 500 is a magic number. Consider defining it as a named constant (e.g., SIMULATED_API_DELAY_MS) at a higher scope. This improves readability and makes it easier to change the value if needed.