Versioning and deprecation

// Three version numbers, and what each one versions.
import { createRequire } from 'node:module';

import { SPEC_VERSION, validate } from '@payvol/core';
import { DRAFT_VERSION, validateArtifact } from '@payvol/core/draft02';

// The third number: the npm version of the package these came from. It is read
// from the package's own manifest, which every Payvol package exports as
// `./package.json`. That export was missing before 0.3.2.
const require_ = createRequire(import.meta.url);
console.log('npm package   ', require_('@payvol/core/package.json').version, '(the code)');
console.log('shipped profile', SPEC_VERSION, '(the artifact format)');
console.log('draft profile ', DRAFT_VERSION, '(under development, may change)');

// A package at 0.4.x writing a 0.1 artifact is normal, not a mismatch: the
// three numbers above version three different things.
const v01 = {
  version: SPEC_VERSION,
  type: 'transfer',
  recipient: 'payee::1220aabbcc',
  instrument: 'DSO::1220be58/Amulet',
};
console.log('0.1 accepted  ', validate(v01).valid);

// Each profile refuses the other by name rather than half understanding it.
const asDraft = validateArtifact({ payload: v01, envelope: { security: 'unsignedAllowed' } });
console.log('0.1 as draft  ', asDraft.valid, asDraft.valid ? '' : asDraft.code);
console.log(
  '0.2 as v0.1   ',
  validate({ ...v01, version: DRAFT_VERSION }).valid,
  validate({ ...v01, version: DRAFT_VERSION }).code ?? '',
);

npm package    0.4.0 (the code)
shipped profile 0.1 (the artifact format)
draft profile  0.2-draft (under development, may change)
0.1 accepted   true
0.1 as draft   false UNKNOWN_VERSION
0.2 as v0.1    false UNKNOWN_VERSION

Output from @payvol/core version 0.4.0 and its sibling packages, installed from npm, on 2026-10-18.