v1.2.2 — enforceable parity via the published normalization corpus

Vendoring kept this Action's normalizer aligned with the IntentSpec reference by convention. Now it is enforceable.

test/normalization-corpus.json is the same file run by pathmodeio/intentspec and by Pathmode's browser and MCP parsers: markdown in, exact normalized object out. Accept/reject fixtures cannot catch two implementations agreeing that a document is valid while disagreeing about what it says, which is the whole promise of one format.

On its first run it caught exactly that. The reference accepted ASCII -> for edge cases while the shipped Pathmode parsers accepted → and :, so the same document produced different edge cases depending on which tool read it. All implementations now accept all four documented forms:

- **scenario**: expected behavior
- scenario: expected behavior
- scenario -> expected behavior
- scenario → expected behavior

Also fixes package metadata: the package name was cli, the license field said ISC while LICENSE is MIT, and the author was blank.

Usage is unchanged: uses: pathmodeio/validate-intentspec-action@v1