[Pipeline B] Wire fill flow to accept input_id and use stored transcript - #649
Merged
marcvergees merged 1 commit intoAug 5, 2026
Conversation
marcvergees
approved these changes
Aug 5, 2026
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
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.
Closes #638.
Changes the fill endpoints to accept input_id and use the stored Input.transcript instead
of a raw input_text in the request — the core of Pipeline B's "store the transcript once,
reuse it" model.
get_input, raises 404 INPUT_NOT_FOUND if missing, 409 INPUT_NOT_READY (with the actual
status in the detail) if status != ready, else returns the transcript. Both routes use it,
so the rule lives in one place.
front, before the Celery dispatch, so 404/409 return synchronously and no job is queued
on a bad input_id.
this is the input_text → input_id switch deferred from the contract-reshape PR, now done
with the code together.
separate follow-up issue).
Note: input_id is a UUID (matching the Input model / input-record.yaml), not int as the
issue text said - corrected here.
Please Review @marcvergees @vharkins1 @chetanr25 .