chore: willboosterify this repo

Author: WillBooster-bot

.cursor/rules/general.mdc

@@ -13,11 +13,12 @@ alwaysApply: true
 ## General Instructions
 
 - Create a new branch if the current branch is `main`.
-- Do not write tests unless explicitly requested.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
 - After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
   - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
   - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.

.lefthook/pre-push/check.sh

@@ -1 +1 @@
-yarn typecheck
+yarn run typecheck

.yarn/plugins/plugin-auto-install.cjs

@@ -30,4 +30,4 @@ plugins:
     path: .yarn/plugins/plugin-auto-install.cjs
     spec: 'https://github.com/WillBooster/yarn-plugin-auto-install/releases/download/v2.0.7/index.cjs'
 
-yarnPath: .yarn/releases/yarn-4.12.0.cjs
+yarnPath: .yarn/releases/yarn-4.13.0.cjs

.yarn/releases/yarn-4.12.0.cjs

@@ -7,11 +7,12 @@
 ## General Instructions
 
 - Create a new branch if the current branch is `main`.
-- Do not write tests unless explicitly requested.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
 - After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
   - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
   - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.

.yarn/releases/yarn-4.13.0.cjs

@@ -7,11 +7,12 @@
 ## General Instructions
 
 - Create a new branch if the current branch is `main`.
-- Do not write tests unless explicitly requested.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
 - After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
   - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
   - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.

.yarnrc.yml

@@ -7,11 +7,12 @@
 ## General Instructions
 
 - Create a new branch if the current branch is `main`.
-- Do not write tests unless explicitly requested.
+- Write tests ONLY if explicitly requested.
+  - Make sure to continue to modify the tests and code until the tests pass.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
 - After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+- Once you have verified your changes, commit and push them to the current (non-main) branch then create a PR via `gh`.
   - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
   - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.

AGENTS.md

@@ -9,8 +9,8 @@ pre-push:
 pre-commit:
   commands:
     cleanup:
-      glob: '*.{cjs,css,cts,htm,html,js,json,json5,jsonc,jsx,md,mjs,mts,scss,ts,tsx,vue,yaml,yml}'
-      run: yarn lint-staged
+      glob: '*.{astro,cjs,css,cts,gql,htm,html,java,js,json,json5,jsonc,jsx,md,mjs,mts,scss,svelte,ts,tsx,vue,yaml,yml}'
+      run: yarn run format && yarn run lint-fix && git add -- {staged_files}
     check-migrations:
       glob: '**/migration.sql'
       run: |-