Reproduction
On Windows with the usual Git core.autocrlf=true checkout of current main (ea544d88405590eb91b5132eb73ef28546b6b0f3):
npm run validate:skills
[viking-skills] validation failed:
- [vs-alias-mapping] SKILL.md must start with YAML frontmatter
...the same error for all 13 skills...
All 13 files do start with valid --- frontmatter. The standalone validator and runtime skill parser both match only LF delimiters (\n) in parseFrontmatter. The same Git blobs pass unchanged when checked out with LF line endings. The dist acceptance suite consequently also fails skill list/show/validate cases on Windows.
I searched all-state issues, all PR titles/bodies, and repository history for Windows, CRLF, line-ending, frontmatter, and skill-validation reports and found no existing report or pending fix.
Expected behavior
Both parser implementations should accept CRLF and LF Markdown (for example by normalizing input or matching \r?\n), and the Windows acceptance cases should see the same 13 skills as an LF checkout.
Reproduction
On Windows with the usual Git
core.autocrlf=truecheckout of currentmain(ea544d88405590eb91b5132eb73ef28546b6b0f3):All 13 files do start with valid
---frontmatter. The standalone validator and runtime skill parser both match only LF delimiters (\n) inparseFrontmatter. The same Git blobs pass unchanged when checked out with LF line endings. The dist acceptance suite consequently also fails skill list/show/validate cases on Windows.I searched all-state issues, all PR titles/bodies, and repository history for Windows, CRLF, line-ending, frontmatter, and skill-validation reports and found no existing report or pending fix.
Expected behavior
Both parser implementations should accept CRLF and LF Markdown (for example by normalizing input or matching
\r?\n), and the Windows acceptance cases should see the same 13 skills as an LF checkout.