chore(js): recover 0.15.0 release after concurrent publish

[konard]

Summary

• apply the generated JavaScript 0.15.0 version, changelog, and lockfile metadata on top of the Rust 0.13.1 release commit
• consume the two TUI capture changesets already merged in feat: capture PTY terminal sessions #176 and fix(js): preserve states before leading repaint #177
• allow the existing release workflow to self-heal the unpublished npm package without another source change

Why this follow-up is needed

The JavaScript and Rust release workflows started from the same main commit after #177. Rust published 0.13.1 and advanced main first. JavaScript generated its valid 0.15.0 release commit afterward, but its push was rejected as non-fast-forward. The retry logic could not rebase because dependency installation had left unstaged changes in the runner.

This PR recreates only that generated release metadata on the current main tip. Its changeset-release/ branch name follows the workflow's generated-release convention and bypasses the normal requirement to add a new changeset while consuming existing ones.

Verification

• bun run format:check
• npm pack --dry-run (package version 0.15.0; PTY capture files included)
• full cross-platform JavaScript and Rust checks passed on fix(js): preserve states before leading repaint #177 before the release workflows started

Closes the JavaScript release portion of #175.