feat(api): consolidate interpretation-run stored-request and run-id lookup GET/CLI - #468
Closed
seonghobae wants to merge 4 commits into
Conversation
…nt GET
Publish GET /v1/interpretation-runs/{idempotency_key}/request so operators
fetch the accepted create request without POST replay. scientific_authority
stays false. Naruon and LineageWeave are refused. NaruonLiveService stays
POST-only. Cancel extra-segment stays refused. ADR 0085.
…d CLI Publish tepp-interpretation-run-request get so operators retrieve the stored create request on spawned tepp-orchestrator-loopback TCP without POST replay. scientific_authority stays false. Empty stdin is admitted. Naruon and LineageWeave are refused. NaruonLiveService stays POST-only. Cancel extra- segment stays refused. ADR 0086.
GET /v1/interpretation-runs/by-run-id/{interpretation_run_id} returns the
metric-free hypothetical identity on OrchestratorLiveService. Dual identity
of GET-by-id (idempotency_key). Zero and ambiguous matches fail closed.
claim_status remains hypothetical; scientific_authority remains false.
NaruonLiveService stays POST-only. Does not re-open cancel lineages.
Publish tepp-interpretation-run-lookup so operators can mint
GET /v1/interpretation-runs/by-run-id/{interpretation_run_id} onto spawned
tepp-orchestrator-loopback TCP without scanning collection pages. Metric-free
identity only. Empty stdin admitted. Naruon and LineageWeave refused.
seonghobae
marked this pull request as draft
September 1, 2026 18:09
seonghobae
changed the base branch from
feat/interpretation-run-lookup-get-gap-003a
to
feat/interpretation-run-retrieval-get-gap-003a
September 1, 2026 18:12
This was referenced Sep 1, 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.
Superseded by fold into #469
Strict ancestry was verified before closure: #468 exact head
287584d4d99d1cf44f26dbeb4d8f010fc167837ais the merge base of #469 exact head6a68f98971986f3ea9562fd7a73c5974e5a4af6e, which was exactly one commit ahead and zero behind. #469 was retargeted to this PR's surviving base, so the full #453 → #454 → #467 stored-request/run-id lookup lineage plus this lookup CLI remains in one Analysis Run landing vehicle together with the server-id stored-request GET. This PR is closed only to reduce duplicate WIP; discussion and review history remain immutable evidence.The failed attempt to convert #469 back to Draft was a connector GraphQL schema error (
Repository.fullDatabaseIdunavailable), not a repository-state decision. #469 therefore remains non-Draft metadata-wise but must still be treated as review-not-ready until its retargeted exact head reacquires checks and qualifying review.