Plan Every Code default branch and release identity

[cbusillo]

Objective

Plan and execute the branch/release identity transition for Every Code after product docs and import policy are aligned.

Finish Line

The path from local/cbusillo-overlay to main and GitHub-release-only publishing is documented and ready to execute.

Current Status

State: Waiting
Next action: Audit workflow/default-branch references and draft the wave-two branch rename plan.
Blocked by: #86
Waiting for: Product identity docs/import policy to land first so the branch rename has coherent terminology.
Last verified: 2026-05-16 strategy discussion.

Scope

• In: default branch rename from local/cbusillo-overlay to main, workflow branch references, release tag wording, GitHub metadata, and post-rename validation.
• Out: npm publishing/package rename for now; code architecture changes.

Acceptance Criteria

• All references to local/cbusillo-overlay are audited before rename.
• Workflows and branch protection/default-branch metadata are updated together.
• GitHub Releases are documented as sufficient distribution for now.
• Old branch name is retired or redirected with clear guidance.
• Post-rename gh/Actions/default-branch checks pass.

Relationships

Parent: #85
Blocked by: #86

Validation

Use rg local/cbusillo-overlay, gh workflow list --all, GitHub default branch metadata, and post-rename PR/Actions checks.

Decisions

• Branch rename is wave two, not the first docs PR.
• Publishing outside GitHub Releases is intentionally deferred.

Open Questions

• Rename the existing branch in place, or create main from it and retire the old branch after validation?