Document beta branch workflow

[howarewoo]

Goal

Keep main as the primary stable branch while routing development through protected beta and reserving release merges for the repository owner.

Summary

• document stable installation from main and beta installation from beta
• make beta the required base for ordinary development PRs
• allow only release promotion PRs from beta into main through the required verify check
• document that only the owner may merge beta into main
• document the owner's review bypass on beta and required owner approval for contributors
• target future npm and GitHub Actions Dependabot updates at beta
• explain the single active service/extension constraint
• pin the v0.1.0 installation command to its release tag

Verification

• actionlint .github/workflows/ci.yml .github/workflows/dependency-review.yml
• git diff --check
• cloned main and beta with the documented branch commands and observed the expected branches
• cloned v0.1.0 with the documented release command and observed the tagged commit
• GitHub default branch read back as main; Graphite trunk read back as beta
• main ruleset read back with an update restriction and only the Admin role bypass
• sole repository administrator read back as howarewoo
• beta protection read back with admin bypass and one owner code-review requirement for contributors
• existing Dependabot PRs chore(deps): bump actions/setup-node from 5 to 7 #216–chore(deps): bump fastify from 5.10.0 to 5.12.1 #223 retargeted to beta

[howarewoo]

• Document beta branch workflow #226 👈 (View in Graphite)
• beta

This stack of pull requests is managed by Graphite. Learn more about stacking.