{"version":"2.1.269","anchor":"eval-scaffold-script-now-warns-explicitly-when-skipped","canonical_anchor":"eval-scaffold-script-now-warns-explicitly-when-skipped","heading":"Eval scaffold_script now warns explicitly when skipped","tier":"notice","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/eval-scaffold-script-now-warns-explicitly-when-skipped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Eval scaffold_script now warns explicitly when skipped\n\nEval cases with a `scaffold_script` now warn explicitly when `--scaffold` wasn't passed instead of silently skipping it\n\n**What**\n\nWhen an eval case defines a `scaffold_script` (author-supplied setup code) but the `--scaffold` flag wasn't used, Claude Code now prints an explicit warning that the script won't run and that the case will execute against an unstaged workspace, rather than skipping it silently.\n\n**Why**\n\nThis makes it clear when a case is running without its intended setup, and reminds you that `--scaffold` runs author-supplied bash code as you, so it should only be passed for eval suites you trust.\n\n- Area: Plugin Eval\n- Names: `--scaffold`, `scaffold_script`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}