Update yarn lockfile to pass asset generation

[RaghavsBrowserStack]

The lockfile in master is currently out of sync due to intellistory changes. This pr fixes that

[RaghavsBrowserStack]

Claude Code PR Review

PR: #2379 • Head: c8f17c4 • Reviewers: stack:code-reviewer

Summary

Lockfile-only change (yarn.lock, +35/-8) that repairs a yarn.lock left internally inconsistent by the hand-edited IntelliStory merge — adding the missing @types/node@* and get-stream@^5.1.0 resolutions (plus their cascading sub-deps pump, end-of-stream@^1.1.0, undici-types@~8.3.0, once@^1.3.1) and pruning the orphaned @types/yauzl@^2.9.1 entry.

Review Table

Priority	Category	Check	Status	Notes
High	Security	No hardcoded secrets or credentials	Pass	No code changed; lockfile contains only registry URLs and integrity hashes.
High	Security	Authentication/authorization checks present	N/A	No auth surface touched.
High	Security	Input validation and sanitization	N/A	No input-handling code touched.
High	Security	No IDOR — resource ownership validated	N/A	No resource access code touched.
High	Security	No SQL injection (parameterized queries)	N/A	No database code touched.
High	Correctness	Logic is correct, handles edge cases	Pass	Verified every added entry closes a real gap: @types/cacheable-request, @types/keyv, @types/responselike all declare "@types/node" "*" with no resolution in master; cacheable-request@^7.0.2 declares get-stream "^5.1.0" with no resolution in master. once@^1.3.1 correctly merged into the existing 1.4.0 group.
High	Correctness	Error handling is explicit, no swallowed exceptions	N/A	No executable code.
High	Correctness	No race conditions or concurrency issues	N/A	No concurrent code.
Medium	Testing	New code has corresponding tests	N/A	Lockfile regeneration; nothing to unit test.
Medium	Testing	Error paths and edge cases tested	N/A	See above.
Medium	Testing	Existing tests still pass (no regressions)	Pass	All 47 GitHub checks pass on c8f17c4 (Build, Lint, Regression, typecheck, and every per-package test job).
Medium	Performance	No N+1 queries or unbounded data fetching	N/A	No data-access code.
Medium	Performance	Long-running tasks use background jobs	N/A	Not applicable.
Medium	Quality	Follows existing codebase patterns	Pass	Standard yarn v1 lockfile format; entries carry both resolved and integrity.
Medium	Quality	Changes are focused (single concern)	Pass	Exactly one file, one concern — lockfile consistency. Earlier stray-fixture commits on the branch were already reverted before this head.
Low	Quality	Meaningful names, no dead code	Pass	Orphaned @types/yauzl@^2.9.1 removed — confirmed nothing in root or packages/* package.json, nor any lockfile dependencies: block, references it.
Low	Quality	Comments explain why, not what	N/A	Generated file.
Low	Quality	No unnecessary dependencies added	Pass	No package.json changed; all added lockfile entries are transitive resolutions already required by existing declared ranges.

Findings

No Fail rows and no Critical/High/Medium findings. Two informational notes, neither introduced by this PR:

• File: yarn.lock (@types/node@* entry)

• Severity: Low

• Reviewer: stack:code-reviewer

• Issue: @types/node@* resolves to 26.1.2, a very new major, because the transitively-declared range is unpinned *. Multiple @types/node majors now coexist in the tree (14.14.22, 26.1.2, plus >= ranges). Ambient global type declarations across differing majors can in principle produce tsc errors.

• Suggestion: No action needed — the unpinned * range is pre-existing transitive behavior, and test:types passes in CI on this head. If type-stacking ever bites, add an explicit @types/node resolution to pin it.

• File: yarn.lock (new entries use registry.yarnpkg.com, surrounding entries use registry.npmjs.org)

• Severity: Low

• Reviewer: stack:code-reviewer

• Issue: Mixed registry hostnames in resolved URLs (120 yarnpkg vs 1120 npmjs at head).

• Suggestion: Cosmetic only. The mix already exists in master and reflects different yarn-version writers over the file's history; both hosts serve identical tarballs and integrity hashes are present. Not worth churning the file to normalize.

Verification performed beyond the diff: dependency-graph consistency check over the resulting lockfile (every declared name@range spec has a matching resolution entry), @types/yauzl orphan status confirmed by grep across all package.json files and lockfile dependency blocks, and yarn install --frozen-lockfile usage located in .github/workflows/version-bump.yml:41 — the job whose failure this PR fixes.

---

Verdict: PASS