[BC-INTEGRATION-04] Publish an immutable integration-ready BuildCompiler release

[Gonza10V]

Notion task: https://app.notion.com/p/39f1a3339dcb816da7fff7a83c7ca169
Parent epic: #111
Notion program: https://app.notion.com/p/39f1a3339dcb818ea29eec44007d8e6e
Temporary ID: BC-04
Release: R2 Planning Preview
Dependencies: BC-01, BC-02, BC-03
Codex-ready: yes after dependencies are satisfied

Goal

Document the clean token-based server workflow and publish/tag an immutable version SynBioSuite can pin.

Expected files/modules

• pyproject.toml
• README.md
• RELEASE_CHECKLIST.md
• .github/workflows/python-publish.yml
• notebooks/buildcompiler_synbiohub_authenticated_tutorial.ipynb

Scope

• Update tutorial to obtain a token outside BuildCompiler and construct the clean API.
• Correct package/release metadata and PyPI target references.
• Document core versus automation extras.
• Run release checklist and create an immutable tag/release.

Non-goals

• Do not publish from an unreviewed branch.
• Do not require automation extras for the core release.

Acceptance criteria

• SynBioSuite can install a specific immutable version/tag.
• Tutorial exercises the clean API and matches current signatures.
• Release metadata names synbio-buildcompiler consistently.
• Release notes describe contract version and known limits.

Verification

• Build wheel/sdist and install into a clean environment.
• Run core CI and documentation build.

Risks and review

• Risk tags: cross-repo-contract, optional-dependency
• Human checkpoint required: yes
• Treat AI-generated changes as unreviewed until tests and human review pass.

Codex handoff

Implement as one focused PR. Begin by verifying dependencies and current repository state. Preserve unrelated work. Report implemented behavior, tests, commands, assumptions, and blockers.