ci: run static checks independently of package builds

[mldangelo-oai]

Summary

Every SDK test and installed-package job waits for the shared package job. Typechecking and formatting do not need to delay that archive, so run them independently while keeping them required.

Changes

• Move typechecking and formatting into one independent Ubuntu job.
• Keep compilation, plugin source checks, packing, and archive validation in the package job.
• Make the existing Unix and Windows required checks fail when the new job fails, is canceled, or is unexpectedly skipped.
• Preserve reduced Markdown CI and the existing required check names.
• Extend the gate behavior tests and remove redundant assertions of entire condition strings.

Testing

• Full SDK suite with seed 12345: 2,072 passed, 39 skipped.
• Full randomized SDK suite with seed 4294301641: 2,072 passed, 39 skipped.
• Focused workflow and release tests: 296 passed.
• Typechecking, formatting, and bundled-plugin build passed.

Risk and rollout

CI-only change with one additional setup/install job. Package consumers still wait for a compiled and inspected archive, and existing required checks enforce the independent static checks. Hosted timing improvements have not yet been measured for this 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.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-30T01:41:13.498947Z	583d6fd	Manual request
🔒 Security Review	✅ Completed 2026-08-30T01:38:49.336550Z	583d6fd	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[mldangelo-oai]

@codex review

Please review the current head, 583d6fd.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: 583d6fd882

ℹ️ 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".