v9.0.0 — Social Monitoring & Quick Capture #139

Merged

claude-bot merged 8 commits from feat/v9-social-watch into main 2026-07-18 06:43:49 +00:00

Conversation 0 Commits 8 Files changed 30 +2470 -33

claude-bot commented 2026-07-18 06:18:03 +00:00

Contributor

Copy link

Milestone v9.0.0 — watch Bluesky/Mastodon accounts & tags and turn a matching post into an entry in one click.

Status: shipping v9.0.0 = P1 + #117 + P2 (Bluesky Jetstream). Account linking (P3) and Mastodon real-time are deferred to a dedicated spike (the issue's own recommendation — DPoP OAuth + browser flows can't be verified headlessly). The milestone's "done when" is P1 shipping; P2/P3 are upgrades. 334 tests pass (44 files), tsc clean, migration 052 applies, app build green. No new npm dependencies.

In this release

• P1 (#22) — Public-data watch + one-click capture (polling MVP). (migration 052)
• #117 — Worker-process split: BullMQ workers + streams can run in a dedicated worker container (safe-by-default; RUN_WORKERS_IN_API defaults on).
• P2 (#23, partial) — Bluesky Jetstream real-time consumer (single shared WS, server-side DID filter, reconnect/backoff, cursor resume; gated by watch.streamingEnabled, off by default; health at /api/watch/stream-status).

Deferred to a follow-up spike

• P2 (#23) — Mastodon real-time: needs an OAuth token (most instances no longer allow unauthenticated streaming) → lands with P3.
• P3 (#24) — Account linking: Mastodon OAuth2 + Bluesky AT-Protocol OAuth (DPoP + hosted client metadata). Security-sensitive + browser/PDS flows requiring live verification.
• Minor: a Watch-page stream-health chip (endpoint exists).

Closes #22.

🤖 Generated with Claude Code

Milestone [v9.0.0](https://git.rhoving.com/rbrooks/TeaLeaves/milestones) — watch Bluesky/Mastodon accounts & tags and turn a matching post into an entry in one click. **Status: shipping v9.0.0 = P1 + #117 + P2 (Bluesky Jetstream).** Account linking (P3) and Mastodon real-time are deferred to a dedicated spike (the issue's own recommendation — DPoP OAuth + browser flows can't be verified headlessly). The milestone's "done when" is P1 shipping; P2/P3 are upgrades. **334 tests pass** (44 files), tsc clean, migration 052 applies, app build green. No new npm dependencies. ### In this release - [x] **P1 (#22)** — Public-data watch + one-click capture (polling MVP). *(migration 052)* - [x] **#117** — Worker-process split: BullMQ workers + streams can run in a dedicated `worker` container (safe-by-default; `RUN_WORKERS_IN_API` defaults on). - [x] **P2 (#23, partial)** — Bluesky **Jetstream** real-time consumer (single shared WS, server-side DID filter, reconnect/backoff, cursor resume; gated by `watch.streamingEnabled`, off by default; health at `/api/watch/stream-status`). ### Deferred to a follow-up spike - [ ] **P2 (#23) — Mastodon real-time**: needs an OAuth token (most instances no longer allow unauthenticated streaming) → lands with P3. - [ ] **P3 (#24)** — Account linking: Mastodon OAuth2 + Bluesky AT-Protocol OAuth (DPoP + hosted client metadata). Security-sensitive + browser/PDS flows requiring live verification. - [ ] Minor: a Watch-page stream-health chip (endpoint exists). Closes #22. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 4 commits 2026-07-18 06:18:03 +00:00

feat(v9 p1): social watch backend — watches, poller, discovered posts, search ... d3631f8864

Migration 052: watches (project-scoped subscriptions) + discovered_posts
(review queue, deduped by source_id). Platform adapters (bluesky via public
AppView, mastodon via instance REST through the SSRF guard) behind a small
WatchAdapter interface. watchWorker: BullMQ repeatable poll (interval
watch.pollIntervalMinutes, default 10) enqueuing per-watch polls. Routes at
/api/watch: watches CRUD (instance_url SSRF-validated on create), discovered-
post queue + add/dismiss, and live direct search. addSocialPostAsEntry runs
checkDedup before insert (mirrors importWorker), surfacing an existing entry on
an exact source_id match rather than duplicating.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

test(v9 p1): watch endpoints — CRUD, SSRF guard, queue add/dismiss, dedup ... 565eb20716

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

feat(v9 p1): Watch frontend — nav item + page (Watches/Queue/Search) ... 1f71c532fc

New top-level Watch nav (desktop + mobile overflow) with a pending-count badge.
WatchPage with three tabs: Watches (list/create/enable/delete, Mastodon caveat
inline), Queue (add-as-entry / dismiss with dedup messaging), Search (live
account/tag search → add to watchlist / add as entry). api client, plain-text
content, no new deps.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs(v9): changelog for P1 (social watch + one-click capture) ... 7cc942c588

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

rbrooks added 1 commit 2026-07-18 06:23:40 +00:00

feat(v9 #117): worker-process split — dedicated worker entrypoint ... 738b644cb2

Extract BullMQ worker startup into workers.ts (startWorkers) so it runs either
in the API process (RUN_WORKERS_IN_API=true, default — single-process deploys
unchanged) or a dedicated worker.ts process. index.ts starts them in-process
only when the flag is set; the API always owns migrations. deploy/compose.yaml
gains a `worker` service (same image, node dist/worker.js, depends_on api
healthy) with RUN_WORKERS_IN_API=false on the API — the P2-streaming prereq.
Safe-by-default: image auto-update never changes topology (Watchtower swaps
images, not compose); a host adopts the split by updating its compose. Documented
in deploy/README.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

rbrooks added 1 commit 2026-07-18 06:30:46 +00:00

feat(v9 p2): Bluesky Jetstream real-time consumer (#23) ... c8c5f93d57

A single shared Jetstream WebSocket per instance filters server-side by
wantedDids = every watched Bluesky account DID (resolved from handles),
wantedCollections=app.bsky.feed.post — genuinely real-time, cheap regardless of
watch count. Reconnect with backoff, cursor resume, dynamic DID-set refresh.
Runs in the worker set (#117); gated by watch.streamingEnabled (default off) and
additive to polling (global source_id UNIQUE dedupes). Cross-process health via
a Redis heartbeat, exposed at GET /api/watch/stream-status.

Scoping (honest platform reality): Mastodon real-time needs an auth token
(most instances no longer allow unauthenticated streaming), so it lands with P3
account linking; Mastodon + Bluesky tags stay on polling for P2. Extracted the
shared landDiscoveredPost helper. Pure event parser unit-tested.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

rbrooks added 1 commit 2026-07-18 06:32:17 +00:00

docs(v9): changelog for #117 (worker split) + P2 (Jetstream) ... ccde10e22d

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

rbrooks added 1 commit 2026-07-18 06:35:50 +00:00

chore(release): v9.0.0 — Social Monitoring & Quick Capture ... 980769d5d2

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

claude-bot added this to the v9.0.0 - Social Monitoring & Quick Capture milestone 2026-07-18 06:36:07 +00:00

claude-bot merged commit 82e2b6d437 into main 2026-07-18 06:43:49 +00:00

claude-bot deleted branch feat/v9-social-watch 2026-07-18 06:43:50 +00:00

claude-bot referenced this pull request from a commit 2026-07-18 06:43:51 +00:00

v9.0.0 — Social Monitoring & Quick Capture (#139)

claude-bot referenced this pull request 2026-07-18 06:44:24 +00:00

v9 P2: Real-time ingestion (streaming) #23

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

future

Unscoped / not yet prioritized — no milestone

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

wontfix

This won't be fixed

No labels

bug

duplicate

enhancement

future

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No milestone

v9.0.0 - Social Monitoring & Quick Capture

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

rbrooks/TeaLeaves!139

No description provided.