fix(wb): run drizzle-kit and custom start scripts from the monorepo root when shared there

[exKAZUu]

Problem

Monorepos like WillBooster/smartse-zoom-bot keep drizzle.config.ts and scripts/start-production.sh at the repository root (matching Docker's WORKDIR /app), while drizzle-orm is a dependency of a sub package (packages/server). wb ran both drizzle-kit migrate and the custom start script with the sub package as cwd, so:

• drizzle-kit could not find drizzle.config.* and exited with code 1, which broke Playwright's webServer (yarn wb start --mode test) and therefore local yarn test-e2e.
• Even with the config found, root-relative paths inside scripts/start-production.sh (e.g. node_modules/.bin/wb, packages/server/dist/index.js) would not resolve from the sub package.

Project.findFile already supports the "shared file at the monorepo root" layout for Dockerfile, scripts/start-production.sh, etc.; the drizzle commands and the start-script cwd were the only places missing that fallback.

Changes

• drizzleScripts: resolve drizzle.config.* in the project directory first, then the monorepo root, and wrap drizzle-kit commands with (cd "<config dir>" && ...) because drizzle-kit resolves paths in its config against the cwd. Applied to migrate / generate / studio, the wb db <args> passthrough, and the gen-code drizzle-kit check.
• baseScripts: run a custom production start script found at the monorepo root with the root as cwd, like Docker's WORKDIR.

Verification

• New unit tests in packages/wb/test/drizzleScripts.test.ts (4 tests).
• Full @willbooster/wb test suite passes (111 tests) and yarn verify passes.
• End-to-end: built this branch's wb and ran it against smartse-zoom-bot; yarn wb start --mode test in packages/server now migrates, seeds, and serves on :8080, and the previously failing local yarn test-e2e passes (6/6).

🤖 Generated with Claude Code

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!