When `openspec archive` creates a spec, it writes "TBD - created by
archiving change ..." as the spec's Purpose, and `openspec validate
--strict` accepts it. Twenty-five specs still carried it.
Each of the 25 now says what it defines, in one to three sentences
drawn from its own requirements, and each was checked against them.
The lint gains spec-purpose-placeholder: it reports a spec under
openspec/specs/ whose Purpose is the placeholder or empty, at the
placeholder's line, so an archive that creates a spec cannot land
until its Purpose is written. `--specs-dir` points it elsewhere or
turns it off. A table test covers the placeholder, an empty Purpose,
one followed directly by a requirement heading, trailing spaces,
Windows line endings, a written Purpose, a spec with no Purpose, and
a placeholder outside the section. docs/testing.md lists the rule.
cgalo5758
db1bf7c287