mirror of
https://github.com/Fission-AI/OpenSpec.git
synced 2026-10-02 05:24:34 +08:00
* fix(schemas): tell agents the requirement length limit The validator flags requirement text over 500 characters, but the specs instruction never mentioned the limit, so agents kept writing requirements that tripped it. State the limit and how to split, and make the validator message say how to fix it. Part of #1976 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(schemas): match requirement length boundary * test(validation): lock requirement length boundary * fix(schemas): keep MODIFIED requirements whole under the length hint The 500-character check is an INFO hint, not an error. Splitting or trimming an existing requirement under MODIFIED drops scenarios the main spec still has, which validate and archive reject. Say so, and scope the splitting advice to new requirements. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>