feat: logs chain support in logstore (backend)

[impoiler]

Summary

Briefly explain the purpose of this PR and the problem it solves.

Changes

• What was changed and why
• Any notable design decisions or trade-offs

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Describe the steps to validate this change. Include commands and expected outcomes.

# Core/Transports
go version
go test ./...

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

If adding new configs or environment variables, document them here.

Screenshots/Recordings

If UI changes, add before/after screenshots or short clips.

Breaking changes

• Yes
• No

If yes, describe impact and migration instructions.

Related issues

Link related issues and discussions. Example: Closes #123

Security considerations

Note any security implications (auth, secrets, PII, sandboxing, etc.).

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Added a roots_only filter for log searches to show top-level entries without duplicate fallback children.
  • Root results now include aggregated child count, cost, and token usage.
  • Added support for the roots_only query parameter in HTTP log searches.

• Bug Fixes

  • Corrected parent relationships for fallback LLM attempts.
  • Prevented self-referencing and filtered-out parent entries from producing incorrect results.

Walkthrough

Adds a roots_only log search filter. Root-only queries exclude matching child rows, promote children with hidden parents, attach child aggregates, and bypass materialized views. HTTP parsing, fallback parent assignment, and SQLite coverage were added.

Changes

Roots-only log search

Layer / File(s)	Summary
Search contracts and request wiring framework/logstore/tables.go, transports/bifrost-http/handlers/logging.go, plugins/logging/main.go	SearchFilters accepts RootsOnly. Log exposes transient child aggregate fields. The HTTP handler parses roots_only, and fallback requests use the primary request as their parent.
Root filtering and aggregation framework/logstore/rdb.go, framework/logstore/matviews.go	Root-only filtering preserves self-referencing and missing-parent rows, promotes children whose parents are outside the filtered scope, and uses dialect-specific queries. Returned roots include filtered child count, cost, and token totals. Materialized views are excluded.
Roots-only behavior validation framework/logstore/rdb_rootsonly_test.go	SQLite tests cover root selection, aggregates, self-references, parent filters, scopes, child retrieval, parent promotion, and materialized-view eligibility.

Estimated code review effort: 4 (Complex) | ~45 minutes

Suggested reviewers: akshaydeo, pratham-mishra04

Sequence Diagram(s)

sequenceDiagram
  participant HTTPHandler
  participant RDBLogStore
  participant Database
  HTTPHandler->>RDBLogStore: SearchLogs with RootsOnly
  RDBLogStore->>Database: Apply root filtering
  RDBLogStore->>Database: Load child count, cost, and token aggregates
  Database-->>RDBLogStore: Root rows and aggregates
  RDBLogStore-->>HTTPHandler: Filtered logs with aggregate fields
``

</details>

<!-- walkthrough_end -->
<!-- pre_merge_checks_walkthrough_start -->

<details>
<summary>🚥 Pre-merge checks | ✅ 2 | ❌ 3</summary>

### ❌ Failed checks (3 warnings)

|         Check name         | Status     | Explanation                                                                                                                            | Resolution                                                                                                                            |
| :------------------------: | :--------- | :------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------ |
|      Description check     | ⚠️ Warning | The description contains only the unfilled template and does not document the implementation, testing, affected areas, or decisions.   | Complete the Summary, Changes, Type, Affected areas, How to test, Breaking changes, Related issues, Security, and Checklist sections. |
|     Linked Issues check    | ⚠️ Warning | The PR implements log-chain and roots-only logstore behavior, but issue `#123` requires provider File APIs such as POST /v1/files.       | Implement the File APIs requested in `#123`, or link the correct log-chain issue and update the PR scope.                               |
| Out of Scope Changes check | ⚠️ Warning | All summarized changes concern log chains and roots-only log filtering, which are unrelated to the linked File APIs objective in `#123`. | Remove the unrelated logstore changes, or replace or update the linked issue so the stated objective matches the PR scope.            |

<details>
<summary>✅ Passed checks (2 passed)</summary>

|     Check name     | Status   | Explanation                                                                                                |
| :----------------: | :------- | :--------------------------------------------------------------------------------------------------------- |
|     Title check    | ✅ Passed | The title clearly summarizes the main change: backend log-chain support in the logstore.                   |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |

</details>

</details>

<!-- pre_merge_checks_walkthrough_end -->
<!-- finishing_touch_checkbox_start -->

<details>
<summary>✨ Finishing Touches</summary>

<details>
<summary>📝 Generate docstrings</summary>

- [ ] <!-- {"checkboxId": "7962f53c-55bc-4827-bfbf-6a18da830691"} --> Create stacked PR
- [ ] <!-- {"checkboxId": "3e1879ae-f29b-4d0d-8e06-d12b7ba33d98"} --> Commit on current branch

</details>
<details>
<summary>🧪 Generate unit tests (beta)</summary>

- [ ] <!-- {"checkboxId": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "radioGroupId": "utg-output-choice-group-unknown_comment_id"} -->   Create PR with unit tests
- [ ] <!-- {"checkboxId": "6ba7b810-9dad-11d1-80b4-00c04fd430c8", "radioGroupId": "utg-output-choice-group-unknown_comment_id"} -->   Commit unit tests in branch `07-24-feat_show_logs_chain_backend`

</details>

</details>

<!-- finishing_touch_checkbox_end -->
<!-- tips_start -->

---




<sub>Comment `@coderabbitai help` to get the list of available commands.</sub>

<!-- tips_end -->

Loading

[impoiler]

• feat: logs chain support in logstore (backend) #6011 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@framework/logstore/rdb.go`:
- Around line 914-918: Update the aggregate attachment condition around
attachChildAggregates so it runs only when filters.RootsOnly is true and
filters.ParentRequestID is empty. Preserve the existing error propagation and
skip aggregate attachment for ParentRequestID-specific queries.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 456da20e-8948-4485-9c8f-42b4cd7cd052

📥 Commits

Reviewing files that changed from the base of the PR and between c90f9c3 and c1bd494.

📒 Files selected for processing (6)

• framework/logstore/matviews.go
• framework/logstore/rdb.go
• framework/logstore/rdb_rootsonly_test.go
• framework/logstore/tables.go
• plugins/logging/main.go
• transports/bifrost-http/handlers/logging.go

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Honor ParentRequestID precedence for aggregates.

Line 914 attaches child aggregates when both filters are set. applyFilters correctly ignores RootsOnly when ParentRequestID is non-empty, but this post-query step still changes the response. Only attach aggregates for a roots-only list query without ParentRequestID.

Proposed fix

-if filters.RootsOnly {
+if filters.RootsOnly && filters.ParentRequestID == "" {
 	if err := s.attachChildAggregates(ctx, logs, filters); err != nil {
 		return nil, err
 	}
 }

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	if filters.RootsOnly {
	if err := s.attachChildAggregates(ctx, logs, filters); err != nil {
	return nil, err
	}
	}
	if filters.RootsOnly && filters.ParentRequestID == "" {
	if err := s.attachChildAggregates(ctx, logs, filters); err != nil {
	return nil, err
	}
	}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@framework/logstore/rdb.go` around lines 914 - 918, Update the aggregate
attachment condition around attachChildAggregates so it runs only when
filters.RootsOnly is true and filters.ParentRequestID is empty. Preserve the
existing error propagation and skip aggregate attachment for
ParentRequestID-specific queries.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ AdityaPainuli
✅ G-XD
✅ impoiler
❌ Pratham-Mishra04
_{You have signed the CLA already but the status is still pending? Let us recheck it.}