v0.2.0

Dependency alignment: @pegma/storage-core advances from 0.3.0 to 0.4.0, matching the pin used by webhooks, mail, and identity so host dependency trees resolve a single storage-core. No behavioural or public API change; callers must now supply a storage-core 0.4.0 Store/transaction, which is the breaking composition change that moves the version to 0.2.0.

v0.1.1

Security fixes from the 2026-07-29 pass over docs/securityscan.md.

Library:

• details keys that name an inherited accessor (__proto__) are stored instead of being silently dropped, so an event round-trips as the bytes that were submitted.
• occurredAt requires a real ISO 8601 instant: the right shape, a day-of-month that exists in its month, and a parsable value. Date.parse-only formats such as March 3, 2020, and dates it normalizes such as 2026-02-30T00:00:00Z, are refused.
• decodeAuditEvent fails on a row it cannot read faithfully rather than coercing it. An unknown stored actor kind no longer decodes as a principal, and a null or missing field no longer becomes "null"/"undefined".
• sweep validates a supplied limit as a positive safe integer, so NaN can no longer leave a permanent deletion unbounded.

Release pipeline:

• Release validation refuses a published manifest defining preinstall, install, or postinstall.
• runNpm never builds a shell command line; the Windows fallback that passed unescaped arguments through cmd.exe is gone.
• The publish workflow verifies the npm CLI tarball against a reviewed sha512 before installing the tool that packs and publishes the release.

Stricter validation only — no public type or signature changes. Full dispositions, including three findings disputed with reasoning, are in docs/securityscan.md.