test: remove duplicate launcher and runtime coverage

[mldangelo-oai]

Summary

Remove duplicate SDK integration tests without dropping their behavioral assertions.

Changes

• Keep the Windows-aware installed-launcher integration test and move the duplicate compiler-stderr assertion into it.
• Delete the repeated npm-style launcher setup and its now-unused imports.
• Keep one copy of the identical trusted-output-owner permission test.

Testing

• bun test tests-ts/cli.test.ts tests-ts/cli-launcher.test.ts tests-ts/runtime.test.ts --timeout 30000 — passed.
• pnpm run types — passed.
• prettier --check tests-ts/cli.test.ts tests-ts/cli-launcher.test.ts tests-ts/runtime.test.ts — passed.
• git diff --check — passed.

Risk and rollout

Production code is unchanged. The retained launcher test includes Windows junction handling, installed-bin execution, startup failure handling, and the migrated compiler-stderr assertion. The remaining owner test preserves every user-ID and permission case.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[mldangelo-oai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: a5c5483b65

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Security review completed. No security issues were found in this pull request.

Reviewed commit: a5c5483b65

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

[zcrab-oai]

Looks good. Removes duplicate integration tests while retaining launcher, Windows junction, and trusted-owner coverage.