feat(api): enumerate project histories via loopback collection GET - #424
feat(api): enumerate project histories via loopback collection GET#424seonghobae wants to merge 1 commit into
Conversation
LineageWeave operators can GET /v1/project-histories on tepp-loopback without guessing idempotency keys. Metric-free temporal_association_only identities only. tepp.scientific_acceptance.v1 never appears. Evidence text and findings stay off the page. Does not infer causality. Not project-history CLI. Stacked on protected main.
|
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 |
|
Hour-29 exact-head: |
Folded into #428
Closed as
superseded_by_fold, not discarded. #428's head contains this PR as its direct ancestor and has been retargeted to protectedmain, so the project-history collection GET implementation/tests and this review history remain intact while queue WIP is reduced. Retrieval vehicles #431/#456 also retain this ancestry.Canonical collection landing vehicle: #428 (
feat(api): consolidate project-history collection GET and CLI).Do not reopen unless a surviving folded head demonstrably loses unique behavior or evidence.