feat(api): inspect stored analysis-run requests from LineageWeave and Naruon

[seonghobae]

Why

GAP-003A / issue #166 still has no LineageWeave stored-request exchange builder, no Naruon compatibility-listener inspect, and no tepp-loopback TCP proof. ADR 0034 / #377 added GET /v1/analysis-runs/{run_id}/request on AnalysisRunLiveService and the Naruon inspect builder only. A published LineageWeave consumer would have to mint a Naruon-labelled inspect. NaruonLiveService still refused every GET path.

Live slices that this PR does not duplicate:

• feat(analysis): bind validation runs to scientific acceptance evidence #356 analysis_engine scientific-acceptance library
• feat(api): carry scientific acceptance only on terminal results #358 tepp_api terminal-wire DTO
• feat(api): serve scientific acceptance only on loopback status GET #359 GET loopback status
• feat(api): record scientific acceptance via loopback lifecycle POST #360 POST running/terminal lifecycle
• feat(api): cancel accepted and running analysis runs on loopback #361 cancel HTTP
• feat(api): drive scientific acceptance via loopback CLI #362 loopback CLI
• feat(analysis): bind TDT/CHRONOS composition to an analysis-run profile #364 GAP-007 TDT/CHRONOS analysis-run profile
• feat(api): enumerate analysis runs via loopback collection GET #368 collection GET
• feat(api): retry failed and cancelled analysis runs on loopback #369 retry HTTP
• feat(analysis): execute scientific acceptance on loopback lifecycle #370 loopback engine
• feat(api): enumerate analysis runs via loopback collection CLI #371 collection CLI
• feat(analysis): bind CWC within/between slopes to an analysis-run profile #372 CWC analysis-run profile
• feat(api): cancel analysis runs from LineageWeave and Naruon compatibility #373 cancel consumer-parity
• feat(analysis): bind Rubin loading uncertainty to an analysis-run profile #374 Rubin loading uncertainty
• feat(analysis): serve scientific acceptance execute from tepp-loopback #375 tepp-loopback binary execute
• feat(analysis): bind longitudinal ESEM/DSEM composition to an analysis-run profile #376 ESEM/DSEM composition
• feat(api): inspect stored analysis-run create fields on loopback #377 stored-request GET (this PR stacks on that head f80bd97c05641601d5158c12eef2aa48e7944892)
• feat(api): cancel analysis runs via loopback CLI #378 cancel CLI
• feat(api): inspect analysis-run retry children on loopback #379 retry-lineage GET
• feat(api): resolve analysis-run identity by idempotency key on loopback #380 idempotency lookup GET
• feat(analysis): mint execute exchanges for naruon and LineageWeave #381 execute consumer exchange
• feat(analysis): send execute exchanges over tepp-loopback TCP #382 execute-exchange loopback TCP
• feat(api): poll analysis-run status from LineageWeave on loopback #383 status consumer-parity
• feat(api): inspect analysis-run retry parent on loopback #384 retry-parent GET
• feat(api): create analysis runs via loopback CLI #385 create CLI
• feat(analysis): bind two-group OLS invariance to an analysis-run profile #386 two-group OLS invariance (ADR 0039)
• feat(persistence): persist idempotent analysis runs #287 GAP-003B persistence/Compose
• feat(network): replace union-find stand-in with Leiden consensus #351 Leiden
• Driver p.16 std-family slices

What

Unique GAP-003A stored-request consumer-parity slice stacked on #377 over protected main 1bc02f580cf48e1d39da239f0e818453437c31c3:

• lineageweave_analysis_run_stored_request_exchange reuses the Naruon inspect builder and replaces only tepp-consumer
• NaruonLiveService serves metric-free stored-request GET for Naruon only; LineageWeave remains refused there
• accepted inspect returns snapshot, cutoff, model contract, and output profile (200); unknown, consumer mismatch, nonempty body, and metric keys fail closed
• tepp-loopback create-then-inspect over loopback TCP
• ADR 0040 on the stored-request GET lineage (0039 is feat(analysis): bind two-group OLS invariance to an analysis-run profile #386 two-group OLS)

Not an ADR 0014 scientific claim. Not GET status. Not lifecycle POST. Not collection GET. Not retry. Not retry-lineage. Not persistence. Does not open NaruonLiveService to LineageWeave.

Verification

• cargo clippy -p tepp_api --all-targets -- -D warnings
• cargo test -p tepp_api --all-targets
• RUSTDOCFLAGS='-D warnings' cargo doc -p tepp_api --no-deps
• python3 scripts/validate_documentation.py
• python3 scripts/check_docstrings.py
• crates/tepp_api/tests/lineageweave_http_contract.rs
• crates/tepp_api/tests/naruon_live_http_contract.rs
• crates/tepp_api/tests/loopback_binary_contract.rs
• doctoring: docs/research/analysis-run-stored-request-consumer-parity.md

Exact-head Checks on e2ffc6d1cbb6c2f972efd69f236ac5cd918113e6 are required before merge. Two independent current-head APPROVEs are required. Author cannot self-approve. Merge #377 before this stacked PR, or retarget onto protected main after #377 lands. No force-push.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Exact-head COMMENT on e2ffc6d (draft). Unique occupied: analysis-run stored-request consumer-parity (ADR 0040) — LineageWeave exchange reuses origin/body/header validation then replaces only tepp-consumer with lineageweave. Accepted response stays an asynchronous transport acknowledgement, not a psychometric result. Do not leak PII through LineageWeave. Do not add GET to NaruonLiveService. Do not un-quarantine stored-request-by-client-key. Do not un-draft. Zero reviews on this SHA before this COMMENT. Never self-approve. Do not weaken fail-closed. No Buyer language.