2026-10-03 · Creator Publishing Hub Personal Social Desk, Engagement Watcher capture candidate
Review incoming follow invitations by sender and distinguish repeat promotion from verified engagement evidence.
What changed
- Add a separate incoming invitation ledger and bounded intake API. Inviting sender and promoted target remain distinct; repeated captures are deduplicated and displayed backlog counts stay separate from captured rows.
- Add a compact invitation review to Important updates with repeat sender summaries, promoted targets, engagement context and explanatory score reasons.
- A derived retention recommendation may apply an invitation penalty only when exact verified repeated invitations and a complete per-person engagement observation period support it. Positive engagement protects against this penalty. Missing engagement fields and name-only captures never establish inactivity.
- Package a read-only browser capture candidate for one visible batch at a time, with strict native sentence and anchor validation. The candidate does not scroll, accept or decline invitations.
Verification
- All 36 focused checks passed for exact identity, conservative capture deduplication, complete engagement-window gating, positive engagement protection, bounded native DOM extraction and the actual serialized HTTP intake.
- The full local application suite passed 835 tests with one platform skip. Syntax and the feature contract passed for all nine views, with 93 retained controls and 183 API routes. All eight public release-note checks passed.
- A synthetic 4,072-sender projection completed in approximately 82 milliseconds after engagement indexing; this measures local projection performance and does not establish native backlog capture.
- All 836 application tests passed on the deployment host, plus 20 scanner Node checks and seven Python checks. Live intake, duplicate replay, saved partial counts and rendered owner context were independently checked. Existing scanner source and active workers remained intact.
Rollout
Installed and verified in the PWA. Incoming native browser activation and batch declining remain pending.
Updating
- Install the maintained Social Desk patch and refresh the PWA. Existing audience and scanner data are preserved.
- The browser capture candidate requires a separate safe activation and native screen verification.
Scope and limitations
- An invitation does not prove that its sender follows the account. Display names cannot establish identity or link a namesake audience record.
- Current incoming captures remain unverified until the native producer has been activated and independently checked. Screenshot rows and displayed counts are review evidence with partial coverage.
- This update does not clear a backlog on Facebook. Bulk decline needs native screen, account and outcome proof plus safe coordination with the existing shared browser.
- No follower removal or purge is enabled by an invitation recommendation. Existing cleanup remains paused while fresh audience data is reviewed.