132 main-spec requirements are over OpenSpec 1.14.1's 500-character limit, so validate --all --strict fails on 42 specs #156

Closed
opened 2026-10-08 23:17:21 -04:00 by cmoriarty · 1 comment
Owner

OpenSpec 1.14.1 (pinned in #155) made a requirement description over 500 characters a warning, so openspec validate --strict fails on it. On 2026-10-08, openspec validate --all --strict on 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

  • Shorten each long requirement, mostly by moving examples and edge cases into scenarios, or splitting one requirement into several that each state one behaviour. 1.14.1's specs instruction describes how to split without losing scenarios.
  • Keep the scenarios' tests tagged (# spec: <capability>/<scenario>): a renamed scenario needs its tag renamed.
  • Then decide whether a lane should run openspec validate --all --strict, so it stays clean.

Done when

openspec validate --all --strict reports no long-requirement warning, and the fast lane still passes.

OpenSpec 1.14.1 (pinned in #155) made a requirement description over 500 characters a warning, so `openspec validate --strict` fails on it. On 2026-10-08, `openspec validate --all --strict` on 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 - Shorten each long requirement, mostly by moving examples and edge cases into scenarios, or splitting one requirement into several that each state one behaviour. 1.14.1's specs instruction describes how to split without losing scenarios. - Keep the scenarios' tests tagged (`# spec: <capability>/<scenario>`): a renamed scenario needs its tag renamed. - Then decide whether a lane should run `openspec validate --all --strict`, so it stays clean. ## Done when `openspec validate --all --strict` reports no long-requirement warning, and the fast lane still passes.
cmoriarty changed title from 132 main-spec requirements are over OpenSpec 1.14.1's 500-character limit, so validate --all --strict fails on 47 specs to 132 main-spec requirements are over OpenSpec 1.14.1's 500-character limit, so validate --all --strict fails on 42 specs 2026-10-08 23:17:30 -04:00
Author
Owner

Shipped as shorten-long-requirements, in two passes.

  • First pass: 103 requirements that no in-flight change touched.
  • Second pass: 23 more, after tonight's changes were archived: the ones they modified or added, plus one whose text an archive had changed in the meantime.
  • How: each states its behaviour in 500 characters or fewer. The examples, lists, edge cases and incident references moved into scenarios, existing ones or new ones. No requirement header or scenario name changed, so every test's spec: tag still resolves. A reviewer agent checked each against the original, fact by fact.
  • #170's requirements: that session shortened its own 8 when it archived.
  • The fast lane: tests/unit/test_spec_limits.py now 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 --strict reports no long requirement (59 of 59 valid), no test's spec: 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].

Shipped as `shorten-long-requirements`, in two passes. - **First pass:** 103 requirements that no in-flight change touched. - **Second pass:** 23 more, after tonight's changes were archived: the ones they modified or added, plus one whose text an archive had changed in the meantime. - **How:** each states its behaviour in 500 characters or fewer. The examples, lists, edge cases and incident references moved into scenarios, existing ones or new ones. No requirement header or scenario name changed, so every test's `spec:` tag still resolves. A reviewer agent checked each against the original, fact by fact. - **#170's requirements:** that session shortened its own 8 when it archived. - **The fast lane:** `tests/unit/test_spec_limits.py` now 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 --strict` reports no long requirement (59 of 59 valid), no test's `spec:` 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]`.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#156
No description provided.