chore: willboosterify this repo

[exKAZUu]

Customer Summary

• Refreshes the repository configuration with the current WillBooster defaults.
• Keeps the prompt-summary example reliable when Gemini follows the prompt with natural-language framing.
• Requires no migration or compatibility action.

Technical Summary

• Updates managed agent guidance, hook configuration, development tooling, and lockfile metadata.
• Normalizes the Bun lockfile during dependency preparation.
• Makes the prompt-summary model answer require summary-only output without a preamble or explanation.

Why

• Keep the repository aligned with the current shared configuration.
• Prevent nondeterministic Gemini preambles from causing the end-to-end summary judge to fail.

Testing

• Ran the affected live-API end-to-end test eight consecutive times.
• Ran bun run verify-full successfully.

[gemini-code-assist]

Summary of Changes

Hello, 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 aligns the repository with current WillBooster standards. It enhances AI agent instructions, streamlines the bun.lock normalization process into a reusable script, and performs necessary dependency maintenance to keep the project up to date.

Highlights

• Standardized AI Agent Guidelines: Updated documentation and AI agent rules across .cursor/rules/general.mdc, AGENTS.md, CLAUDE.md, and GEMINI.md to include best practices for documentation and Zod-based object validation.
• Lockfile Normalization: Introduced a new shell script (.lefthook/normalize-bun-lockfile.sh) to remove registry-specific proxy URLs from bun.lock, ensuring the lockfile remains registry-agnostic.
• Dependency Updates: Updated core project dependencies, including build-ts, oxc-parser, rolldown, and tsx, to their latest versions.
• Configuration Refactoring: Refactored the lefthook configuration and the package.json prepare script to utilize the new lockfile normalization script.

New Features

🧠 You can now enable Memory (public preview) 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.

Ignored Files

• Ignored by pattern: .gemini/** (1)
  • .gemini/styleguide.md

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 the 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 counterproductive. 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.

---

Lock files now clean, Rules for agents clearly set, Codebase is boosted.

Footnotes

1. Review the Generative AI Prohibited Use Policy, 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 extracts the inline bun lockfile normalization logic from lefthook.yml into a dedicated shell script, .lefthook/normalize-bun-lockfile.sh, and integrates it into the package.json prepare script. It also updates project guidelines in several markdown files to recommend using zod for object validation and to only describe final snapshots in explanatory text, alongside bumping build-ts and other dependencies. The feedback suggests simplifying the new shell script by removing a redundant file copy operation and using cat to overwrite the file.

[gemini-code-assist]

The cp -p command is redundant here because sed immediately overwrites the $normalized file. We can simplify this and avoid copying the file twice by removing cp -p and using cat to write the normalized content back to $file. This naturally preserves the original file's permissions, ownership, and any hard/symlinks without needing to copy them to the temp file first.

Suggested change

	cp -p "$file" "$normalized"
	sed -E 's#(", )"https://npm\.flatt\.tech/[^"]*"#\1""#g' "$file" > "$normalized"
	if ! cmp -s "$file" "$normalized"; then
	mv "$normalized" "$file"
	sed -E 's#(", )"https://npm\.flatt\.tech/[^"]*"#\1""#g' "$file" > "$normalized"
	if ! cmp -s "$file" "$normalized"; then
	cat "$normalized" > "$file"

References

1. Simplify code as much as possible to eliminate redundancy. ^(link)