Dev GitHub Workflows

This section is the control map for GitHub Actions entrypoints in bijux-core. Use it to identify which workflow owns a failure, release gate, or automation path before debugging jobs directly in CI logs.

Pages In This Section

• ci
• deploy-docs
• release-crates
• release-pypi
• release-github
• bijux-canon

Workflow Ownership Map

Workflow	Owns	Enter Here When
ci	Repository validation gates and baseline verification	pull request checks fail or mandatory CI signals regress
deploy-docs	Documentation publishing and site deployment flow	docs site output, publish triggers, or deploy permissions fail
release-crates	Rust crate release orchestration	crates release process, publish ordering, or registry upload issues appear
release-pypi	Python release orchestration	PyPI publication, packaging metadata, or python release gates fail
release-github	GitHub release record and release artifacts	release notes, release tagging, or artifact publication on GitHub breaks
bijux-canon	Cross-repo canon integration workflow	canon handoff integration or shared validation contracts fail

Navigation Rule

Start with workflow ownership first, then inspect job-level behavior. If a failure spans multiple workflows, treat it as a contract boundary issue rather than patching one workflow in isolation.

Stability

Keep this section aligned with workflow files in .github/workflows/ and update ownership notes whenever trigger conditions or release responsibilities change.