@gurupanguji

Objective

Update the automated social media publishing system to act as a queue. This ensures that all posts for a given day are published on the same day, prevents duplicate posts, and handles timing preferences (specifically, waiting for the site build and posting morning posts around 6:00am PT).

Background

Currently, .github/workflows/publish_social.yml runs once a day at 22:00 UTC and only posts the first matching snippet for the current date. scripts/publish_social.py does not track state across runs. We want to convert this into an event-driven and scheduled queue system.

Action Plan

1. Update Python Script (`scripts/publish_social.py`)

Modify the script to look for any file in _snippets/ (not just today’s) that does not contain published: true in its frontmatter.
For each unpublished snippet:
- Verify the post is live on the site.
- Publish to the requested platforms.
- Update the .md file to inject published: true and published_at: <timestamp> into the frontmatter.
Support processing multiple snippets in chronological order if multiple are found.

2. Update GitHub Action (`.github/workflows/publish_social.yml`)

Triggers:
- Change the schedule to cron: '0 13 * * *' (which corresponds to 13:00 UTC / 6:00 AM PT in PDT/PST roughly - we’ll use 14:00 UTC to be safe for 6:00 AM PST or 13:00 UTC for PDT. Let’s use 0 13 * * * and 0 14 * * * or just leave it to run on page_build only? Wait, we’ll use workflow_run on pages-build-deployment or page_build and a specific morning cron.
- Add page_build event trigger to catch ad-hoc builds during the day.
State Commit:
- Add steps to configure git user.
- After running the Python script, git add _snippets/, git commit -m "chore: mark social snippets as published", and git push.

3. Testing & Validation

Run tests on the python script to ensure it correctly identifies unpublished snippets and safely updates frontmatter without losing data.
Ensure GitHub Action has permissions: contents: write.