From 54456cf5a42eb8a8c070ff26a8a0274dd5dbeaa7 Mon Sep 17 00:00:00 2001 From: Bill Murdock Date: Tue, 12 May 2026 15:12:10 -0400 Subject: [PATCH] fix: remove hardcoded attribute count limits from assessment schema The schema enforced a maximum of 25 on attributes_assessed, attributes_skipped, attributes_not_assessed, attributes_total, and findings. The assessor count has grown beyond 25, causing the validate CI job to fail on legitimate submissions. Removes the upper bounds entirely so the schema does not need updating each time a new assessor is added. Co-Authored-By: Claude Sonnet 4.6 --- .../contracts/assessment-schema.json | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/specs/001-agentready-scorer/contracts/assessment-schema.json b/specs/001-agentready-scorer/contracts/assessment-schema.json index a51d239c..4f2bdedd 100644 --- a/specs/001-agentready-scorer/contracts/assessment-schema.json +++ b/specs/001-agentready-scorer/contracts/assessment-schema.json @@ -57,31 +57,26 @@ }, "attributes_assessed": { "type": "integer", - "minimum": 0, - "maximum": 25 + "minimum": 0 }, "attributes_skipped": { "type": "integer", "minimum": 0, - "maximum": 25, "description": "Canonical key name for skipped/not-assessed attributes" }, "attributes_not_assessed": { "type": "integer", "minimum": 0, - "maximum": 25, "description": "Deprecated alias for attributes_skipped (backwards compatibility)" }, "attributes_total": { "type": "integer", "minimum": 10, - "maximum": 25, - "description": "Total attributes in assessment (may be < 25 if --exclude was used)" + "description": "Total attributes in assessment (may be fewer if --exclude was used)" }, "findings": { "type": "array", "minItems": 10, - "maxItems": 25, "items": { "type": "object", "required": ["attribute", "status"],