docs(gap-baseline): retract false main-history-splice claim (shallow-clone artifact)

[seonghobae]

Retraction

This PR originally claimed main's history was spliced onto new roots around 2026-08-20/21, based on 15 PRs (later 16, plus 2 more queued) all hitting fatal: refusing to merge unrelated histories. That claim was wrong.

Root cause: the local .github checkout in the analysis sandbox was a shallow git clone (git rev-parse --is-shallow-repository → true). A shallow clone's truncation-boundary commits present as disjoint history roots (git rev-list --max-parents=0 lists them as fake roots), and git merge from inside a shallow checkout genuinely raises fatal: refusing to merge unrelated histories even when the real, full history is a single connected line — this is real, documented git behavior for shallow clones, which is exactly why it read as convincing evidence of an actual split.

After git fetch --unshallow origin: origin/main has exactly one root commit (0c6e99ed0acab17b1cdd9f853a8398ddb0eed269), and 731af58e (originally claimed "not reachable from current main at all") is a completely normal ancestor.

A Devin Review comment on this PR directly disputed the original claim ("All 15 listed heads share a merge base with current main, and 731af58e is its ancestor") and asked for reproducible evidence — that's what prompted the re-check that found the shallow clone. Thank you for catching this.

Corrective actions taken

• Retraction comments posted on all 16 PRs that received the false triage guidance (the original 15, plus fix(scheduler): fall back to REST when auto-rebase GraphQL transport fails #1065 from a second triage pass).
• The second triage pass (which was actively applying the same false diagnosis to more PRs) was stopped before it posted beyond fix(pip-audit): keep index-url locks hashed and reject symlink parents #1051 (already covered) and fix(scheduler): fall back to REST when auto-rebase GraphQL transport fails #1065; two more (feat(integration): add ecosystem capability catalogue #1147, fix(strix): bind evidence to exact workflow artifacts #1009) were queued but never posted.
• No merges, pushes, or branch rewrites were ever made on the basis of the false diagnosis — the recommended remediation was comment-only by design, which limited the damage to incorrect guidance rather than lost work.
• docs/product-technical-gap-baseline.md's entry has been rewritten in place to record the retraction, the real root cause, and a standing lesson: always check git rev-parse --is-shallow-repository (and git fetch --unshallow if true) before diagnosing any multi-root or "unrelated histories" condition on any repo in this ecosystem.

Verification

• pytest tests/test_product_technical_gap_baseline.py -q → 5 passed.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 42 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 82cf20ca-099c-47ac-9621-19a9dac58bfe

📥 Commits

Reviewing files that changed from the base of the PR and between 8c08583 and ce4fad9.

📒 Files selected for processing (1)

• docs/product-technical-gap-baseline.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}