Skip to content

Carry include_confidence through the SDK and CLI - #30

Merged
yudelevi merged 8 commits into
developmentfrom
feat/discogen-typed-columns
Sep 22, 2026
Merged

yudelevi merged 8 commits into
developmentfrom
feat/discogen-typed-columns

Conversation

@yudelevi

@yudelevi yudelevi commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Adds include_confidence to discogen.process and discogen.process_personas, plus --include-confidence on the CLI. It applies to typed DiscoGen columns, which the platform answers with a TypeSafe judgment model rather than generated prose.

_generated/requests.py was regenerated with gen_requests.py --spec against the platform branch's own OpenAPI, not hand-edited. The regen also picks up an integration_id description that had drifted since native-icp shipped.

Blocked until the platform change is on api-dev. contract.yml checks a PR targeting development against DEV_SPEC_URL, so check_contract.py and gen_requests.py --check will both disagree until then. Platform side is discolike/discolike-platform!885.

RetriggerConfidence Score: 5/5

The PR appears safe to merge once its stated external platform dependency is available; no actionable code defect remains in the reviewed changes.

Summary

The PR carries typed-column confidence controls through the generated SDK request models and both DiscoGen CLI commands, adds request-serialization coverage for all include_confidence states, and updates contract checking for stacked non-main branches.

  • Adds typed_columns and include_confidence request fields for domain and persona DiscoGen processing.
  • Adds matching positive, negative, and omitted-state CLI coverage for include_confidence.
  • Documents the new SDK and CLI behavior in the changelog.
  • Uses the development API specification for internal PRs targeting any non-main branch while retaining the production fallback for forks.

Reviews (2) · Last reviewed commit: "Trigger checks for the merged typed-colu..."

Regenerated from the branch's own OpenAPI spec via gen_requests.py
--spec rather than edited by hand, since that file says not to. The
regen also picks up an integration_id description that had drifted since
native-icp shipped.

Ordering: contract.yml checks a PR targeting development against
DEV_SPEC_URL, so this needs the platform change on api-dev before the
SDK PR opens, not a prod deploy. Until then check_contract.py and
gen_requests.py --check both disagree, because the spec they read does
not carry the field yet.
Comment thread packages/discolike-cli/src/discolike_cli/discogen.py
DiscoGen's typed-column detector (which columns run through TypeSafe
judgment instead of generated prose) is picked server-side from the
query text; the client only opts in with a bool, same shape as
include_confidence which already made the trip last commit. Hand-added
to _generated/requests.py rather than regenerated, since api-dev does
not serve this field yet (same ordering constraint as include_confidence).
yudelevi and others added 6 commits September 22, 2026 10:22
The flag has distinct true, false, and unset wire behavior but no
dedicated test exercised any of it for run or run-personas.
A PR stacked on a feature branch is as far ahead of prod as the branch it
targets, but base_ref only matched "development" literally, so the stack
fell through to the prod spec and reported every unreleased field as a
missing one. Fork PRs still get the prod spec, since they never receive
DEV_SPEC_URL.
# Conflicts:
#	CHANGELOG.md
#	packages/discolike-cli/tests/test_discogen_cli.py
Carry the typed_columns opt-in flag through the SDK and CLI
@yudelevi yudelevi closed this Sep 22, 2026
@yudelevi yudelevi reopened this Sep 22, 2026
@yudelevi
yudelevi merged commit 3bd6db2 into development Sep 22, 2026
7 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