Set up automatic upstream sync workflow

[JaL-P]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

🧪 How Has This Been Tested?

Please describe how you tested your changes so that maintainers can verify them. Include enough detail for someone else to reproduce your tests.

Checklist:

• Verified output manually
• Tested with relevant sample documents or data
• Wrote Vite Test Case (if applicable)

Expected Results:

• What the tests should produce (e.g., correct PDF rendering, no errors).

Actual Results:

• What you observed when running the tests.

Checklist:

• I have signed the Contributor License Agreement (CLA) or my organization has signed the Corporate CLA
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[github-actions]

CLA Signature Required

Thank you for your contribution! Before we can accept your pull request, you need to sign our Contributor License Agreement (CLA).

Why do we need a CLA?

BentoPDF uses a dual licensing model (AGPL-3.0 for open source + commercial license). The CLA allows us to:

• Include your contributions in both open source and commercial versions
• Protect you and us legally
• Keep the project sustainable

How to sign

To sign the CLA, please comment on this PR with:

I have read the CLA Document and I hereby sign the CLA

For corporate contributions, please have your organization sign our Corporate CLA (CCLA) by contacting us at [email protected].

---

⚠️ Note: You only need to sign the CLA once. Future contributions to this repository will not require re-signing.

---

I have read the CLA Document and I hereby sign the CLA

---

0 out of 2 committers have signed the CLA.
❌ @JaL-P
❌ @claude
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[MrFreePress]

Not approving. This introduces a scheduled workflow that can push directly to main, and it also currently has a failed CLA check. This needs deliberate maintainer review and likely stronger guardrails before merge.