This PR updates the Copilot instructions to implement a beta-first development workflow as requested in the issue. The changes ensure all pull requests are properly routed through beta branches with appropriate version labeling.

Key Changes

Branch Strategy Implementation

• Beta-first workflow: All PRs must now target beta branches (format: beta-X.Y.Z) instead of directly targeting main
• Version-based branching: Clear instructions for creating beta branches based on semantic versioning:
  • patch releases (bug fixes): beta-X.Y.Z+1 (e.g., 3.0.2 → beta-3.0.3)
  • minor releases (new features): beta-X.Y+1.0 (e.g., 3.0.2 → beta-3.1.0)
  • major releases (breaking changes): beta-X+1.0.0 (e.g., 3.0.2 → beta-4.0.0)

Required Labeling System

• Mandatory labels: Issues must have one of three labels before Copilot assignment:
  • patch - for bug fixes and minor improvements
  • minor - for new features and enhancements
  • major - for breaking changes
• Pre-assignment requirement: Labels must be set before assigning any issue to Copilot

Documentation Updates

The instructions now include:

1. Repository Overview: Added branch strategy context
2. Development Workflow: New comprehensive "Branch Strategy and PR Workflow" section
3. When Making Changes: Added "Branch Targeting" as step 0 with CRITICAL emphasis
4. Clear workflow steps: 4-step process from labeling to release

Example Workflow

Issue labeled "minor" → Create/target beta-3.1.0 → Develop → Test → Merge to main

This ensures proper version management, testing in beta branches, and controlled releases to main.

Fixes #161.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.