Steve Yegge 1e97d9ccee fix: Exclude tombstones from orphan detection warnings ...

Orphan detection was reporting tombstoned issues (already deleted) as
orphans, causing repeated warnings during sync. Filter out status='tombstone'
from the orphan query.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-17 23:20:21 -08:00

..

001_dirty_issues_table.go

…

002_external_ref_column.go

…

003_composite_indexes.go

…

004_closed_at_constraint.go

…

005_compaction_columns.go

…

006_snapshots_table.go

…

007_compaction_config.go

…

008_compacted_at_commit_column.go

…

009_export_hashes_table.go

…

010_content_hash_column.go

…

011_external_ref_unique.go

…

012_source_repo_column.go

…

013_repo_mtimes_table.go

…

014_child_counters_table.go

…

015_blocked_issues_cache.go

…

016_orphan_detection.go

fix: Exclude tombstones from orphan detection warnings

2025-12-17 23:20:21 -08:00

017_close_reason_column.go

fix(db): add close_reason column to issues table (bd-uyu)

2025-12-01 21:56:41 -08:00

018_tombstone_columns.go

feat(tombstone): implement delete-to-tombstone and TTL expiration (bd-3b4, bd-olt)

2025-12-05 16:20:43 -08:00

019_messaging_fields.go

feat(schema): add messaging fields for bd-kwro epic

2025-12-16 13:06:47 -08:00