feat(api): mint interpretation-run lookup stored-request GET from a dedicated CLI - #470
Merged
seonghobae merged 1 commit intoSep 1, 2026
Conversation
…edicated CLI Publish tepp-interpretation-run-lookup-request get so operators who hold a 202 receipt can recover the stored create onto spawned tepp-orchestrator-loopback TCP. Empty stdin admitted. Metric-free. Naruon and LineageWeave refused.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Comment on lines
+366
to
+367
| let stored = InterpretationRunRequest::from_json(&response.body)?; | ||
| stored.to_json() |
There was a problem hiding this comment.
🟡 Wrong run response accepted
Given any valid stored-request response, render_interpretation_run_lookup_stored_request_cli_stdout prints it without binding it to the requested run. A misrouted response returns another run's request as success.
Prompt for agents
The lookup stored-request response contains only InterpretationRunRequest, so render_interpretation_run_lookup_stored_request_cli_stdout cannot verify that a successful body belongs to invocation.interpretation_run_id. The neighboring lookup CLI validates the returned run ID, and the idempotency-key stored-request CLI validates the returned idempotency key. Extend the response contract or execution flow so this CLI receives a verifiable binding between the requested interpretation_run_id and the stored request, reject mismatches before printing, and add a contract test with a valid request from a different run.
Was this helpful? React with 👍 or 👎 to provide feedback.
seonghobae
merged commit Sep 1, 2026
5b46d78
into
feat/interpretation-run-lookup-stored-request-get-gap-003a
4 of 7 checks passed
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
1 participant
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.
Superseded by fold into #469
Closed as
superseded_by_fold, not discarded. #470 was based exactly on #469's prior head6a68f98971986f3ea9562fd7a73c5974e5a4af6e. The surviving #469 branch was fast-forwarded without force to this PR's exact head5b46d78aef81902ab12b8ad691fd83be68d616cc, so the publishedtepp-interpretation-run-lookup-request getCLI, stored-request lookup route, tests, RED/GREEN lineage, and this discussion remain preserved in the consolidated Analysis Run application/adapter vehicle.Canonical surviving vehicle: #469 (
feat(api): consolidate interpretation-run retrieval, lookup, and stored-request adapters).This route does not establish an independent bounded context or architecture authority; operation-specific ADR identity remains implementation lineage pending #437 normalization. Do not reopen unless the surviving exact head demonstrably loses unique behavior or evidence.