fix(search): finish retirement and index maintenance on deploy

[icecrasher321]

Summary

• Finish legacy Search retirement in one deployment with 25,000-ID SQL pages, atomic cursor checkpoints, and bounded lock retries. Remove the one-minute/page-count deferral and pacing delay.
• Follow deletion with a separately journaled concurrent rebuild of the vector projection's HNSW indexes and vacuum/analyze of the affected tables. Resume completed maintenance steps and recover invalid temporary indexes after interrupted rebuilds.
• Preserve the selected cleanup scope, live Search configuration, and ordinary KB content. The deployment job keeps its existing five-hour timeout; index maintenance may dominate runtime.

Type of Change

• Bug fix

Testing

• All 114 database PostgreSQL/pgvector integration checks passed, including single-invocation completion, cascading deletes, scope isolation, rollback/resume, transient row locks, canceled concurrent index rebuilds, and maintenance checkpoints.
• All 104 database unit tests, database type-check, lint, API validation, migration safety, docs manifest, and all 52 repository audits passed.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• 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.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 29, 2026 11:04pm UTC

[icecrasher321]

@greptile

[icecrasher321]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@icecrasher321 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 5 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Critical risk] Database schema changes and migration ordering for search index retirement.

The PR appears safe to merge; no outstanding findings remain.

Summary

This PR completes Search embedding retirement in one migration run, then separately journals index rebuilding and vacuum maintenance.

• Retirement uses larger, atomic SQL pages with bounded retries and resumable cursors.
• Maintenance resumes from checkpoints and handles invalid indexes left by interrupted concurrent rebuilds.
• The runbook now states the existing session-affine connection requirement for both entry points.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Migration runner] --> B[0027: retire Search content]
  B --> C[Checkpoint completed pages]
  C --> D[Record retirement receipt]
  D --> E[0028: rebuild HNSW indexes]
  E --> F[Vacuum and analyze tables]
  F --> G[Record maintenance receipt]

Loading

_{Reviews (2) · Last reviewed commit: "docs(search): clarify retirement migrati..."}

[icecrasher321]

@greptile

[icecrasher321]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@icecrasher321 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 5 files

Confidence score: 5/5

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

_{Re-trigger cubic}