{"version":"2.1.235","anchor":"plugin-eval-results-written-inside-a-plugin-now-warn-about-c","canonical_anchor":"plugin-eval-results-written-inside-a-plugin-now-warn-about-c","heading":"plugin eval results written inside a plugin now warn about component loading","tier":"notice","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/plugin-eval-results-written-inside-a-plugin-now-warn-about-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### plugin eval results written inside a plugin now warn about component loading\n\n`plugin eval` warns when writing results inside a plugin's own directory could get picked up as plugin components\n\nWhen eval results are written under the plugin itself (no `--output-dir` given), the command now checks the destination against the plugin's layout and warns that files written there may be loaded as plugin components. Case discovery also refuses to follow symlinked directories, and logs when a directory has no `prompt.md` or `case.yaml`, so it's scanned for subcases rather than mistakenly treated as one.\n\n- Area: Plugin Eval\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}