chore: willboosterify this repo

[exKAZUu]

No description provided.

[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 updates the repository's tooling and agent configuration to improve reliability and performance. It introduces best practices for running long-duration tasks within agent-managed shells, updates core build dependencies, and streamlines configuration files to ensure a more consistent development environment.

Highlights

• Agent Workflow Optimization: Updated documentation in .cursor/rules/general.mdc, AGENTS.md, CLAUDE.md, and GEMINI.md to include robust instructions for running long-running commands (like bun verify-full) in the background using nohup to avoid agent shell timeouts.
• Dependency Updates: Updated @willbooster/wb to 20.1.1 and build-ts to 21.0.4 in package.json and bun.lock.
• Configuration Refinement: Simplified bunfig.toml by updating the minimumReleaseAge and significantly cleaning up the minimumReleaseAgeExcludes list.
• Build Automation: Updated .lefthook/post-merge/prepare.sh to automatically remove node_modules if critical bunfig.toml settings change during a merge.

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: .github/workflows/** (4)
  • .github/workflows/close-comment.yml
  • .github/workflows/release.yml
  • .github/workflows/semantic-pr.yml
  • .github/workflows/test.yml

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.

---

The agent runs a task so long, But shells will cut it with a gong. With nohup now the job will stay, And verify the code all day.

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 updates agent guidelines across several documentation files to advise running long-running verification commands detached via nohup to avoid shell timeouts. It also updates dependency versions in package.json and bun.lock, modifies bunfig.toml configuration (specifically minimumReleaseAge and its excludes), adds .docker.env to .gitignore, and updates the post-merge hook to clear node_modules if key bunfig.toml settings change. Feedback is provided to refine the regular expression in the post-merge hook to prevent false positives when matching configuration keys.

[gemini-code-assist]

The regular expression ^[+-] *(globalStore|linker|publicHoistPattern) matches any line starting with + or - followed by spaces and any of the keywords as a prefix (e.g., linkerOpts, globalStorePath). To prevent potential false positives from future configuration keys or comments, anchor the keywords with a word boundary (\b) or match the assignment operator (*=).

Suggested change

	if git diff --no-color -U0 ORIG_HEAD HEAD -- '*bunfig.toml' | grep --quiet -E '^[+-] *(globalStore|linker|publicHoistPattern)'; then rm -Rf -- 'node_modules'; fi
	if git diff --no-color -U0 ORIG_HEAD HEAD -- '*bunfig.toml' | grep --quiet -E '^[+-] *(globalStore|linker|publicHoistPattern) *='; then rm -Rf -- 'node_modules'; fi