⚠️ Repository sync failed

[github-actions]

Repository synchronization encountered errors on commit 8842307.

✅ Running in APPLY mode (changes will be made to GitHub)

📖 Parsing REPOSITORIES.md...
🌐 Fetching GitHub organization state...
🔐 Checking transfer permissions...
🔍 Detecting drift...

🚧 INFO: Repository transfer feature under development
Found 1 repository(ies) with Origin field:
❌ migration-test ← TooAngel/worlddriven-migration-test
❌ 1 blocked (missing admin permission)
Transfer API implementation pending - see issue #9

📋 Generating sync plan...
🔍 Checking for empty repositories...
⚡ Executing sync plan...

✅ APPLY Repository Sync Report

Summary: 4 total actions

• Create: 0
• Update descriptions: 0
• Update topics: 0
• Initialize (add first commit): 0
• Ensure settings: 3
• Delete: 0
• Transfer (blocked): 1
• Skip (protected): 0

✅ Successfully Applied (2)

• Ensure settings for documentation

  • Applied standard configuration

• Ensure settings for webapp

  • Applied standard configuration

❌ Failed (1)

• ensure-settings for migration-test
  • Error: GitHub API error (404): {"message":"Not Found","documentation_url":"https://docs.github.com/rest/repos/repos#update-a-repository","status":"404"}

⚠️ Skipped - Manual Action Required (1)

• migration-test: Transfer blocked: ❌ worlddrivenbot has "read" access to TooAngel/worlddriven-migration-test (admin required)

---

Commit: 8842307
Triggered by: @worlddriven[bot]
Action: feat: add migration-test repository for testing transfer automation (#17)

• feat: add migration-test repository for testing transfer automation

Add test repository to validate the migration workflow before
migrating real repositories like worlddriven core.

Origin: TooAngel/worlddriven-migration-test

• feat: implement repository transfer API

Add transferRepository() function that calls GitHub's transfer API
to move repositories from external owners to the worlddriven org.

After transfer completes, standard settings and topics are applied.
Transfer errors are handled gracefully - if post-transfer config
fails, the transfer itself is still considered successful.

Closes #9

• fix: check worlddrivenbot's permission instead of worlddriven org

The permission check was looking for 'worlddriven' org as a collaborator,
but we invite 'worlddrivenbot' user. Changed to use the repo endpoint
which returns permissions for the authenticated user (worlddrivenbot).

Please review the errors above and take appropriate action.