Skip to content

Soft-deprecate discover consensus and enhanced - #46

Merged
yudelevi merged 3 commits into
developmentfrom
feat/discover-deprecate-consensus-enhanced
Oct 19, 2026
Merged

yudelevi merged 3 commits into
developmentfrom
feat/discover-deprecate-consensus-enhanced

Conversation

@yudelevi

@yudelevi yudelevi commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

The platform now applies consensus itself (single-domain lookalike searches without ICP text) and no longer runs AI result enhancement (platform !1024 / !1025, live on dev). Both discover request fields are accepted and ignored.

  • _generated/requests.py is regenerated from the dev spec. DiscoverParams drops consensus and enhanced, and variance describes where a list stops.
  • Passing either field still works: it goes out as an extra field and raises a DeprecationWarning. The warning is scoped to DiscoverParams through a new per-model table next to DEPRECATED_REQUEST_FIELDS, so contacts consensus is untouched.
  • CLI: --consensus and --enhanced on discover say deprecated/no-op, and --variance (discover, bulk) describes the stop.
  • Unrelated contract fix: dev's ProspectingRunResponse gained question (ProspectingOpenQuestion, what a needs_input run waits on). Without it the dev contract check fails for every PR, so ProspectingRun.question is declared here, with a test.

Checks against the dev spec: gen_requests.py --check is up to date and check_contract.py matches. 936 tests pass.

Changelog entries are left for release prep. The docs follow-up (discolike-api-docs, SDK reference rows) merges after this, since docs CI validates against this repo's development branch.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge, with the previous CLI help issue fixed.

Summary

Soft-deprecates discover's consensus and enhanced fields while keeping supplied values in outgoing requests.

  • Discover requests warn when callers use consensus or enhanced.
  • Variance tells callers where a result list stops.
  • Prospecting runs can show the question they are waiting on.

The changes since the previous review only restore the missing CLI choices. No new actionable issues were found.

Reviews (2) · Last reviewed commit: "fix(cli): list every variance level in t..." · Reviewed by Greptile

The platform now decides consensus itself and no longer runs AI result
enhancement, so both discover request fields are ignored. The
regenerated DiscoverParams drops them; passing either still sends it
and raises a DeprecationWarning, scoped to discover so contacts
consensus is untouched. CLI help for --consensus, --enhanced and
--variance says what the server does now.
The dev spec's ProspectingRunResponse gained question, the
ProspectingOpenQuestion a needs_input run waits on; without it the
contract check against dev fails for every PR.
Comment thread packages/discolike-cli/src/discolike_cli/discover.py Outdated
@yudelevi
yudelevi merged commit 09fb6c9 into development Oct 19, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant