Conversation
merge develop into main (#61) * ci: add separate main-to-develop backmerge workflow for non-hotfix merges * ci: handle fork develop branch names in backmerge sync guard * docs: refresh release docs metadata, module paths, and Claude integration link * docs(deploy): restore CLAUDE_CODE_WHITELIST.md at canonical path * docs(reference): add API_REFERENCE.md compatibility shim * docs(reference): mirror full api-reference content to API_REFERENCE.md * governance: establish two-repo public promotion contract and automation * governance: transition to single-repo public release model * docs(reference): convert API_REFERENCE.md to compatibility stub * docs(reference): remove API_REFERENCE.md and normalize canonical API links * chore: sync develop into main (docs + release governance updates) (#53) (#54) * ci: add separate main-to-develop backmerge workflow for non-hotfix merges * ci: handle fork develop branch names in backmerge sync guard * docs: refresh release docs metadata, module paths, and Claude integration link * docs(deploy): restore CLAUDE_CODE_WHITELIST.md at canonical path * docs(reference): add API_REFERENCE.md compatibility shim * docs(reference): mirror full api-reference content to API_REFERENCE.md * governance: establish two-repo public promotion contract and automation * governance: transition to single-repo public release model * docs(reference): convert API_REFERENCE.md to compatibility stub * docs(reference): remove API_REFERENCE.md and normalize canonical API links * docs(quickstart): prioritize project-local usage and separate contributor clone path * docs: add agent onboarding snippets and align discovery contract * feat(skills): ship official task-orchestrator skill package * fix(release): include agent skill package in public subset allowlist
release docs gate
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fde50a94e0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| LICENSE | ||
| CONTRIBUTING.md | ||
| tm | ||
| README.md |
There was a problem hiding this comment.
Every allowlist entry is now indented, but read_allowlist (scripts/public-repo-sync.sh, line 76) does not trim whitespace before building "$SOURCE_DIR/$rel"; this makes the sync/check logic look for filenames like " README.md" that do not exist. In the build-public-subset workflow (.github/workflows/build-public-subset.yml), that causes scripts/public-repo-sync.sh to fail with MISSING_SOURCE for essentially all entries.
Useful? React with 👍 / 👎.
| # Canonical public release subset contract (single-repo model). | ||
| # Paths are relative to repository root. | ||
| # Canonical public release subset contract (single-repo | ||
| model). |
There was a problem hiding this comment.
This wrapped comment continuation is missing #, so it is parsed as a required path (model).), and the same file also includes stray EOF/quit tokens later; scripts/public-repo-sync.sh will treat each as an allowlisted file and fail with missing-source/drift errors. That breaks public subset sync/check runs even when all real project files are present.
Useful? React with 👍 / 👎.
1 participant
Hotfix Pull Request
? This template is for urgent production fixes only.
Use this only when:
Incident Reference
Root Cause Summary
Brief explanation of what caused the issue.
Scope of This Fix
What exactly is being changed?
Explicitly confirm:
TDD & Verification
If a regression test could NOT be added, explain why:
Risk Assessment
Risk notes:
Rollback Plan (Mandatory)
If deployment fails, we will:
Post-Deploy Verification
After deployment, verify:
Follow-Up Required?
Does this hotfix require:
If yes, link follow-up issue(s):