feat: fork and onboard @unabandoned/JSONStream (vendor through, node:test suite) - #1

Follow-up to #1. The onboarding merged with the package named
`@unabandoned/JSONStream`, but **npm forbids uppercase letters in new
package names** — that name can't be published, and it can't even be
resolved as an `npm:` alias (npm fails name validation with _"name can
no longer contain capital letters"_, which is exactly what broke `npm
install` in the first repoint PR).

This renames the published package to the lowercase
**`@unabandoned/jsonstream`**.

What does **not** change:
- The GitHub repo stays `unabandoned/JSONStream`.
- Consumers keep the dependency **key** `JSONStream`, aliased to
`npm:@unabandoned/jsonstream@^1`, so `node_modules/JSONStream` and
`require('JSONStream')` are unchanged — no consumer code changes.
- The `JSONStream.parse` / `JSONStream.stringify` API is untouched.

Also updates `package` in `.unabandoned.yml` to match (validated).

`node --test test/*.js` still passes (28/28) — the rename is inert to
behaviour.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_

🤖 I have created a release *beep* *boop*
---


##
[1.4.0](jsonstream-v1.3.5...jsonstream-v1.4.0)
(2026-08-14)


### Features

* add option for emitting keys
([9aa2446](9aa2446))
* fork and onboard @unabandoned/JSONStream (vendor through, node:test
suite) ([#1](#1))
([f11ffef](f11ffef))


### Bug Fixes

* lowercase npm package name to @unabandoned/jsonstream
([#4](#4))
([76dfce6](76dfce6))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Repoints the `JSONStream` runtime dependency to
`npm:@unabandoned/jsonstream@^1`, so the abandoned upstream (and its
abandoned `through` dependency) leaves deps-sort' transitive tree. Part
of adopting JSONStream into the program — see unabandoned/JSONStream#1 /
unabandoned/JSONStream#4 and the tracking issue
unabandoned/browser-pack#3.

The dependency **key** stays `JSONStream` (aliased to
`npm:@unabandoned/jsonstream`), so `node_modules/JSONStream` and
`require('JSONStream')` are unchanged — the fork is a drop-in with the
same `JSONStream.parse` / `JSONStream.stringify` API, no code changes.

## Verification

Installed deps-sort's full tree with `@unabandoned/jsonstream` (packed
from the fork) standing in for the alias and ran the suite: **9 tests, 9
pass, 0 fail** on Node 22.22 and Node 24.19. `require('JSONStream')`
resolved to the fork.

## Ordering note

⚠️ **CI here stays red until `@unabandoned/jsonstream` is published to
npm** (unabandoned/JSONStream#4 → release → publish). `npm install`
can't resolve the alias until then; this is the expected
publish-ordering dependency, verified above via a local install of the
exact package contents. Holding ready-for-review in the meantime.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_

Repoints the `JSONStream` runtime dependency to
`npm:@unabandoned/JSONStream@^1`, so the abandoned upstream (and its
abandoned `through` dependency) leaves module-deps' transitive tree.
Part of adopting JSONStream into the program — see
unabandoned/JSONStream#1 and the tracking issue
unabandoned/browser-pack#3.

The fork is a drop-in: same `JSONStream.parse` / `JSONStream.stringify`
API, so `require('JSONStream')` is unchanged and there are no code
changes — only the dependency spec.

## Verification

Installed module-deps' full tree with `@unabandoned/JSONStream` (packed
from unabandoned/JSONStream#1) standing in for the alias and ran the
suite: **51 tests, 51 pass, 0 fail** on Node 22.22 and Node 24.19.
`require('JSONStream')` resolved to the fork.

## Ordering note

⚠️ **CI here will stay red until `@unabandoned/JSONStream` is published
to npm** — `npm install` can't resolve `npm:@unabandoned/JSONStream@^1`
until then. This is the expected publish-ordering dependency: merge +
release + publish unabandoned/JSONStream#1 first, then re-run CI on this
PR and it will go green (verified above via a local install of the exact
package contents). Holding this PR ready-for-review in the meantime.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_

Repoints the `JSONStream` runtime dependency to
`npm:@unabandoned/jsonstream@^1`, so the abandoned upstream (and its
abandoned `through` dependency) leaves insert-module-globals' transitive
tree. Part of adopting JSONStream into the program — see
unabandoned/JSONStream#1 / unabandoned/JSONStream#4 and the tracking
issue unabandoned/browser-pack#3.

The dependency **key** stays `JSONStream` (aliased to
`npm:@unabandoned/jsonstream`), so `node_modules/JSONStream` and
`require('JSONStream')` are unchanged — the fork is a drop-in with the
same `JSONStream.parse` / `JSONStream.stringify` API, no code changes.

## Verification

Installed the full tree with `@unabandoned/jsonstream` (packed from the
fork) standing in for the alias and ran the suite: **17 pass, 0 fail, 1
skip** (the pre-existing `windows partitions` platform skip) on Node
22.22 and Node 24.19. `require('JSONStream')` resolved to the fork.

## Ordering note

⚠️ **CI here stays red until `@unabandoned/jsonstream` is published to
npm** (unabandoned/JSONStream#4 → release → publish). `npm install`
can't resolve the alias until then; this is the expected
publish-ordering dependency, verified above via a local install of the
exact package contents. Holding ready-for-review in the meantime.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_