2026-10-03 · Creator Publishing Hub Personal Social Desk, Audience Profile Scanner, Owned-device Agent Data API, Creator Publishing Hub Author Release Notes
Pinned and visitor posts no longer leave a misleading ordinary-activity date in saved Social Desk records.
What changed
- Normalize the saved profile-result projection before merging it into Social Desk. The newest positively owner-authored nonpinned visible post supplies latestVisiblePost and lastPostAt.
- Pinned-only observations explicitly report pinned-only with unknown ordinary activity and null ordinary date. Unproven authorship, absent posts and empty engagement do not establish inactivity. Future or invalid dates cannot displace valid observed posts.
- Related message and birthday profile-review summaries use the same derived fields. Captured facts, timestamps, original scanner ledgers, observer revision and protected owner decisions retain their provenance.
- Keep permanent public version pages and their index available through a scoped static cache generated from their published author-site content. The cache retains earlier entries and content verification markers while avoiding a saturated dynamic request pool.
Verification
- Twenty-four focused activity and owner-evidence checks passed, including the actual server result-pull path, pin and visitor precedence, newest-post ordering, idempotent derivation and protected-owner persistence.
- The complete local application suite passed 788 tests with one platform skip; all 789 passed during Linux deployment, along with 20 scanner Node checks and seven Python checks. The feature contract passed for all nine views. Live stored-field checks found null ordinary dates on pin-only records and matching newest owner-post dates; protected owner evidence survived result pulls and service restart.
- Canonical public HTTP readback verified current version-content digests and index links after the scoped cache rollout. An earlier permanent version page remained available with its original digest. The live PWA, owned-device API and completed private image-processing readback remain available.
Rollout
Installed and independently verified in the maintained PWA and author release-note cache. Existing result pulls now normalize saved ordinary activity while preserving original scanner evidence. Parallel worker adoption remains pending the coordinator plan, current-day accounting, an idle transition and a real canary. Native follow-notification capture and browser extension activation remain pending.
Updating
- Install the maintained Social Desk patch; existing result pulls refresh the derived fields without an audience database migration. Refresh the PWA to see current saved evidence.
- Retain the existing authenticated scanner and coordinator queues. Parallel worker adoption remains a separate verified idle transition.
Scope and limitations
- Coverage remains partial until fresh successful observations prove the rescan. Pin-only or unproven-author evidence cannot establish when a person last posted ordinarily.
- The parallel scanner transition and native follow-notification producer remain pending. No new follower-removal or purge queue is created; cleanup writes remain disabled during the rescan.
- Prior source ledgers remain unchanged for audit. Owner death confirmation remains separate from a Facebook memorial label.
- Release-note edits must be published through the maintained publisher so the scoped public cache and saved author pages remain synchronized.