feat(api): POST retry from published tepp-retry CLI

[seonghobae]

Why

GAP-003A / issue #166 still has no published CLI that POSTs /retry from the typed naruon/LineageWeave retry exchange onto spawned tepp-loopback TCP. ADR 0032 / #369 owns retry HTTP. ADR 0033 / #393 owns consumer-parity exchanges. Operators still had to embed the library or invent HTTP. analysis_engine cannot own this CLI: retry glue lives in tepp_api, and tepp_api cannot depend on analysis_engine. tepp-analysis-runs lives on the diverged #385 stack that lacks retry HTTP.

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(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(api): cancel analysis runs from LineageWeave and Naruon compatibility #373 cancel consumer-parity
• feat(analysis): serve scientific acceptance execute from tepp-loopback #375 execute loopback binary
• feat(api): inspect stored analysis-run create fields on loopback #377 stored-request GET
• feat(api): cancel analysis runs via loopback CLI #378 cancel CLI
• feat(api): inspect analysis-run retry children on loopback #379 retry children
• feat(api): resolve analysis-run identity by idempotency key on loopback #380 idempotency lookup
• feat(analysis): mint execute exchanges for naruon and LineageWeave #381 execute consumer exchange
• feat(analysis): send execute exchanges over tepp-loopback TCP #382 execute 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 profile
• feat(api): inspect stored analysis-run requests from LineageWeave and Naruon #387 stored-request consumer-parity
• feat(api): record analysis-run lifecycle from LineageWeave and Naruon compatibility #388 lifecycle consumer-parity
• feat(analysis): bind irregular event-time log-rate to an analysis-run profile #389 irregular event-time
• feat(analysis): POST execute from published tepp-execute CLI #390 execute CLI
• feat(api): enumerate analysis runs from LineageWeave and Naruon #391 collection consumer-parity
• feat(api): inspect analysis-run status via loopback CLI #392 status CLI
• feat(api): retry analysis runs from LineageWeave and Naruon compatibility #393 retry consumer-parity (this PR stacks on that head 520f1a4e9fc73c274201d89a9857b8d0b5d8353d)
• feat(persistence): persist idempotent analysis runs #287 GAP-003B persistence/Compose
• feat(network): replace union-find stand-in with Leiden consensus #351 Leiden
• feat(longitudinal): consolidate lagged correlation and discreteDRIFTstd #310 discreteDRIFTstd

What

Unique GAP-003A retry CLI slice stacked on #393 over protected main 1bc02f580cf48e1d39da239f0e818453437c31c3:

• published tepp-retry retry mints naruon_analysis_run_retry_exchange or lineageweave_analysis_run_retry_exchange and renders through loopback_http1_from_retry_exchange
• --origin stays the published HTTPS origin; only --host is the loopback bind address printed by tepp-loopback
• empty stdin is admitted; typed retry JSON must match --run-id and the new --idempotency-key
• success stdout is a metric-free child 202 Accepted with a new run_id (not the parent) and matching new idempotency key
• public bind hosts, localhost, unpublished consumers, credential-shaped flags, metric keys, http:// origins, and retry of accepted/running/succeeded/unknown parents fail closed
• ADR 0043

Not an ADR 0014 scientific claim. Not retry HTTP. Not retry consumer-parity. Not execute CLI. Not cancel/create/status/collection/lifecycle CLI. Persistence remains GAP-003B.

Verification

• cargo clippy -p tepp_api --all-targets -- -D warnings
• cargo test -p tepp_api --test analysis_run_retry_cli_contract
• cargo test -p tepp_api
• cargo doc -p tepp_api --no-deps
• python3 scripts/validate_documentation.py
• python3 scripts/check_docstrings.py

Stacking

Base is feat/analysis-run-retry-consumer-parity-gap-003a (#393). Merge #393 first or retarget onto main after #393 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 deef33b (draft). Unique occupied: tepp-retry retry minting POST /v1/analysis-runs/{run_id}/retry (ADR 0043). Stdout is metric-free child 202 Accepted. tepp.scientific_acceptance.v1 never appears. Supports naruon and LineageWeave typed exchanges. Do not un-draft. Zero reviews on this SHA before this COMMENT. Never self-approve. Persistence remains GAP-003B. Do not weaken fail-closed. No Buyer language. No PII in LineageWeave.