[dKosarevsky]

Release candidate

Prepare @agent-axiom/streamsplit@0.1.1 to refresh the stale npm installation text and package the documentation/tooling improvements already merged.

• Bump package.json and both lockfile version fields together.
• Add and package CHANGELOG.md; retain the zero-runtime-dependency/API contract.
• Update the local archive example and validate changelog/version consistency.
• Clarify that the opt-in Actions variable is repository-scoped, and that prevent-self-review requires a second reviewer.

Verification

• npm run release:check: 54 tests, TypeScript API checks, packed ESM/TypeScript consumers, short demo, and archive build passed locally.
• npm run demo and git diff --check passed.
• All 15 dist files in the candidate are byte-identical to the published 0.1.0 archive.
• Candidate contains 29 package files, including the changelog and corrected installation documentation.
• SHA-256: 616c9ae69e9534eaeb73948f7f58ce992b077f0d918b47996da3056049b493f5.
• Exact commit ec3be0516ddaffc715d875df8deb1300fc58d72a passed all four CI jobs: Node 20/22/24 and eventsource-parser 4.1.1.
• Fetched the exact remote commit, verified its tree, reran release:check from a clean checkout, and verified the manifest's source commit plus archive SHA-256/npm integrity.

Publication boundary

This is a draft preparation PR. No Git tag, GitHub release, npm publication, trusted-publisher grant, environment protection, or activation variable was created. Registry check still shows 0.1.0 as the latest stable version. Publication and persistent npm access need separate explicit approval; a new publisher must complete a successful publish within two days of setup.

The final merged release commit must be checked again before publishing; an archive's SHA-256 does not itself constitute npm provenance.