improvement(knowledge): skip redundant document resurrection writes

[waleedlatif1]

Summary

• Restrict document resurrection updates to soft-deleted rows, avoiding redundant writes for documents that are already live.
• Add a PostgreSQL regression test that verifies tombstone restoration and checks that the resurrection step leaves an active row's version unchanged.

Type of Change

• Performance improvement

Testing

• 16 PostgreSQL integration tests passed; the new regression test fails without the guard and passes with it.
• 216 focused connector unit tests passed.
• App type check, lint, all 47 audits (including API boundary validation), block registry validation, and docs manifest check passed.

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 19, 2026 2:01am UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge because it removes only a redundant null-to-null write while preserving tombstone resurrection.

Summary

This PR avoids redundant PostgreSQL tuple updates when the connector rediscovers documents that are already active.

• Restricts resurrection updates to eligible documents with a non-null deletion timestamp.
• Adds integration coverage proving tombstoned documents are restored while active documents are not rewritten.

_{Reviews (1) · Last reviewed commit: "improvement(knowledge): skip redundant d..."}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

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

_{Re-trigger cubic}