Small bugfixes on prompts, return types

[NolanTrem]

🚀	This description was created by Ellipsis for commit 0927140

Summary:

This pull request includes minor bug fixes and improvements, such as updating return types, removing unused functions, and correcting error messages and imports across multiple files.

Key points:

• Updated return types in js/sdk/src/r2rClient.ts for rag and agent functions to include Promise<ReadableStream<Uint8Array>>.
• Removed unused async functions aupdate_documents and aevaluate in py/core/main/engine.py.
• Corrected error message in py/core/main/services/ingestion_service.py to suggest update_files instead of update_documents.
• Fixed import order in py/core/base/abstractions/__init__.py.
• Corrected spelling in py/core/providers/prompts/defaults/rag_agent.yaml from "relevent" to "relevant".
• Adjusted import order in py/core/base/abstractions/__init__.py for consistency.

---

Generated with ❤️ by ellipsis.dev

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 0927140 in 1 minute and 5 seconds

More details

• Looked at 452 lines of code in 13 files
• Skipped 0 files when reviewing.
• Skipped posting 4 drafted comments based on config settings.

1. js/sdk/src/r2rClient.ts:1180

• Draft comment:
  The change from @featureGenerator to @feature might affect the functionality if @feature does not handle generators. Ensure that the decorator is intended for this use case.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  The comment is relevant to the changes made in the diff. It points out a potential issue with the change from @featureGenerator to @feature, which could affect functionality if the decorator does not handle generators. This is a valid concern and not something that would be caught by a build or is obvious, making it a useful comment.
  The comment could be seen as speculative since it suggests a potential issue without confirming it. However, it is directly related to the change and highlights a possible oversight that could lead to a bug.
  The comment is not purely speculative; it is based on a change in the code that could have significant implications. It is important to highlight such potential issues during a code review.
  The comment should be kept as it highlights a potential issue with the change from @featureGenerator to @feature, which is directly related to the changes made in the diff.

2. js/sdk/src/r2rClient.ts:1238

• Draft comment:
  The change from @featureGenerator to @feature might affect the functionality if @feature does not handle generators. Ensure that the decorator is intended for this use case.
• Reason this comment was not posted:
  Marked as duplicate.

3. py/core/main/services/ingestion_service.py:324

• Draft comment:
  Ensure that the change from update_documents to update_files is consistent across the codebase, including documentation and tests.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The change in the error message from update_documents to update_files should be consistent across the codebase.

4. py/tests/regression/expected_outputs/test_document_management.json:206

• Draft comment:
  Ensure that the change from update_documents to update_files is consistent across the codebase, including documentation and tests.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The change in the error message from update_documents to update_files should be consistent across the codebase.

Workflow ID: wflow_LExiwnRhWnAj0pis

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.