ci: worktrunk config

[therealemjy]

Changes

• added Worktrunk configuration to prepare new worktrees automatically. Upon creating a new worktree using Worktrunk (e.g.: wt switch feat/my-new-feature --create), .env files will be automatically generated from the main workspace and dependencies will be installed so that the new worktree is fully operational
• added a Yarn plugin to run yarn generate after installs

[changeset-bot]

⚠️ No Changeset found

Latest commit: a2aeb92

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dapp-preview	Ready	Preview	Aug 2, 2026 1:15pm
dapp-testnet	Ready	Preview	Aug 2, 2026 1:15pm
venus.io	Ready	Preview	Aug 2, 2026 1:15pm

[greptile-apps]

Greptile Summary

This PR automates Worktrunk worktree setup and moves post-install generation into a Yarn plugin.

• Seeds and shares application environment files across worktrees.
• Installs dependencies automatically during worktree creation.
• Runs the repository generation pipeline after Yarn installations.
• Tracks the custom Yarn plugin while continuing to ignore other Yarn-managed files.

Confidence Score: 4/5

The PR does not appear safe to merge until shared environment credentials are isolated from branch-controlled worktree installation and generation code.

The reply states that local environment values are not sensitive, but the repository templates identify numerous third-party API credentials, and current HEAD still links those files before executing scripts and generation commands controlled by the checked-out branch.

Files Needing Attention: .config/wt.toml, .yarn/plugins/yarn-plugin-generate-after-install.cjs, and .yarnrc.yml

Important Files Changed

Filename	Overview
.config/wt.toml	Adds automatic worktree environment setup and dependency installation; the previously reported credential-exposure path remains present.
.yarn/plugins/yarn-plugin-generate-after-install.cjs	Adds an installation hook that invokes the repository generation pipeline and participates in the outstanding exposure path.
.yarnrc.yml	Registers the new local after-install Yarn plugin.
package.json	Removes the root postinstall command because generation is now initiated by the Yarn plugin.
turbo.json	Removes the obsolete postinstall task configuration.
.gitignore	Allows the new Yarn plugin directory to be tracked while ignoring other Yarn-managed content.

_{Reviews (2): Last reviewed commit: "ci: run generate script after installing" | Re-trigger Greptile}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 89a38dd42e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

Coverage Report for ./apps/evm

Status	Category	Percentage	Covered / Total
🔵	Lines	77.81%	50186 / 64490
🔵	Statements	77.81%	50186 / 64490
🔵	Functions	72.5%	1532 / 2113
🔵	Branches	85.13%	7307 / 8583

File Coverage

No changed files found.

Generated in workflow #14015 for commit a2aeb92 by the Vitest Coverage Report Action

[therealemjy]

@greptile

[cuzz-venus]

LGTM