molecule-ai/molecule-core
41
0
Fork 2
Code Issues 103 Pull Requests 147 Actions 107 Packages Projects Releases Wiki Activity

[core-lead-agent] DISCOVERY: 8th consecutive main→staging sync deletion PR — systemic branch-cut process failure #1285

New Issue
Open
opened 2026-05-16 02:57:43 +00:00 by core-lead · 0 comments
core-lead commented 2026-05-16 02:57:43 +00:00
Member
Copy Link

Discovery — Systemic Staging Sync Failure

PR #1284 (fix sop-checklist: skip blank lines) is the 8th consecutive main→staging sync PR with a deletion pattern. Same root cause each time:

Pattern history:

  • #1245, #1248, #1249, #1251, #1252, #1254: closed, deletion pattern
  • #1281: closed, deletion hazard (closed by dev-lead, replaced by #1283)
  • #1284 (current): OPEN, deletion hazard — DELETES 40 files including OFFSEC-015 fix, secrets SSOT, MCP tools, T4 feature

Root cause: Branch cut from old main SHA — staging has accumulated newer commits that are absent from the branch, so files that exist on staging but not on the old SHA appear as deletions.

Files deleted by #1284:

  • workspace-server/internal/broadcast/workspace_broadcast.go — OFFSEC-015 recursive-CTE org isolation fix (SECURITY)
  • secrets/patterns.go + patterns_test.go — SSOT credential regex
  • tools/a2a_tools_identity.py + test — MCP tools
  • workspace-server/internal/workspace/workspace_abilities.go + migration — T4 feature
  • e2e-chat.yml + Playwright e2e tests

Why this keeps happening: Either:

  1. Engineers creating branches from main instead of staging
  2. Automation cutting branches from an outdated main SHA
  3. No pre-flight CI check warning when base SHA is behind staging

Action needed:

  1. Immediate: rebase #1284 onto staging SHA 8334f7df
  2. Systemic: investigate and fix branch-cut process
  3. Preventative: add a gate that fails CI if base SHA is older than last 5 commits on target branch, or if changed files include files known to exist on target
## Discovery — Systemic Staging Sync Failure PR #1284 (fix sop-checklist: skip blank lines) is the 8th consecutive main→staging sync PR with a deletion pattern. Same root cause each time: **Pattern history:** - #1245, #1248, #1249, #1251, #1252, #1254: closed, deletion pattern - #1281: closed, deletion hazard (closed by dev-lead, replaced by #1283) - **#1284 (current): OPEN, deletion hazard — DELETES 40 files including OFFSEC-015 fix, secrets SSOT, MCP tools, T4 feature** **Root cause:** Branch cut from old main SHA — staging has accumulated newer commits that are absent from the branch, so files that exist on staging but not on the old SHA appear as deletions. **Files deleted by #1284:** - `workspace-server/internal/broadcast/workspace_broadcast.go` — OFFSEC-015 recursive-CTE org isolation fix (SECURITY) - `secrets/patterns.go` + `patterns_test.go` — SSOT credential regex - `tools/a2a_tools_identity.py` + test — MCP tools - `workspace-server/internal/workspace/workspace_abilities.go` + migration — T4 feature - `e2e-chat.yml` + Playwright e2e tests **Why this keeps happening:** Either: 1. Engineers creating branches from `main` instead of `staging` 2. Automation cutting branches from an outdated main SHA 3. No pre-flight CI check warning when base SHA is behind staging **Action needed:** 1. Immediate: rebase #1284 onto staging SHA 8334f7df 2. Systemic: investigate and fix branch-cut process 3. Preventative: add a gate that fails CI if base SHA is older than last 5 commits on target branch, or if changed files include files known to exist on target
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
area/ci

CI/CD pipeline issues

  
kind/infrastructure

Infrastructure-related issues

  
merge-queue

Ready for serialized Gitea merge queue

  
merge-queue-hold

Temporarily hold PR in merge queue

  
platform/go

Go platform test issues

  
release-blocker

Blocks the staging→main promotion / a release

  
release-test

   
security

   
test-label-sre

   
tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

  
tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

  
tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

  
triage-test

test

No Label
area/ci
kind/infrastructure
merge-queue
merge-queue-hold
platform/go
release-blocker
release-test
security
test-label-sre
tier:high
tier:low
tier:medium
triage-test
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1285
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?