[dKosarevsky]

Summary

• Extend the existing SSE and NDJSON integrations with a pinned, development-only @streamparser/json@0.0.26 adapter.
• Add runnable SSE, NDJSON, and streaming-JSON examples; the real SSE example demonstrates broken UTF-8 decoding, reduction to [13,7], and an exact fixed replay.
• Cover JSON byte boundaries, escaped surrogate pairs, selected array elements, numeric EOF flushing, concatenated roots, truncated input, and harness emission failures.
• Prepare an opt-in GitHub-release/OIDC workflow. It verifies stable version tags, clean main ancestry, source/hash-bound candidate artifacts, and registry integrity/provenance metadata. OIDC is confined to the protected npm publishing job.

Verification

• npm run check: 52 tests, TypeScript API checks, packed ESM/TypeScript consumers; zero runtime dependencies.
• npm run demo, all three example:* commands, and npm run release:check passed locally on Node 24.
• YAML syntax parsed; release guards include negative tests for mismatched/prerelease tags, tampered archives, dirty checkouts, and commits outside main history.
• Node 20/22/24 and eventsource-parser 4.1.1 checks are provided by this PR's CI.

Approval boundary

This is preparation only. NPM_PUBLISH_ENABLED is not enabled; no npm trusted publisher, environment protection, token, tag, release, or registry publication was created. Package version stays 0.1.0; these new repository examples are not represented as already published in 0.1.0.

Before activation, separately approve/configure npm trust for agent-axiom/streamsplit, publish.yml, environment npm, direct publishing permission, GitHub environment reviewers/tag restrictions, and the opt-in variable. Current npm requirements and the two-day initial-publish deadline are documented in docs/RELEASING.md using official references checked 2026-10-08. A successful OIDC publication has not been exercised.