132 main-spec requirements are over OpenSpec 1.14.1's 500-character limit, so validate --all --strict fails on 42 specs #156
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OpenSpec 1.14.1 (pinned in #155) made a requirement description over 500 characters a warning, so
openspec validate --strictfails on it. On 2026-10-08,openspec validate --all --stricton this repository reported 132 such requirements across 42 of the 52 specs. Nothing runs that check today, so nothing is blocked, but the specs no longer pass the CLI's own strict check.Braid's runs are not affected: their only strict check is
openspec validate <change> --strict, which in 1.14.1 flags only ADDED requirements in the change.What it needs
# spec: <capability>/<scenario>): a renamed scenario needs its tag renamed.openspec validate --all --strict, so it stays clean.Done when
openspec validate --all --strictreports no long-requirement warning, and the fast lane still passes.132 main-spec requirements are over OpenSpec 1.14.1's 500-character limit, soto 132 main-spec requirements are over OpenSpec 1.14.1's 500-character limit, sovalidate --all --strictfails on 47 specsvalidate --all --strictfails on 42 specsShipped as
shorten-long-requirements, in two passes.spec:tag still resolves. A reviewer agent checked each against the original, fact by fact.tests/unit/test_spec_limits.pynow fails on any main-spec requirement over 500 characters, naming it. It also fails on a stale entry in its known-exceptions list, which is empty.Verified. After the archive (
2c0561a),openspec validate --all --strictreports no long requirement (59 of 59 valid), no test'sspec:tag was left without its scenario, and the fast lane passes with the new test. It changes no code, so it was pushed with[skip ci].