feat(ci): add github action for automated feature table sync

[Piotr1215]

Summary

Add scheduled GitHub Action workflow to auto-check feature table sync with upstream repos and create PR when drift detected.

• Schedule: Weekly on Monday at 09:00 UTC
• Manual trigger: Supports workflow_dispatch for ad-hoc syncs
• Auto-PR: Uses peter-evans/create-pull-request when drift found

How it works

1. Runs npm run validate-upstream to check for drift
2. If drift detected, runs npm run sync-upstream to update local files
3. Creates PR with changes to src/data/features.yaml and src/data/products.yaml

Upstream sources

• Features: loft-sh/admin-apis/definitions/features.yaml
• Tiers: loft-sh/plans/*.yaml

Test plan

• Workflow syntax is valid (CI will check)
• Can be triggered manually via Actions tab
• Weekly schedule is correctly configured

Note

Adds a GitHub Actions workflow for automated weekly syncing of feature tables from upstream repositories. The workflow validates for drift and creates PRs when changes are detected.

^{Generated by Claude for 536e65e}

Closes DEVOPS-508

[netlify]

✅ Deploy Preview for vcluster-docs-site ready!

Name	Link
🔨 Latest commit	536e65e
🔍 Latest deploy log	https://app.netlify.com/projects/vcluster-docs-site/deploys/697ceb97791bf900075751cc
😎 Deploy Preview	https://deploy-preview-1653--vcluster-docs-site.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[loft-bot]

Claude finished @Piotr1215's task in 1m 6s —— View job

---

Issues Found

Found 4 security issues where the workflow unnecessarily uses a custom GH_ACCESS_TOKEN secret instead of the default GITHUB_TOKEN. This creates unnecessary security risks and dependencies on custom secrets.

All GitHub Actions workflows should use the built-in GITHUB_TOKEN unless specific additional permissions are required. The GITHUB_TOKEN already has sufficient permissions for:

• Checking out code
• Reading from public repositories via gh CLI
• Creating pull requests in the same repository

Using custom access tokens introduces security risks and maintenance overhead.

[github-actions]

DEVOPS-508: add github action for automated feature table sync