feat(collect): add an optional blog filter to --collect

"--collect 1 zomb-eh" now restricts the run to a single blog. The name is bound as a SQLite parameter and matched exactly against Posts.BlogName, which leads the primary key, so the predicate uses that index. Trailing arguments are scanned rather than positionally fixed: a token that parses as a date is the cutoff, anything else is the blog name, in either order. --blog=name forces the blog reading for a name that would otherwise parse as a date. The filter is a pure filter -- the zomb-eh 3-day refresh branch reads from the already-scoped PostsWithCount CTE, so a filtered worklist is a strict subset of the unfiltered one. Verified against TL.db: --collect 1 returns 651 posts, of which --collect 1 zomb-eh returns exactly its 164 and --collect 1 cs1d3blog exactly its 18. Blog-scoped runs are excluded from managed-run state, so collecting one blog cannot mark a full re-check complete. Co-Authored-By: Claude Opus 5 <[email protected]>
2026-08-08 21:47:38 -05:00
parent b31d5842cc
commit 0d9641db08
3 changed files with 109 additions and 41 deletions
@@ -31,7 +31,7 @@ dotnet run -- --test [blogname] [postID]  # Test API for specific post
 - `--test [blogname] [postID]`: Test API note collection
 - `--posts`: Export post blogs to file
 - `--blogs`: Export blog list to file
- `--collect`: Collect notes for all posts in DB
+- `--collect [0|1] [datetime] [blogname]`: Collect notes for posts in DB. Optional `blogname` restricts the run to one blog (exact match), e.g. `--collect 1 zomb-eh`
 - `--blogsR`: Export reply blogs to file
 - `--blogsO [start] [stop]`: Export blogs within range