2026-10-03 · Creator Publishing Hub Personal Social Desk, Owned-device Agent Data API, Audience Profile Scanner Status
Social Desk distinguishes fresh successful checks from historical coverage and reports active retry workers accurately.
What changed
- Report the observer revisions actually saved in captured evidence separately from the application's evidence policy. A packaged policy revision does not imply that an existing scanner was upgraded.
- Keep historical coverage explicit and expose the last 24-hour window, successful observations, attempts and access failures separately through the PWA and agent API. These are distinct-profile counts, not a daily all-attempt quota ledger.
- Inspect existing owned scanner processes without changing them. Verified running retry workers take precedence over an idle or previously failed timer service; unavailable inspection remains unknown.
- Label the PWA scan ring as saved coverage, display recent successful checks visibly, and retain compact explanatory tooltips. Refresh cached application assets for the corrected display.
Verification
- All 41 focused checks passed for revision provenance, historical versus recent evidence, running retries alongside an idle or failed canonical service, and unavailable process inspection. A read-only host probe independently found active retries while the scheduled service was idle.
- The complete local application suite passed 799 tests with one platform skip; all 800 passed during Linux deployment, along with 20 scanner Node checks and seven Python checks. Source syntax and the feature contract passed for all nine views.
- Live owned-device reads verified the installed version, captured observer revision, active worker count and explicit recent window. The rendered PWA showed active scanning, recent successful checks, detailed statistics and protected owner evidence. Owner notes and the completed WebP processing result survived restart.
Rollout
Installed and independently verified in the maintained PWA and owned-device API. Existing scanner workers continued running with their original source. Parallel scanner adoption, native follow-notification capture and browser extension activation remain pending.
Updating
- Install the maintained Social Desk patch and refresh the PWA. Existing saved records need no migration.
- Continue the existing authenticated scanner and coordinator queues. Scanner adoption requires the coordinator plan and a separate verified idle transition.
Scope and limitations
- Historical coverage is not proof of a completed fresh rescan. Recent counters describe saved evidence for distinct linked profiles; they do not prove every retry or enforce the separate daily attempt limit.
- Fresh public enrichment can still omit fields that were not captured. Missing bios, posts or engagement cannot be interpreted as an inactive person.
- The roster remains partial unless complete-capture evidence says otherwise. Per-person unfollow logic cannot infer departures from missing names in a partial roster; native follow-notification capture remains pending.
- The reviewed parallel scanner package is not the currently installed worker. No new follower-removal or purge queue is created; cleanup remains paused during the fresh-rescan review.