fix(docs): correct db:push backfill description

[waleedlatif1]

Summary

• Remove the incorrect claim that db:push skips backfills; it runs the search-vector backfill after schema reconciliation.

Type of Change

• Documentation fix

Testing

• Verified the wording against the push runner.
• Lint, all 46 repository 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 (documentation only)
• 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 16, 2026 6:36am UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

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

_{Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

The documentation correction appears safe to merge.

Summary

This documentation-only PR corrects the development database guidance by removing the inaccurate claim that db:push skips backfills.

• Preserves db:migrate as the canonical staging and production command.
• Accurately states that db:push bypasses versioned migration guards.
• Aligns the contributor guidance with the push runner, which performs required database post-steps, including the search-vector backfill.

_{Reviews (1) · Last reviewed commit: "fix(docs): correct db:push backfill desc..."}