PR-13: migrate coords/vectors to v2 (#454)

[charliecreates]

Stack step PR-13 in the issue #454 migration chain.

• Issue: Simplify CSPICE parity runner from first principles #454
• Head: charlie/issue-454-v2-pr14-migrate-coords-vectors-v2
• Base: charlie/issue-454-v2-pr13-geometry-gf-group12

[github-actions]

orrery preview: https://pr-513.orrery-c4f.pages.dev/

[charliecreates]

The migration is mechanically consistent, but it likely weakens validation by using an empty contract.result schema across methods. Additionally, setting global 1e-12 tolerances introduces a potentially flaky behavioral change for trig/angle-heavy transforms. Finally, switching from an explicit uses: workflows/legacy/coords-vectors.basic@v1 to an unparameterized invokeLegacyCall risks subtle parity semantics drift if defaults differ.

Summary of changes

What changed

• Migrated coords/vectors parity-checking method specs from v1 to v2 schema across multiple methods.
• For each method, removed the @v1.yml spec and added a new @v2.yml spec with:
  • schemaVersion: 2
  • manifest metadata (id, kind)
  • contract section (contractMethod, canonicalMethod, aliases, and a placeholder result schema)
  • defaults.compare tolerances (tolAbs/tolRel set to 1e-12)
  • workflow.steps using op: invokeLegacyCall
  • The same cases/args/expect content as before (plus preserved per-case compare overrides like angleWrapPi: true).

Files affected

• Replaced v1 specs with v2 equivalents for:
  • axisar, georec, latrec, mtxv, mxm, mxv, recgeo, reclat, recsph, rotate, rotmat, sphrec, vadd, vcrss, vdot, vhat, vminus, vnorm, vscl, vsub.