v0.2.0

Read the corpus fixture from the directory it is tracked in

CI has been red on main since 2026-09-01. The corpus test read
__DIR__.'/../fixtures/...' while the file is tracked at tests/Fixtures/...,
capital F. Windows resolves both to the same directory, so it passed on every
developer machine and failed on Linux CI from the day it was written.

Identical to the defect fixed in prism-harness earlier today, in a second
repository, found by sweeping for the shape rather than by waiting for it to be
reported. A sweep of every repo says these two were the only ones: the other
four that read a JSON fixture this way track it in a lowercase directory and
agree with themselves.

The package was never broken. 123 tests, 633 assertions, types and formatting
all green once the path matched -- the whole failure was one character of case
in a path, invisible to everyone who develops on a case-insensitive filesystem.

Worth stating because it is the second time today: a green local run is not
evidence about CI. The two disagree in exactly the ways a developer machine
hides, and this class of bug cannot be caught by running the suite locally at
all.