chore(ci): remove lockfile-sync workflow

[yuvrxj-afk]

Removes the Lockfile Sync workflow.

It regenerated pnpm-lock.yaml on every push to main and pushed it back, but corsair-team was never in main's branch-protection bypass allowlist — so every push 403'd. Zero successful syncs since it was added. The job runs post-merge and isn't a required check, so it blocks nothing; it only produced a recurring red X.

Lockfile correctness is already guaranteed by pnpm install --frozen-lockfile in the PR gate — a PR can't merge with an out-of-sync lockfile. PR_BOT_PAT is now unused (docs already list it as safe to delete).

Summary by CodeRabbit

• Chores
  • Removed the automated workflow that regenerated and committed lockfile updates after changes to the main branch.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
www	Ready	Preview	Aug 24, 2026 2:23am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d6fcbf22-4d56-4027-8197-0458fc65fab8

📥 Commits

Reviewing files that changed from the base of the PR and between bdbbc71 and 1dc5ff4.

📒 Files selected for processing (1)

• .github/workflows/lockfile-sync.yml

💤 Files with no reviewable changes (1)

• .github/workflows/lockfile-sync.yml

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request removes .github/workflows/lockfile-sync.yml. The deleted workflow regenerated and committed pnpm-lock.yaml after pushes to main, with serialized concurrency and push retries.

Changes

Cohort / File(s)	Summary
Lockfile synchronization workflow .github/workflows/lockfile-sync.yml	Removes automated lockfile regeneration and commit handling on pushes to main.
Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 1dc5f

This removes a non-required post-merge workflow that consistently failed without affecting merge gating, while lockfile validation remains part of the PR checks; no actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the removal of the lockfile synchronization workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-lockfile-sync

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

Removes the post-merge Lockfile Sync workflow, which could not push its generated lockfile commits through main branch protection.

• Deletes the push-to-main lockfile regeneration job.
• Removes the workflow’s checkout, pnpm setup, commit, retry, and push logic.
• Leaves pull-request frozen-lockfile validation as the active lockfile correctness mechanism.

Confidence Score: 5/5

The PR appears safe to merge because it removes a workflow that never successfully updated the lockfile and introduces no new reachable failure.

Lockfile validation remains available in pull-request CI, while the removed post-merge workflow provided no effective correction behavior because its pushes were consistently rejected.

Important Files Changed

Filename	Overview
.github/workflows/lockfile-sync.yml	Deletes a nonfunctional post-merge workflow whose attempted lockfile pushes were rejected by branch protection; no changed-code-triggered defect was identified.

_{Reviews (1): Last reviewed commit: "chore(ci): remove lockfile-sync workflow" | Re-trigger Greptile}