[superlog-bot]

Summary

Sync the TypeScript SDK with the API changes published on 2026-10-26:

• Add Company.revenue_range to response schemas.
• Add people.job_description to people search filters.
• Add company.mx.provider to job search and TAM-by-jobs company filters.
• Add regression coverage for the response field and request serialization.

API change: 2026-10-26 public API changelog — “Companies now return their revenue band in revenue_range”, “Filter people by job description with people.job_description”, and “Filter jobs by company mail provider with company.mx”.

Verification

• pnpm test -- --run: 159 tests passed.
• pnpm typecheck: passed.

Confidence Score: 4/5

The PR appears safe to merge, with one non-blocking improvement to the response test.

Findings

1.  Test misses typed field removal ▶

Fix with agent prompt

### Issue 1
test/models.test.ts:155
This assertion still passes if `revenue_range` is removed from `Company`. `blitzObject` preserves undeclared keys, so the fixture value survives without the schema entry. Add `expect(Object.keys(Company.shape)).toContain("revenue_range")` alongside the value check to catch that regression.

```suggestion
    expect(resp.company?.revenue_range).toBe("$10M-$50M");
    expect(Object.keys(Company.shape)).toContain("revenue_range");
```

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Adds the announced API fields to the TypeScript SDK.

• Company responses expose a revenue band to TypeScript callers.
• People and job searches accept two new filters.

_{Reviews (1) · Last reviewed commit: "Sync SDK with 2026-10-26 API fields" · Reviewed by Greptile}

[greptile-apps]

Test misses typed field removal

This assertion still passes if revenue_range is removed from Company. blitzObject preserves undeclared keys, so the fixture value survives without the schema entry. Add expect(Object.keys(Company.shape)).toContain("revenue_range") alongside the value check to catch that regression.

Suggested change

	expect(resp.company?.revenue_range).toBe("$10M-$50M");
	expect(resp.company?.revenue_range).toBe("$10M-$50M");
	expect(Object.keys(Company.shape)).toContain("revenue_range");

Prompt To Fix With AI

This is a comment left during a code review.
Path: test/models.test.ts
Line: 155

Comment:
**Test misses typed field removal**

This assertion still passes if `revenue_range` is removed from `Company`. `blitzObject` preserves undeclared keys, so the fixture value survives without the schema entry. Add `expect(Object.keys(Company.shape)).toContain("revenue_range")` alongside the value check to catch that regression.

```suggestion
    expect(resp.company?.revenue_range).toBe("$10M-$50M");
    expect(Object.keys(Company.shape)).toContain("revenue_range");
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!