fix(sdk): land v2 predict + financial + typed on main (stranded by stacked-merge order) - #4
Merged
Merged
Conversation
…observations, query) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…file, predict, calibration) + end-to-end demo Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ention, provenance Adds PredictionTarget (event_occurrence/numeric/event_time/anomaly) on PredictRequest, TargetPrediction + first-class abstained/abstentionReason on PredictResult, and an ergonomic tf.lattice.predictTarget() helper. Mirrors the engine v2 contract the product API already serves. Includes a predict-anything example and README section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…financial/typed types Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
feat(sdk): v2 general-prediction surface + financial & typed-attributes resources
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this exists
PRs #2 and #3 were a stack (#3 based on
feat/health-resource). They merged ~10s apart, but #2 (health → main) merged first, somainwas taken fromfeat/health-resourcebefore #3 added the catch-up commits to it. Result: the catch-up work (typed-attributes, financial, the v2 general-prediction surface) merged intofeat/health-resourcebut never reachedmain.predictTargetcount onorigin/mainis currently 0 — i.e. the v2 SDK surface is not actually shipped despite both prior PRs showing "merged".What this does
Brings
feat/health-resource(which now contains the catch-up via the #3 merge) up tomain. Diff = the four already-reviewed commits:feat(typed)— typed-attributes resourcefeat(financial)— financial resource + demofeat(predict)— v2 general prediction:PredictionTarget,TargetPrediction, first-classabstained,tf.lattice.predictTarget()chore(client)— wiring + exportsNo new code vs. #3 — this is purely the merge-to-main that the stacked order skipped.
After merge
origin/mainwill containpredictTargetand the v2 types indist. Verified cleantscat this tree previously.🤖 Generated with Claude Code