feat(api): query cutoff-safe temporal context via loopback CLI

[seonghobae]

Why

Protected main already serves POST /v1/temporal-context on AnalysisRunLiveService / tepp-loopback, but LineageWeave operators still had to write raw HTTP/1.1. Stdout stays cutoff-safe and metric-free with claim_boundary association_not_causal. tepp.scientific_acceptance.v1 never appears. The CLI does not infer causality.

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 by id
• 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 scientific-acceptance loopback CLI
• feat(api): enumerate analysis runs via loopback collection GET #368 collection GET
• feat(api): enumerate analysis runs via loopback collection CLI #371 collection CLI list
• feat(api): cancel analysis runs via loopback CLI #378 cancel CLI
• feat(api): create analysis runs via loopback CLI #385 create CLI
• feat(api): inspect analysis-run status via loopback CLI #392 status CLI
• feat(api): POST retry from published tepp-retry CLI #394 retry CLI
• feat(api): inspect stored analysis-run requests via loopback CLI #395 stored-request CLI
• feat(api): POST running and terminal from published tepp-lifecycle CLI #397 lifecycle CLI
• feat(api): GET retry parent from published tepp-retry-parent CLI #400 retry-parent CLI
• feat(api): resolve analysis-run identity via loopback lookup CLI #401 lookup CLI
• feat(api): GET retry children from published tepp-retry-lineage CLI #403 retry-lineage CLI
• feat(api): wait for analysis-run terminal status via loopback CLI #406 wait CLI
• feat(api): authorize purpose-bound exports via loopback CLI #410 export-authorize CLI
• feat(api): retrieve authorized exports via loopback GET #411 export-retrieval GET
• feat(persistence): persist idempotent analysis runs #287 GAP-003B persistence/Compose
• feat(network): replace union-find stand-in with Leiden consensus #351 Leiden
• GAP-010 Figma/export

What

LineageWeave temporal-context CLI stacked on protected main 1bc02f580cf48e1d39da239f0e818453437c31c3:

• tepp-temporal-context query client of POST /v1/temporal-context on tepp-loopback
• stdin is TemporalContextRequest JSON; consumer is lineageweave only
• no idempotency-key (bounded read, not a durable create)
• metric-free association_not_causal stdout; tepp.scientific_acceptance.v1 never prints
• loopback-only; credential flags, empty stdin, unknown verbs, and metric keys fail closed
• ADR 0027 on protected main (distinct from GET-status ADR 0027 on other stacks)

Not an ADR 0014 scientific claim. Not persistence. Not a causal score. Not project-history CLI.

Verification

• cargo clippy -p tepp_api --all-targets -- -D warnings
• cargo test -p tepp_api --lib temporal_context_cli
• cargo test -p tepp_api --test temporal_context_cli_contract
• RUSTDOCFLAGS='-D warnings' cargo doc -p tepp_api --no-deps
• python3 scripts/validate_documentation.py
• python3 scripts/check_docstrings.py

Exact head: a4409f96aa6123d12f26f8df59843aa92596a81e

Do not merge without two independent APPROVE reviews on this exact head and current Checks. Author COMMENTED is not independent APPROVE.

[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]

Hour-28 exact-head: a4409f96aa6123d12f26f8df59843aa92596a81e. LineageWeave temporal-context CLI tepp-temporal-context query against tepp-loopback (POST /v1/temporal-context) stacked on protected main. Metric-free association_not_causal; tepp.scientific_acceptance.v1 never appears. Does not infer causality. Devin/CodeRabbit/author COMMENTED is not independent APPROVE. Ruleset 18156473 needs two independent APPROVE reviews. No self-approve.

[seonghobae]

Exact-head COMMENT on a4409f9 (draft). Unique occupied: tepp-temporal-context query POST /v1/temporal-context (ADR 0027) as LineageWeave consumer on AnalysisRunLiveService / tepp-loopback. Cutoff-safe, metric-free. Non-loopback host is AuthorizationDenied; non-LineageWeave consumer is InvalidWirePayload. Forbidden keys include rmse family, se_gate, scientific_acceptance, causal_score, causality.

Do not duplicate this POST CLI. Retrieval GET/CLI is #452; stored-request GET/CLI is #464. Do not un-draft. Zero reviews on this SHA before this COMMENT. Never self-approve. No PII in LineageWeave. Do not weaken fail-closed. No Buyer language.