Implement automated GitHub label synchronization from README documentation

Implement automation to keep GitHub repository labels synchronized with the documentation in README.md.

Concept:
The worlddriven application democratizes repository management through automated processes. The project should apply this philosophy to itself by automatically managing its own GitHub labels based on documentation changes.

Implementation Ideas:

• Documentation-driven labels: Parse label definitions from README.md
• Automated sync on PR merge: Detect when label documentation changes and update GitHub labels accordingly
• Validation checks: Ensure documentation matches actual GitHub labels
• CI/CD integration: Add workflow step to sync labels after README changes

Technical Approach:

• Parse markdown label documentation from README.md
• Compare with current GitHub labels via API
• Create/update/delete labels to match documentation
• Run as part of CI/CD pipeline or webhook processing

Benefits:

• Consistency: Labels always match documentation
• Self-managing: Worlddriven manages its own repository automatically
• Democratic: Changes go through PR review process before taking effect
• Transparent: All label changes are documented and version controlled

Acceptance Criteria:

• Design label definition format in README.md (structured parsing)
• Implement label parser for markdown documentation
• Create GitHub API integration for label management
• Add automation trigger (webhook/CI on README changes)
• Include validation to prevent accidental label deletion
• Test with current label set
• Document the automation process

Priority: Medium

Start with README.md and determine a structured format for the documented labels. Then review the GitHub API and the proposed CI/CD or webhook trigger, with validation against the current label set. Done means parsing, comparison, safe create/update/delete behavior, automation, tests, and process documentation are all defined and working.