feat(contract-validator): add gate contract versioning

- design-gate.md and data-gate.md declare gate_contract: v1
- domain-consultation.md Gate Command Reference includes Contract column
- validate_workflow_integration now checks contract version compatibility
- Tests added for match, mismatch, and missing contract scenarios

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

plugins/contract-validator/skills/mcp-tools-reference.md

@@ -16,7 +16,7 @@ Available MCP tools for contract-validator operations.
 | `validate_compatibility` | Check two plugins for conflicts |
 | `validate_agent_refs` | Check agent tool references exist |
 | `validate_data_flow` | Verify data flow through agent sequence |
-| `validate_workflow_integration` | Check domain plugin exposes required advisory interfaces |
+| `validate_workflow_integration` | Check domain plugin exposes required advisory interfaces and gate contract version |
 
 ### Report Tools
 | Tool | Description |
@@ -57,8 +57,9 @@ Available MCP tools for contract-validator operations.
 ### Workflow Integration Check
 ```
 1. validate_workflow_integration(plugin_path, domain_label)  # Check single domain plugin
-2. For each domain in domain-consultation.md detection rules:
-     validate_workflow_integration(domain_plugin_path, domain_label)
+2. validate_workflow_integration(plugin_path, domain_label, expected_contract="v1")  # With contract version check
+3. For each domain in domain-consultation.md detection rules:
+     validate_workflow_integration(domain_plugin_path, domain_label, expected_contract)
 ```
 
 ## Error Handling

plugins/contract-validator/skills/validation-rules.md

@@ -35,7 +35,9 @@ Rules for validating plugin compatibility and agent definitions.
 2. Gate command produces binary PASS/FAIL output
 3. Review command exists (WARNING if missing, not ERROR)
 4. Advisory agent exists referencing the domain label
-- Severity: ERROR for missing gate, WARNING for missing review/agent
+5. Gate command declares `gate_contract` version in frontmatter
+6. If expected version provided, gate contract version matches expected
+- Severity: ERROR for missing gate, WARNING for missing review/agent or contract mismatch, INFO for missing contract
 
 ## Severity Levels
 

plugins/data-platform/commands/data-gate.md

@@ -1,5 +1,6 @@
 ---
 description: Data integrity compliance gate (pass/fail) for sprint execution
+gate_contract: v1
 arguments:
   - name: path
     description: File or directory to validate

plugins/projman/skills/domain-consultation.md

@@ -154,10 +154,12 @@ This pattern ensures domain expertise stays in domain plugins while projman orch
 
 ## Gate Command Reference
 
-| Domain | Gate Command | Review Command | Advisory Agent |
-|--------|--------------|----------------|----------------|
-| Viz | `/design-gate <path>` | `/design-review <path>` | `design-reviewer` |
-| Data | `/data-gate <path>` | `/data-review <path>` | `data-advisor` |
+| Domain | Gate Command | Contract | Review Command | Advisory Agent |
+|--------|--------------|----------|----------------|----------------|
+| Viz | `/design-gate <path>` | v1 | `/design-review <path>` | `design-reviewer` |
+| Data | `/data-gate <path>` | v1 | `/data-review <path>` | `data-advisor` |
 
 Gate commands return binary PASS/FAIL for automation.
 Review commands return detailed reports for human review.
+
+**Contract Version:** Gate commands declare `gate_contract: vN` in their frontmatter. The version in this table is what projman expects. If a gate command bumps its contract version, this table must be updated to match. The `contract-validator` plugin checks this automatically via `validate_workflow_integration`.

plugins/viz-platform/commands/design-gate.md

@@ -1,5 +1,6 @@
 ---
 description: Design system compliance gate (pass/fail) for sprint execution
+gate_contract: v1
 arguments:
   - name: path
     description: File or directory to validate