fix(file-search): increase indexing worker memory

[icecrasher321]

Summary

• Increase workspace-file-search-index from medium-1x (2 GB) to medium-2x (4 GB) to give document parsers more memory before chunking.
• Update the existing task configuration test and document why parser memory needs a separate budget from indexed text size.

Type of Change

• Bug fix

Testing

Existing task and file-search unit tests, application type check, lint, all repository audits, block registry, and docs manifest checks.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 18, 2026 5:47am UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge because it makes a narrowly scoped, consistently tested worker-memory increase using an established machine preset.

Summary

This PR increases the workspace file-search indexing task’s Trigger.dev worker from medium-1x to medium-2x.

• Updates the configuration test to protect the larger worker preset.
• Documents the parser-specific memory rationale and separation between parser memory, complexity guards, and indexed-text limits.
• No security-sensitive behavior, data contracts, or indexing logic are changed.

_{Reviews (1) · Last reviewed commit: "fix(file-search): increase indexing work..."}

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}