Repository navigation
The action now reads the heading aliases in IntentSpec SPEC.md section 2. When ## Objective is absent, ## Problem and then ## Why carry the objective, and ## Proposed outcome stands in for an absent ## Outcomes. The first heading present is the section, even when it is empty, and aliases never merge. ## What is not an alias: it usually states the solution, and an outcome is the observable result.
What changes for you: a sectioned intent.md that wrote its objective only under ## Problem or ## Why used to fail with "required property 'objective'" for a field it visibly had. It now validates. A document using the canonical headings validates exactly as under v1.2.4.
It also keeps this action in step with the normalization corpus published at intentspec.org, which gains four cases for these aliases. v1.2.4 fails three of them.
@v1 now points at this release. Nothing to change if you use @v1; bump to @v1.2.5 if you pin exact versions.