feat(evaluator): add evaluator contract extension with model routing

.github/workflows/add-community-bundle.md

@@ -66,7 +66,30 @@ with `[Bundle]:`. If it does not, stop without commenting.
 
 ## Step 1 - Read and Parse the Issue
 
-Read issue #${{ github.event.issue.number }} and extract these issue-form fields:
+Read issue #${{ github.event.issue.number }}.
+
+### 1a. Detect issue format
+
+The issue **must** be submitted using the GitHub issue form template
+(`Bundle Submission`). Before attempting to parse any fields, check whether
+the issue body follows the expected form structure.
+
+**Form-format indicator:** The body must contain a heading `### Bundle ID`
+(the first required field in the form template). If this heading is absent, the
+issue was submitted with a free-form body instead of the issue form.
+
+If the issue is **not** in form format:
+1. Add a comment explaining that the issue must be submitted using the
+   `Bundle Submission` issue form template. Include a link to the form:
+   `https://github.com/github/spec-kit/issues/new?template=bundle_submission.yml`
+2. Add the `validation-failed` label
+3. **Stop — do not proceed further**
+
+If the issue **is** in form format, continue to parse the fields below.
+
+### 1b. Parse form fields
+
+Extract these issue-form fields:
 
 | Field | Issue Form ID | Required |
 |-------|---------------|----------|

.github/workflows/add-community-extension.md

@@ -64,6 +64,27 @@ If it does not, stop without commenting.
 
 Read issue #${{ github.event.issue.number }}.
 
+### 1a. Detect issue format
+
+The issue **must** be submitted using the GitHub issue form template
+(`Extension Submission`). Before attempting to parse any fields, check whether
+the issue body follows the expected form structure.
+
+**Form-format indicator:** The body must contain a heading `### Extension ID`
+(the first required field in the form template). If this heading is absent, the
+issue was submitted with a free-form body instead of the issue form.
+
+If the issue is **not** in form format:
+1. Add a comment explaining that the issue must be submitted using the
+   `Extension Submission` issue form template. Include a link to the form:
+   `https://github.com/github/spec-kit/issues/new?template=extension_submission.yml`
+2. Add the `validation-failed` label
+3. **Stop — do not proceed further**
+
+If the issue **is** in form format, continue to parse the fields below.
+
+### 1b. Parse form fields
+
 Extract the following fields from the structured issue body (GitHub issue form
 fields):
 

.github/workflows/add-community-preset.md

@@ -64,6 +64,27 @@ If it does not, stop without commenting.
 
 Read issue #${{ github.event.issue.number }}.
 
+### 1a. Detect issue format
+
+The issue **must** be submitted using the GitHub issue form template
+(`Preset Submission`). Before attempting to parse any fields, check whether
+the issue body follows the expected form structure.
+
+**Form-format indicator:** The body must contain a heading `### Preset ID`
+(the first required field in the form template). If this heading is absent, the
+issue was submitted with a free-form body instead of the issue form.
+
+If the issue is **not** in form format:
+1. Add a comment explaining that the issue must be submitted using the
+   `Preset Submission` issue form template. Include a link to the form:
+   `https://github.com/github/spec-kit/issues/new?template=preset_submission.yml`
+2. Add the `validation-failed` label
+3. **Stop — do not proceed further**
+
+If the issue **is** in form format, continue to parse the fields below.
+
+### 1b. Parse form fields
+
 Extract the following fields from the structured issue body (GitHub issue form
 fields):
 

.gitignore

@@ -60,3 +60,6 @@ docs/dev
 .grok/
 .specify/
 specs/
+benchmarks/evaluator/results/
+benchmarks/evaluator/reports/
+benchmarks/reports/

extensions/catalog.community.json

@@ -1747,6 +1747,44 @@
       "created_at": "2026-07-08T00:00:00Z",
       "updated_at": "2026-07-08T00:00:00Z"
     },
+    "evaluator": {
+      "name": "Evaluator Contract",
+      "id": "evaluator",
+      "description": "Standard evaluator result contract for evidence, provenance, uncertainty, and recovery — a provider-neutral protocol for extensions that evaluate artifact quality between phases",
+      "author": "ElectroHire",
+      "version": "1.0.0",
+      "download_url": "https://github.com/electrohire/spec-kit-evaluator/releases/download/v1.0.0/evaluator.zip",
+      "repository": "https://github.com/electrohire/spec-kit-evaluator",
+      "homepage": "https://github.com/electrohire/spec-kit-evaluator",
+      "documentation": "https://github.com/electrohire/spec-kit-evaluator/blob/main/README.md",
+      "changelog": "https://github.com/electrohire/spec-kit-evaluator/blob/main/CHANGELOG.md",
+      "license": "MIT",
+      "category": "process",
+      "effect": "read-write",
+      "requires": {
+        "speckit_version": ">=1.0.0"
+      },
+      "provides": {
+        "commands": 4,
+        "hooks": 4
+      },
+      "tags": [
+        "evaluator",
+        "evidence",
+        "provenance",
+        "quality",
+        "governance",
+        "compliance",
+        "workflow",
+        "model-routing",
+        "portfolio"
+      ],
+      "verified": false,
+      "downloads": 0,
+      "stars": 0,
+      "created_at": "2026-09-02T00:00:00Z",
+      "updated_at": "2026-09-02T00:00:00Z"
+    },
     "extensify": {
       "name": "Extensify",
       "id": "extensify",

extensions/evaluator/.gitignore

@@ -0,0 +1,6 @@
+# Spec Kit Evaluator Contract Extension
+__pycache__/
+*.pyc
+*.pyo
+.pytest_cache/
+.ruff_cache/

extensions/evaluator/CHANGELOG.md

@@ -0,0 +1,17 @@
+# Changelog
+
+All notable changes to the Evaluator Contract extension will be documented in this file.
+
+## [1.0.0] - 2026-09-01
+
+### Added
+- Initial release of the Evaluator Contract extension
+- JSON Schema for evaluator results (6 outcomes, 14 finding kinds, 5 evidence kinds, 6 uncertainty levels)
+- 4 commands: `speckit.evaluator.run`, `.compose`, `.report`, `.route`
+- 3 parity scripts: Python, Bash, PowerShell
+- 4 lifecycle hooks: `after_specify`, `after_plan`, `after_tasks`, `after_implement`
+- Model routing: recommends budget/standard/premium tier per phase
+- Composition: strict/majority/optimistic strategies with contradiction detection
+- Quick-start demo: `python examples/demo.py`
+- Token-economic benchmark suite with Monte Carlo simulation
+- 70 tests with 0 regressions against spec-kit test suite

extensions/evaluator/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ElectroHire
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.