Prospecting defaults to 3 contacts per company

[yudelevi]

The API now uses 3 contacts per company when a brief doesn't state a count (was 1). The SDK's ProspectingBrief default, CLI help, READMEs and CHANGELOG still said 1.

requests.py is regenerated from the spec; the field stays optional and 1-10, and is still omitted from the wire when unset, so older and newer SDKs behave the same against any server.

Pilot checkpoint reply copy also changed server-side. No change needed here: the CLI shows and sends the suggested_replies the server returns, and hardcodes none.

Confidence Score: 4/5

The PR appears safe to merge; the remaining issue is a non-blocking test-coverage gap for an explicit value of 3.

Findings

1.  Explicit default lacks coverage ▶

Fix with agent prompt

### Issue 1
packages/discolike/tests/test_prospecting.py:420
The updated test checks that an omitted count stays off the wire, but its explicit case uses `2`. It does not protect the new default of `3` when a caller supplies it explicitly. That value must be sent so it can override a different count inferred from the brief; otherwise a future serialization change could break that behavior unnoticed.

```suggestion
    assert (implicit.target_companies, implicit.contacts_per_company) == (1000, 3)
    assert ProspectingBrief(brief=implicit.brief, contacts_per_company=3).to_wire() == {
        "brief": implicit.brief,
        "contacts_per_company": 3,
    }
```

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

The PR aligns the SDK model default, CLI help, documentation, and an SDK test with the API’s stated fallback of three contacts per company. An unset count remains omitted from the request body, leaving brief inference to the server.

_{Reviews (1) · Last reviewed commit: "Prospecting defaults to 3 contacts per c..."}

[greptile-apps]

Explicit default lacks coverage The updated test checks that an omitted count stays off the wire, but its explicit case uses 2. It does not protect the new default of 3 when a caller supplies it explicitly. That value must be sent so it can override a different count inferred from the brief; otherwise a future serialization change could break that behavior unnoticed.

Suggested change

	assert (implicit.target_companies, implicit.contacts_per_company) == (1000, 3)
	assert (implicit.target_companies, implicit.contacts_per_company) == (1000, 3)
	assert ProspectingBrief(brief=implicit.brief, contacts_per_company=3).to_wire() == {
	"brief": implicit.brief,
	"contacts_per_company": 3,
	}

Knowledge Base Used: Quality and delivery automation

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/discolike/tests/test_prospecting.py
Line: 420

Comment:
**Explicit default lacks coverage** The updated test checks that an omitted count stays off the wire, but its explicit case uses `2`. It does not protect the new default of `3` when a caller supplies it explicitly. That value must be sent so it can override a different count inferred from the brief; otherwise a future serialization change could break that behavior unnoticed.

```suggestion
    assert (implicit.target_companies, implicit.contacts_per_company) == (1000, 3)
    assert ProspectingBrief(brief=implicit.brief, contacts_per_company=3).to_wire() == {
        "brief": implicit.brief,
        "contacts_per_company": 3,
    }
```

**Knowledge Base Used:** [Quality and delivery automation](https://app.greptile.com/discolike/-/custom-context/knowledge-base/discolike/discolike-python/-/docs/quality-and-delivery.md)

---

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!