fix(posts): make HasImage raise-only to stop rescan churn

TraverseDirectory's two AddPost call sites pass opposite hasImage values
for one post (duplicate _N folders, /blog/private bodies on own-blog
reblogs), and --ingest does the same across duplicate files. The
overwrite flipped the flag 0->1->0 and bumped DateModified every pass.
UpdatePost, AddPost's fallback and UpsertPostFromTextFile now only raise
HasImage, matching ByLikes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jimandClaude Opus 5.5 committed 2026-10-02 09:15:42 -05:00
1 parent 5af284a49f
commit e18fb5ca10
3 files changed
+30 -13

No files matched your search

+2 -1
View File
@@ -201,7 +201,8 @@ Notable:
(`Fri, 14 Feb 2025 15:20:09 GMT`); every write path runs `PostDates.Normalize` to
convert it, and `../normalize-postdate.sql` fixed the 4 rows written before that.
- `HasImage = 1` on 14,026 rows. It records that the post *had* a picture, not that a
usable URL was kept, so it is not a reliable predictor that anything will render.
usable URL was kept, so it is not a reliable predictor that anything will render. It is
raise-only: no import or crawl lowers it, only a manual correction does.
- `PhotoURL` is largely unused; in practice the image markup lives inside `Body`.
- `NotFound = 1` on 4,712 rows — posts that have since been deleted upstream.
- The content columns (`Body`, `Quote`, `Question`, `Answer`, …) are the heavy ones. List