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
…ng (#70) * fix(release): use portable python resolver in release scripts * fix(release): auto-insert missing docs version markers during packaging
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hotfix Pull Request
This PR backmerges
mainintodevelopto synchronize release and pipeline fixes after v2.9.2.Summary
Backmerge
mainintodevelopso release hardening changes and post-release fixes become the new integration baseline.Incident Reference
Post-release branch drift after v2.9.2 publication and subsequent release tooling fixes.
Why This Hotfix Is Needed
maincontains release process fixes that must be present indevelopto prevent recurrence of packaging/version-marker failures and Windows execution friction.Root Cause Summary
Multiple release fixes landed on
mainafter publication, butdevelopadvanced independently; without a backmerge, branch drift remains and can reintroduce release-process instability.Scope of This Fix
mainintodevelop.TDD & Verification
main -> developsync PR before this change.origin/main...origin/develop = 6 19.Risk Assessment
Rollback Plan (Mandatory)
If regression is detected on
develop, revert the merge commit from this PR and reopen a narrowed sync PR.Post-Deploy Verification
develop.git rev-list --left-right --count origin/main...origin/develop.Follow-up Required?
No immediate follow-up expected beyond standard post-merge sync verification.