Trace first-party OAuth usage

[RhysSullivan]

What changed

• add executor.oauth.client_first_party to OAuth start/request traces
• add the same boolean to executor.oauth.complete
• verify first-party flows emit true at both points

Why

OAuth completion traces already expose the client slug, but filtering for host-operated clients requires parsing the first-party: prefix. The boolean provides a stable, low-cardinality dimension for queries, dashboards, and alerts.

Validation

• bun run --cwd packages/core/sdk test -- oauth-first-party.test.ts
• bunx oxlint -c .oxlintrc.jsonc packages/core/sdk/src/oauth-service.ts packages/core/sdk/src/oauth-first-party.test.ts --deny-warnings
• bun run typecheck

[github-actions]

Cloudflare preview

Torn down — the PR is closed.

[pkg-pr-new]

Open in StackBlitz

@executor-js/cli

npm i https://pkg.pr.new/@executor-js/cli@1633

@executor-js/config

npm i https://pkg.pr.new/@executor-js/config@1633

@executor-js/execution

npm i https://pkg.pr.new/@executor-js/execution@1633

@executor-js/sdk

npm i https://pkg.pr.new/@executor-js/sdk@1633

@executor-js/codemode-core

npm i https://pkg.pr.new/@executor-js/codemode-core@1633

@executor-js/runtime-quickjs

npm i https://pkg.pr.new/@executor-js/runtime-quickjs@1633

executor

npm i https://pkg.pr.new/executor@1633

@executor-js/plugin-file-secrets

npm i https://pkg.pr.new/@executor-js/plugin-file-secrets@1633

@executor-js/plugin-graphql

npm i https://pkg.pr.new/@executor-js/plugin-graphql@1633

@executor-js/plugin-keychain

npm i https://pkg.pr.new/@executor-js/plugin-keychain@1633

@executor-js/plugin-mcp

npm i https://pkg.pr.new/@executor-js/plugin-mcp@1633

@executor-js/plugin-onepassword

npm i https://pkg.pr.new/@executor-js/plugin-onepassword@1633

@executor-js/plugin-openapi

npm i https://pkg.pr.new/@executor-js/plugin-openapi@1633

commit: 5bc1324