Delta validation reads only the first line of a requirement body (false SHALL/MUST errors on hard-wrapped text)

[andrulli85]

Version: 1.5.0

Repro: a delta spec requirement whose body is hard-wrapped markdown, with SHALL appearing after the first physical line:

### Requirement: Barge-in takes the turn
When the talk key is pressed while an agent response is in flight, the loop
SHALL stop playback immediately, ...

openspec validate fails with:

✗ [ERROR] voice-loop/spec.md: ADDED "Barge-in takes the turn" must contain SHALL or MUST

openspec show <change> --json --deltas-only confirms the parsed requirement text is only the first physical line — every hard-wrapped body is truncated there, so the SHALL/MUST check (and any consumer of the JSON text) sees one line of an N-line requirement.

Scope note: openspec archive copies the markdown content, so the ARCHIVED specs keep the full multi-line body — the truncation appears to affect validation and the JSON view only. Still, the same requirement is valid or invalid depending on where the author's editor wraps a line.

Expected: requirement text spans until the next ####/### heading (or blank-line rule, but consistently), so hard-wrapped prose validates and round-trips.

Workaround: keep each requirement body on one long line.

[mc856]

Fixed on current main by #1281. The unified reader (src/core/parsers/requirement-text.ts) captures the full requirement body instead of stopping at the first physical line, so the hard-wrapped repro from this issue now behaves: openspec validate passes for the delta, and show --json --deltas-only returns the complete multi-line text — verified on main (a5bfeda).

One scope note: the truncation was not delta-only. Main-spec validation shared the same single-line extraction (validator.ts used it for the body-keyword check at three call sites), so a hard-wrapped requirement in a main spec failed validate <spec> the same way — #1281 unified both paths, and that case also validates clean on main now. Looks closable.

[clay-good]

Closing as fixed by #1281, shipped in v1.6.0. Requirement reading was unified in src/core/parsers/requirement-text.ts, so a requirement body now spans until the next heading rather than the first newline.

Verified with your exact repro on current main: the hard-wrapped SHALL requirement validates clean, and show --json --deltas-only returns the full multi-line text. Your editor may now wrap lines wherever it likes without changing your compliance posture.