Vouch Request - Jatin Awankar #4025

Why do you want to contribute?

I'd like to fix issue #2279 - the /runs docs don't explain the FROZEN run status.
I dug into this, including a maintainer comment on the issue saying FROZEN "shouldn't ever get this status through to your code" - and reconciled why the reporter still saw it:

• FROZEN is the status name returned by apiStatusFromRunStatusV1 (ApiRetrieveRunPresenter.server.ts), which is used whenever a request doesn't explicitly send the current API version header (getApiVersion() falls back to NON_SPECIFIC_API_VERSION in that case).
• Only requests that explicitly send the current API version header get the newer mapping, where the same internal statuses (PAUSED / WAITING_TO_RESUME) are returned as WAITING instead.
• So FROZEN isn't unreachable - it's the default/legacy-version name for what's now called WAITING. It just doesn't show up if you're already on the current API version, which is presumably what the maintainer meant.

Planned fix: add a short clarifying note to docs/runs.mdx explaining FROZEN as the legacy/unversioned-API equivalent of WAITING, rather than listing it as a separate first-class state.

I've posted this finding on the issue and am waiting to confirm the framing with the maintainer before opening a PR.
I'd like to start with this small, well-scoped docs fix and take on larger things as I get more familiar with the codebase.

Prior contributions or relevant experience

Full-stack developer - TypeScript, Next.js, Node.js, PostgreSQL, Redis, Prisma, BullMQ.

• OpenStatus (github.com/openstatusHQ/openstatus): 2 merged PRs (loading-state/skeleton work on dashboard), 1 backend fix currently in review on a PUT /v1/incidents/{id} attribution bug.
• Infisical (github.com/Infisical/infisical): docs-accuracy PR pending maintainer approval (fixed a stale GitHub App Connection setup path in the docs).
• GitHub: github.com/jatin-awankar - portfolio: jatinawankar.dev (Open Source section lists contributions as they land).

I work carefully: confirm scope on the issue before coding, keep PRs to a single clean commit, and trace root causes through the actual code rather than guessing from an issue title - as shown above with the FROZEN/PAUSED/WAITING_TO_RESUME trace.