Repository navigation
BUG: openspec validate --strict succeeds, but openspec archive fails validation #498
Description
I'm getting these errors on archive
Proposal warnings in proposal.md (non-blocking):
⚠ Requirement must contain SHALL or MUST keyword
⚠ Requirement must have at least one scenario
⚠ Requirement must contain SHALL or MUST keyword
⚠ Requirement must have at least one scenario
⚠ Requirement must contain SHALL or MUST keyword
⚠ Requirement must have at least one scenario
⚠ Requirement must contain SHALL or MUST keyword
⚠ Requirement must have at least one scenario
But validate succeeds with no issue. The headers in question I THINK are because my agent put in extra headers into the spec
---
### Documentation Requirements <---- I think this is the issue
### Requirement: AI Application Documentation
Teams building AI applications SHALL document agent definitions, prompts, and integration patterns.
#### Scenario: Agent Definition Documentation
yadayadawhatever
while I could just get my agent to stop doing that, and I probably will, I don't think the validation should succeed with openspec validate and fail when I go to archive it.
Activity
docs(openspec): bulletproof parser-fidelity proposal with empirical e…
docs(openspec): deepen parser-fidelity proposal — add Fission-AI#418,…
docs(openspec): third pass — reject recognition tightening, add fence…
fix(parser): unify the requirement reader, fence/metadata/multi-line …
Fix `archive` exit code on validation failure (Fission-AI#1311)
refactor: unify requirement reader and surface Fission-AI#498 (Fissio…
fix(review): 双语化 spec-structure 结构诊断正则（review F1 major）
合并英文上游 v1.6.0-beta.1 + 双语解析保住 + 增量汉化 (#5)
fix(parser): ignore delta headers that are not "### Requirement:"
fix(parser): stop delta section dividers from becoming phantom requir…