@gurupanguji

Goal

Make the social metadata PR tail choose between direct merge and auto-merge without changing the posting logic.

Steps

1. Create and commit a short spec and implementation plan for the workflow fix.
2. Add a focused failing unit test for merge mode selection on clean and blocked PR states.
3. Implement a small helper script that reads gh pr view --json output and returns direct or auto.
4. Update .github/workflows/publish_social.yml to call the helper and branch between gh pr merge --squash and gh pr merge --auto --squash.
5. Run the focused unit test and inspect the workflow diff.

Verification

• python3 -m unittest tests.test_social_metadata_pr_merge -q
• confirm the helper chooses direct for a clean, mergeable PR
• confirm the helper chooses auto for a PR that is not yet mergeable
• confirm the workflow only changed the final metadata PR merge tail