Release v0.2.0: tag emissions schedule + fix Node ESM resolution

[Gio2050]

Why

afi-core pins afi-math so it can derive totalRewardPool from the emissions schedule, but two problems made that pin unusable:

1. No durable ref to pin to. afi-math had zero tags, so afi-core pinned a raw commit SHA — and the SHA it picked (2042ed3, 2025-12-16) predated the emissions module (src/emissions/emissionsSchedule.ts, added in 1a524d3 on 2026-01-25, 40 days later). The pinned tree didn't even contain emissions/.
2. The package wasn't importable under Node ESM. src/index.ts re-exported submodules with extensionless specifiers ("./timeValue/timeValue"). The package is "type": "module", so tsc emits those verbatim and Node's ESM loader throws Cannot find module .../dist/timeValue/timeValue. The library only resolved under bundlers/vitest, never in a plain Node-ESM consumer like afi-core.

This PR cuts the first tagged release, v0.2.0, and makes it actually consumable.

What

• fix(esm) — add explicit .js extensions to the relative re-exports in src/index.ts so the compiled dist/index.js resolves under Node's native ESM loader. Verified with a Node import() smoke test (emissions.buildEmissionsSchedule is now reachable).
• chore(release): v0.2.0 — bump package.json 0.1.0 → 0.2.0 and add a CHANGELOG.md. Minor bump because it's additive (the emissions schedule) over 0.1.0.

Verification

• npm run build ✅
• npm test ✅ — 92/92 passing (4 suites)
• Node ESM smoke import of dist/index.js ✅ — emissions exports present

Tag

v0.2.0 is tagged locally on the release commit (which contains src/emissions/). The tag push was blocked by this environment's egress policy — pushes to refs/tags/* return 403 (only the feature branch ref is writable), and per the proxy rules I don't retry policy denials. Please push the tag once this merges:

git checkout main && git pull
git tag -a v0.2.0 -m "afi-math v0.2.0 — canonical emissions schedule + Node ESM fix"
git push origin v0.2.0

Until then, afi-core pins the release commit SHA (6091cbf) over git+https, which is equivalent; it can be flipped to #v0.2.0 once the tag exists.

Related

Paired with the afi-core re-pin PR (same branch name) that points afi-core at this release over git+https.

---

Generated by Claude Code