release 0.5.1

[fabracht]

Cuts 0.5.1, a patch release.

What changed for consumers

One published-surface change since 0.5.0: the runtime dependency @laboverwire/stitch-wasm floor ^0.2.1 → ^0.2.2. stitch-wasm 0.2.2 implements the optional StoreConfig override fields that 0.5.0 already declared in its type surface but the engine did not honor (userScopeField, versionField, updatedAtField, syncTopicPrefix, responseTopicPrefix, topLevelEntities, localOnlyEntities).

• No @laboverwire/stitch API or type changes. The published surface (dist) is otherwise identical to 0.5.0.
• ^0.2.1 already permitted 0.2.2, so consumers on a fresh install were already resolving it; this makes the tested floor official.

Contents

• package.json: 0.5.0 → 0.5.1
• CHANGELOG.md: ## 0.5.1 section + fresh empty ## Unreleased

Verification

• npm run release:check passes: type-check, lint, format, 33 tests, and changelog gate all green.
• extract-changelog.mjs 0.5.1 produces the release notes the publish workflow will use.
• Build emits all entry points.

Release

After this merges, tagging v0.5.1 on the merge commit triggers release.yml (verify tag == version → check → build → npm publish --provenance → GitHub Release).