fix: docker, broken npm build script and missing dependency

[ruant]

• Add missing copy in dockerfile.
• Add missing zod dependency

[gemini-code-assist]

Summary of Changes

Hello @ruant, 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 addresses critical issues related to the project's build system and dependency management. It ensures that the Docker environment correctly incorporates all required package configurations, integrates a previously missing zod dependency for the user interface, and rectifies an npm build script to guarantee all internal packages are compiled successfully. These changes are crucial for maintaining a robust and consistent development and deployment workflow.

Highlights

• Dockerfile Update: The Dockerfile has been updated to include the package.json files for the libs/spec-parser library, ensuring all necessary dependencies are available during the Docker build process.
• Missing Dependency Added: The zod library has been added as a dependency to apps/ui/package.json, resolving a previously missing dependency for the UI application.
• NPM Build Script Fix: The build:packages script in the root package.json has been corrected to properly build the @automaker/spec-parser workspace, addressing a broken build command.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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. ↩

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

📝 Walkthrough

Walkthrough

Adds a Dockerfile COPY for libs/spec-parser package metadata, introduces zod as a dependency in apps/ui, and splits the monolithic build:packages script into two sequential npm build steps for @automaker/utils and @automaker/spec-parser.

Changes

Cohort / File(s)	Summary
Docker / Build config Dockerfile, package.json	Dockerfile: added COPY to include libs/spec-parser/package*.json in the base stage. package.json: changed build:packages to run @automaker/utils and @automaker/spec-parser as separate sequential npm build commands.
App dependencies apps/ui/package.json	Added dependency: zod with version constraint `^3.24.1

Sequence Diagram(s)

(omitted — changes do not introduce a multi-component sequential workflow that meets diagram criteria)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• refactor: update Dockerfiles for server and UI to streamline dependen… #302 — touches Docker build/context and copying workspace package.json files, related to package-file copying and build sequencing.
• Fix production docker build #651 — adds COPY for libs/spec-parser/package*.json in Dockerfile, directly related.

Suggested labels

Bug, Ready-To-Merge

Suggested reviewers

• webdevcody

Poem

🐰 I hopped through Docker, light on my paws,

Copied spec files without any pause.
Zod joined the party, schemas in tune,
Builds split in order beneath the moon.
A tiny rabbit cheers — build green soon! 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: Docker build fix, npm build script correction, and missing dependency addition.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request addresses several build-related issues by fixing the npm build script, adding a missing dependency, and updating the Dockerfile to include the new spec-parser library. My review identified a critical typo in the Dockerfile that needs to be corrected for the Docker build to succeed. I've also provided a suggestion to improve the consistency and maintainability of the npm build script in package.json. The other changes appear to be correct.

[gemini-code-assist]

There's a typo in the source path of this COPY instruction. The directory is spec-parser, not spep-parser. This will cause the Docker build to fail as it won't be able to find the source file.

COPY libs/spec-parser/package*.json ./libs/spec-parser/

[gemini-code-assist]

This change serializes the build for @automaker/utils and @automaker/spec-parser, which likely fixes a build issue. However, the script remains inconsistent as other packages are still built in parallel using multiple -w flags in a single command (e.g., @automaker/prompts and @automaker/model-resolver).

For improved consistency and to prevent similar issues in the future, I suggest serializing all the package builds. This makes the build order explicit and easier to debug.

Suggested change

	"build:packages": "npm run build -w @automaker/types && npm run build -w @automaker/platform && npm run build -w @automaker/utils && npm run build -w @automaker/spec-parser && npm run build -w @automaker/prompts -w @automaker/model-resolver -w @automaker/dependency-resolver && npm run build -w @automaker/git-utils",
	"build:packages": "npm run build -w @automaker/types && npm run build -w @automaker/platform && npm run build -w @automaker/utils && npm run build -w @automaker/spec-parser && npm run build -w @automaker/prompts && npm run build -w @automaker/model-resolver && npm run build -w @automaker/dependency-resolver && npm run build -w @automaker/git-utils",

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@Dockerfile`:
- Line 28: The Dockerfile has a typo in the COPY instruction: the source path
string "libs/spep-parser/package*.json" is incorrect and should be
"libs/spec-parser/package*.json"; update the COPY line that reads COPY
libs/spep-parser/package*.json ./libs/spec-parser/ to use the correct source
path so the build can find the package.json files.

🧹 Nitpick comments (1)

apps/ui/package.json (1)

108-108: Clarify the rationale for supporting both Zod v3 and v4.

The version constraint ^3.24.1 || ^4.0.0 spans two major versions. Since zod is used directly only in apps/ui/src/routes/terminal.tsx, confirm whether both versions are actually needed or if the range can be narrowed to a single major version to avoid potential inconsistencies.