{"version":"2.1.224","anchor":"eval-authoring-guidance-had-two-wrong-field-names","canonical_anchor":"eval-authoring-guidance-had-two-wrong-field-names","heading":"Eval-authoring guidance had two wrong field names","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/eval-authoring-guidance-had-two-wrong-field-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Eval-authoring guidance had two wrong field names\n\nPlugin eval guidance now names the real fields, suite.plugins and costUsd.\n\n**What**\n\nThe guidance for writing plugin evals now names the fields that actually exist: `suite.plugins` for checking the plugin loaded, and `costUsd` for the cost figure in `aggregate-result.json`. It previously said `plugins` and `cost_usd`.\n\n**Evidence**\n\n`The pilot's top-level \\`costUsd\\` in \\`aggregate-result.json\\``\n\n- Area: Plugins\n- Names: `suite.plugins`, `costUsd`, `aggregate-result.json`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}