{"version":"2.1.233","anchor":"plugin-eval-stops-the-suite-when-authentication-fails","canonical_anchor":"plugin-eval-stops-the-suite-when-authentication-fails","heading":"Plugin eval stops the suite when authentication fails","tier":"soon","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/plugin-eval-stops-the-suite-when-authentication-fails","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Plugin eval stops the suite when authentication fails\n\nA failed login stops the whole eval suite instead of wasting every case.\n\n**What**\n\nAn eval run that cannot authenticate, or whose credential is rejected before any case completes, now aborts the whole suite instead of burning every remaining case on the same broken credential. The HTML report banner explains the stop, the CLI prints \"stopped: authentication failed\", and the outcome is reported separately from the two existing partial reasons, a cost ceiling and interruption. `plugin eval` remains behind an early-access check.\n\n**Details**\n\n- Individual case results carry an auth-rejected outcome with its own label in the run-status table.\n- The suite aborts once the first run comes back auth-rejected.\n- A new environment variable marks the child process spawned for the `plugin eval init` interview, and its presence suppresses report publishing.\n- The command's long description moved into the shared command-help table.\n\n**Evidence**\n\n`A run could not authenticate (or the credential was rejected before any run), so the suite stopped before every case finished.`, `a run could not authenticate \\u2014 every remaining run would fail the same way, so the suite stops here. Fix the credential above and re-run.`, `stopped: authentication failed`\n\n- Area: Plugin Eval\n- Names: `plugin eval`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}