ccb-github

# CCB GitHub Release Maintainer ## Core Rule Treat GitHub as the user-facing product page. A release is not done until local version files, npm package metadata, both READMEs, changelog, GitHub Release, release assets, npm registry state, and Actions status all agree. GitHub's repository homepage renders README from the default branch, not from the latest release tag. If release documentation is prepared on a feature or hotfix branch, merge that branch to the default branch before calling the homepage updated. Use repository `SeemSeam/claude_codex_bridge` unless the user explicitly gives a different repo. For CCB releases, npm publishing is part of the release surface by default. If `package.json`, npm wrapper scripts, README npm install snippets, or `.github/workflows/npm-publish.yml` are missing or stale during release preparation, create or repair them before the release commit and before creating or pushing the release tag. Do not create a tag first and add npm publish support in a later branch commit. ## Execution Contract When the user asks for a final release or homepage result, do the git/GitHub work instead of only describing it: 1. Make the file edits, including npm package/workflow/docs auto-completion for release work. 2. Run the local checks. 3. Commit the changes. 4. Push the working branch. 5. Merge to the default branch when README/GitHub homepage state must change. 6. Push the default branch. 7. Create/push the release tag only after the intended rele...