v0.2.0

v0.2.0 - Node 22 is the floor

Breaking changes: the declared Node floor moves from 20 to 22. Node 20
reached end of life on 2026-04-30, and engines >=20 told consumers that running
there was sanctioned. Be exact about what this does: npm checks engines and
emits EBADENGINE, but it is a WARNING and the install still proceeds. It is a
refusal only where you set engine-strict=true; pnpm refuses by default. No
source changed, so the code would most likely still run on Node 20 -- what
changed is that it is no longer claimed to.

Tested on Node 22, 24 and 26, on Linux and Windows.

This release adds a README. The package has been on npm with no README
at all, so its page showed nothing you could read before installing it.

Every TypeScript example in it is typechecked against the package's own source
rather than written from reading it. That caught four wrong examples before
release -- an interface method that does not exist, a required field left out,
a wrong argument shape, and a missing import. One claim was not just wrong but
backwards, describing a protection the code does not provide; it now states the
actual limit instead.

v0.1.0

v0.1.0 - Perplexity for the TypeScript port

@particle-academy/prism-perplexity targets Perplexity's Agent API.

Not /chat/completions, which Perplexity retires on 2026-09-27. If you are
carrying chat-completions-era search filters, the Agent API rejects them with a
400 on an unknown field.

The transport is injected, so the surface runs with no network and no key.

KNOWN GAPS, and they are not small: the cross-language corpus currently has ONE
of seventeen rows agreeing (G-29 through G-32). An absent usage is [] in the
reference and {} in both ports; the refusal identifier differs in shape rather
than in name; a JSON array body is misreported by the reference itself. Read the
gaps register before relying on cross-language identity here.

Also missing relative to the reference: usage.cost.total_cost is not mapped.
Perplexity is one of only two providers that price a request in their own
response, so that omission costs you the only cost figure that is not an
estimate.

This is the first published version, and 0.1.0 is meant literally: a focused,
working slice rather than a 1.0 in disguise.

It is published from CI through npm trusted publishing, with a provenance
attestation you can verify. The 0.0.0 that claimed this name was hand-published
and carries none, which is exactly why it was burned rather than used.