feat(api): resolve analysis-run identity from LineageWeave and Naruon - #402
Draft
seonghobae wants to merge 1 commit into
Conversation
LineageWeave can GET /v1/analysis-runs/by-idempotency/{key} without a
Naruon-labelled exchange. NaruonLiveService serves the same metric-free
inspect for Naruon only and returns a real run_id on accepted creates.
tepp-loopback proves create-then-GET over TCP (ADR 0047).
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 31, 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
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.
Why
GAP-003A / issue #166 still has no LineageWeave idempotency-lookup exchange builder, no Naruon compatibility-listener inspect, and no
tepp-loopbackTCP proof of a durablerun_idfrom a 202 receipt key. ADR 0037 / #380 addedGET /v1/analysis-runs/by-idempotency/{key}onAnalysisRunLiveServiceand the Naruon inspect builder only. A published LineageWeave consumer would have to mint a Naruon-labelled inspect.NaruonLiveServicestill refused every GET path.Live slices that this PR does not duplicate:
analysis_enginescientific-acceptance libraryed21a10579d69faf4182ef6c07004fd622983a1e)What
Unique GAP-003A idempotency-lookup consumer-parity slice stacked on #380 over protected main
1bc02f580cf48e1d39da239f0e818453437c31c3:lineageweave_analysis_run_idempotency_lookup_exchangereuses the Naruon inspect builder and replaces onlytepp-consumerNaruonLiveServiceserves metric-free lookup GET for Naruon only; LineageWeave remains refused thererun_id(200) because that listener already keys idempotency replay; unknown, consumer mismatch, nonempty body, and metric keys fail closedtepp-loopbackcreate-then-GET over loopback TCP proves a durablerun_idonAnalysisRunLiveServiceNot an ADR 0014 scientific claim. Not GET status. Not lifecycle POST. Not collection GET. Not retry POST. Not retry-lineage. Not retry-parent. Not persistence. Does not open
NaruonLiveServiceto LineageWeave.Verification
cargo clippy -p tepp_api --all-targets -- -D warningscargo test -p tepp_api --lib --testscargo doc -p tepp_api --no-depspython3 scripts/validate_documentation.pypython3 scripts/check_docstrings.pycrates/tepp_api/tests/lineageweave_http_contract.rscrates/tepp_api/tests/naruon_live_http_contract.rscrates/tepp_api/tests/loopback_binary_contract.rsdocs/research/analysis-run-idempotency-lookup-consumer-parity.mdExact-head Checks on
7034670efb5104479183fab92d913becec1db393are required before merge. Two independent current-head APPROVEs are required. Author cannot self-approve. Merge #380 before this stacked PR, or retarget onto protected main after #380 lands. No force-push.