Enhance Dockerfile and Vite configuration for library integration; re…

[tenkus47]

…factor API calls to use library service. Update environment variables for library API and adjust Nginx configuration for proxying library requests. Modify tests to mock new library service functions.

[greptile-apps]

Confidence Score: 4/5

The PR is not yet safe to merge because searches with more than 100 openable matches still hide all results beyond the adapter's fixed upstream window.

Findings

1.  Search window truncates pagination ▶

Fix with agent prompt

### Issue 1
src/services/library/search.ts:287
When an exact search has more than 100 openable segment matches, `multilingualSearch` fetches only the first 100 without forwarding the requested offset, paginates that truncated set locally, and calculates `total` from it. Results after the first 100 therefore remain unreachable, and a direct request with `skip` at or above 100 returns no sources despite additional matches.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

• Adds the library API client, adapters, mappers, and associated tests.
• Routes browser library requests through Vite and Nginx proxies.
• Refactors chapter, resource, collection, text, and search views to use the library service.
• Calculates search page counts from match totals rather than grouped sources.

Diagram

sequenceDiagram
  participant UI as Sources UI
  participant Adapter as multilingualSearch
  participant API as Library content search
  UI->>Adapter: "query, skip, limit=10"
  Adapter->>API: "query, limit=100"
  API-->>Adapter: first 100 hits
  Adapter->>Adapter: filter, group, slice(skip, skip+10)
  Adapter-->>UI: sources, total within first 100
  UI->>UI: derive page count from truncated total

Loading

_{Reviews (7) · Last reviewed commit: "Refactor layout and styling in Home, Par..."}

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

[greptile-apps]

Search window truncates pagination

When an exact search has more than 100 openable segment matches, multilingualSearch fetches only the first 100 without forwarding the requested offset, paginates that truncated set locally, and calculates total from it. Results after the first 100 therefore remain unreachable, and a direct request with skip at or above 100 returns no sources despite additional matches.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/services/library/search.ts
Line: 287

Comment:
**Search window truncates pagination**

When an exact search has more than 100 openable segment matches, `multilingualSearch` fetches only the first 100 without forwarding the requested offset, paginates that truncated set locally, and calculates `total` from it. Results after the first 100 therefore remain unreachable, and a direct request with `skip` at or above 100 returns no sources despite additional matches.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.