X social lane has been silent since 2026-05-14 — intentional?

[CamSoper]

Found during the 2026-08-18 DWH ingestion audit, from the social-post-state data now in the warehouse (INFORMATION_MARTS.COMMUNITY.FCT_SOCIAL_POST_STATE, fed by posted.json / posted-social.json in the social-post-state bucket):

Platform	Posts recorded	Latest post
LinkedIn	65	2026-08-14
Bluesky	62	2026-08-14
X	13	2026-05-14

LinkedIn and Bluesky have posted continuously through mid-August, while the X lane has recorded nothing for three months. Blog posts still carry X copy in their frontmatter (draft-social-post still generates it), so if this is unintentional it's likely a credential/API failure in the posting path rather than a content gap — the state files record _failures, so the schedule-social logs around mid-May would show whether posts started erroring.

The posting internals live in the private social_core dependency (pulumi-social-core), so triage probably starts there or in the schedule-social workflow runs.

Ask: confirm whether dropping X was a deliberate decision. If deliberate, we should stop generating X copy in frontmatter and note it for the data team (the platform split in fct_social_post_state reads as a breakage otherwise). If not, restore the lane.

[adamgordonbell]

We are using upload-post as a integration layer to the social media sites and not long after this feature was rolled out they dropped support for posting to X. So plan is to use X api directly ( perhaps we should remove upload-post all together, for linked in and blue sky as well. )

this is on @jkramer-debug backlog and will be addressed.