fix: warn agents about yarn verify Deploy.s.sol naming requirement

[austintgriffith]

Problem

yarn verify fails with No such file or directory if the deploy script isn't named exactly Deploy.s.sol. VerifyAll.s.sol hardcodes the broadcast artifact path to broadcast/Deploy.s.sol/<chainId>/run-latest.json — any custom script name produces this error. Discovered in the wild with DeployMetaMultiSigWallet.s.sol.

Two previous PRs (#112, #113) tried to fix this but had issues:

• fix: warn that yarn verify requires Deploy.s.sol script name #112: Warning placed after the command (too late); said "silently fails" (wrong — it throws No such file or directory); bundled a stale gas timestamp change
• fix: place yarn verify script-name warning BEFORE the command #113: Fixed placement but still said "silently fails"; suggested renaming the script as primary resolution (risky — breaks CI/tooling); warning was one dense run-on sentence with no blank line before the code fence

Fix

Adds a clean ⚠️ pre-condition callout before yarn verify that:

• Uses the accurate error message (No such file or directory, not "silent failure")
• Steers agents toward the Foundry fallback instead of renaming files
• Has proper blank-line separation from the code fence

What this does NOT fix

The root cause is in VerifyAll.s.sol in scaffold-eth — it should derive the broadcast path from the actual script name rather than hardcoding Deploy.s.sol. That's a scaffold-eth PR, not an ethskills change.

Closes #112, closes #113

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
site	Ready	Preview	Mar 8, 2026 2:38am