feat: blabsy and pictqiue filter

[coodos]

Description of change

Issue Number

Type of change

• Breaking (any change that would cause existing functionality to not work as expected)
• New (a change which implements a new feature)
• Update (a change which updates existing functionality)
• Fix (a change which fixes an issue)
• Docs (changes to the documentation)
• Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• New Features

  • Introduced eVault Logs viewer with search by eVault identifier, comprehensive log display featuring timestamps, operation status indicators, ontology details, envelope identifiers, and paginated browsing for efficient navigation.

• Bug Fixes

  • Chat and message conversation lists now correctly filter to display only conversations with multiple participants.

[coderabbitai]

Warning

Rate limit exceeded

@coodos has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 2 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 59 minutes and 2 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 87bc3054-0b68-478a-814b-09b73e06d833

📥 Commits

Reviewing files that changed from the base of the PR and between a4be956 and 387f59e.

📒 Files selected for processing (3)

• infrastructure/dev-sandbox/src/routes/+page.svelte
• platforms/blabsy/client/src/components/chat/chat-list.tsx
• platforms/pictique/client/src/routes/(protected)/messages/+page.svelte

📝 Walkthrough

Walkthrough

This PR adds eVault Logs functionality to the dev-sandbox interface with a new tab displaying logs fetched via API, and implements filtering to exclude single-participant chats from two separate client platforms' chat list displays.

Changes

Cohort / File(s)	Summary
eVault Logs Feature infrastructure/dev-sandbox/src/routes/+page.svelte	Added new eVault Logs tab with state management (logsEName, evaultLogs, pagination flags), typed EvaultLog model, and loadEvaultLogs function that validates input, resolves eVault base URI via registry, fetches logs from API with cursor-based pagination, and renders logs table with operation badges, timestamps, and "Load More" functionality.
Chat Filtering Across Platforms platforms/blabsy/client/src/components/chat/chat-list.tsx, platforms/pictique/client/src/routes/(protected)/messages/+page.svelte	Implemented filtering to hide single-participant chats by deriving visibleChats (blabsy) and filtering chats with participants.length < 2 during transformation (pictique), restricting chat list and message pagination to conversations with 2+ participants.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Client as Client UI
    participant Registry as Registry API
    participant PlatformAuth as Platform Auth
    participant eVault as eVault API

    User->>Client: Enter eName and click "Load Logs"
    Client->>Client: Validate eName from input or selectedIdentity
    Client->>Registry: Resolve eVault base URI (if needed)
    Registry-->>Client: Return resolved base URL
    Client->>PlatformAuth: Request platform bearer token
    PlatformAuth-->>Client: Return token
    Client->>eVault: GET /logs with token, limit, cursor
    eVault-->>Client: Return logs array and nextCursor
    Client->>Client: Append/replace logs in state
    Client-->>User: Display logs table with pagination
    alt User clicks "Load More"
        User->>Client: Click "Load More"
        Client->>eVault: GET /logs with nextCursor
        eVault-->>Client: Return additional logs
        Client->>Client: Append new logs to table
        Client-->>User: Update table with more results
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat: blabsy active chat indcator #320: Modifies the same platforms/blabsy/.../chat-list.tsx component for styling changes, while this PR introduces chat filtering logic to the same component.

Suggested reviewers

• ananyayaya129
• sosweetham

Poem

🐰✨ Logs are gathered, chats now lean,
With two or more, the scene is clean!
Pagination hops from page to page,
eVault unfolds upon the stage—
Filter, fetch, and show with care! 🎯📋

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/log-viewer-w3ds

---

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 and usage tips.}