ccb-githublisted

# CCB GitHub Release Maintainer ## Core Rule Treat GitHub as the user-facing product page. A release is not done until local version files, both READMEs, changelog, GitHub Release, release assets, 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. ## 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. 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 when package contents changed and the user asked for a release. 8. Create or update the GitHub Release page. 9. Wait for required GitHub Actions and release assets. 10. Run the published checker and report the result. Keep the checker read-only. Git writes, GitHub Release writes, workflow reruns, and tag operations are explicit agent actions done in the sequence above, not hidden inside the checker. ## Quick Audit From the CCB repo root, run the bundled checker before and after release work: ```bash CHECKER="dev_tools/skills/ccb-github/scri