test(api): share prepared runtime fixtures

[mldangelo-oai]

Summary

Share the identical prepared-runtime fixture used by three API test suites.

Changes

• Move the existing fixture into the API test support module.
• Import the shared fixture from the orchestration, post-scan, and API-surface tests.
• Remove duplicate plugin-root imports and unchanged local fixture implementations.

Testing

• bun test tests-ts/api.test.ts tests-ts/api-post-scan.test.ts tests-ts/api-surface.test.ts tests-ts/api-events.test.ts --timeout 30000 (158 passed).
• pnpm --pm-on-fail=ignore run types.
• prettier --check for all four changed test files.
• git diff --check.

Risk and rollout

Test-only cleanup. The shared helper returns the same values as each removed local helper, and no production or packaged files change.

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

[mldangelo-oai]

@codex security review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 93c3e443e3

ℹ️ 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: 93c3e443e3

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. Shared prepared-runtime fixtures preserve fresh per-test state and existing authentication, provider, and cancellation coverage.