fix: show ingestion error inline on failed Knowledge table rows

[Thenathanb]

Summary

• Hovering a failed row's status badge in the Knowledge table now shows a tooltip with the resolved ingestion error message, instead of requiring a click into the Task dialog just to see why a file failed.
• Clicking the badge still opens the Task dialog exactly as before — no change to that behavior.
• Reuses the existing Tooltip component already used elsewhere in the same file (e.g. the filename column).

Test plan

• npm run typecheck passes with no errors
• npm run lint (biome) shows no new warnings
• Manually verified in the browser: uploaded a corrupted PDF, confirmed the failed row shows a tooltip with the full Docling error message on hover, wraps correctly instead of overflowing, and clicking still opens the Task dialog

Summary by CodeRabbit

• Bug Fixes
  • Knowledge grid ingestion failures now display the associated error message in a tooltip when hovering over the error action.
  • Error action accessibility labels now include the relevant ingestion error when available.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 88b71bf4-4ad3-46b4-83f0-fc32d740536e

📥 Commits

Reviewing files that changed from the base of the PR and between 452f69b and 7742464.

📒 Files selected for processing (1)

• frontend/app/knowledge/page.tsx

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

Walkthrough

The knowledge grid now shows ingestion error text in a tooltip and includes that text in the failed-row button’s accessible label.

Changes

Knowledge error display

Layer / File(s)	Summary
Failed status error details frontend/app/knowledge/page.tsx	The failed-status renderer stores the button in a local variable. The button label includes the error message when available. Rows with errors wrap the button in a tooltip; other rows render the button directly.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 77424

Failed Knowledge ingestion rows now expose their resolved error in an accessible label and hover tooltip while retaining the existing task-dialog action. No current merge-blocking risk remains.

Suggested labels: enhancement

Suggested reviewers: mfortman11, edwinjosechittilappilly, jason-dong03

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: showing ingestion errors inline on failed Knowledge table rows.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[mfortman11]

Medium Issue
Resolve task errors before rendering the tooltip —

When a legacy/provider failure supplies wrapped JSON in fileInfo.error, TaskContext copies that raw value into data.error, whereas the Task dialog passes it through resolveTaskFileError and formatProviderErrorMessage. Rendering data.error directly therefore shows raw backend payloads instead of the resolved user-facing message promised by this change; apply the same resolution used by the dialog.