Repository navigation
Published branches: review 14 superseded candidates and their unique history #302
Description
The owners should decide which work and history from these older candidates still needs retention. All 14 refs have commits outside the audited develop history and have no current open PR head or target role. Several have replacement implementations or later history anchors, so exact ancestry and content adoption need separate decisions.
Snapshot: 8 October 2026, 17:09 UTC. GitHub listed 131 published branches and 21 open PRs. The audit checked exact commit ancestry and tree objects. develop was d430a133; main was 57eb7798.
This issue covers published GitHub refs. Existing product issues retain their implementation and acceptance work. Branch retirement requires the owner's agreement under AGENTS.md. Recheck the live head before acting on a row.
The commit counts below measure original history outside develop. They do not measure the amount of useful code still missing.
| Published branch | Exact head | Tree object | Commits outside develop | Decision or evidence |
|---|---|---|---|---|
cursor/071-release-queue-c457 |
424acd3d | 74042a8a0cdaad4fcb401fd1d2a5acc8221c76f2 |
1 | PR #63 closure records replacement by #140 and transfer of status to issues. Reconcile any remaining work and decide original history. |
cursor/cloud-env-setup-af9e |
cb80aab5 | 980bf7b97ebd5e82e138c5d25d02d4c5548981da |
1 | PR #21 closure records refreshed setup notes. Confirm current guidance and decide original history; the replacement commit is also outside develop. |
docs/weekly-2026-09-25 |
27036f26 | 33247a2a78809338aa9936939bfb6e29e24b8130 |
8 | Contains the exact feat/0.7-product-documentation tip. Keep this protecting ref until both report and documentation history decisions are complete. |
docs/weekly-2026-10-02 |
5af632b0 | f8ba62f9211d57d77638b3984fc5715e3a366ba6 |
2 | Decide whether the historical report needs a retained GitHub ref; current work stays in issues. |
feat/0.7-product-documentation |
19bb7a90 | 460ca4389cff5f66ddafc18cc26ce03ff7700b25 |
6 | Exact tip is contained by docs/weekly-2026-09-25. Review useful documentation and preserve that protecting history before retiring an intermediate label. |
feat/0.7.2-ci-installed-journeys |
136f66da | d5aab9e1b69548a8ede2adefe6a6c7318dbb139f |
16 | PR #152 closure replaces this candidate with #153. Current #153 head is 3495ddf; #150 owns remaining acceptance. |
feat/assistant-modes-in-sidebar |
2d062ff9 | da0d4e7342aeb8818c4c7d0909dc8dbd1607278c |
4 | PR #65 closure records adoption. Three patches match exactly; the fourth differs in test context. Verify behavior and decide original history. |
feat/protected-content-atomic-cutover |
25ab205e | 8778f7a79c322f481880a3a8569a451aa560ce84 |
2 | PR #59 closure points to #203. This exact tip is contained by followup and listing-buy. |
feat/protected-content-0.7.1-followup |
43585914 | 6828fa7053e36c7ad097325597023e36674810e5 |
8 | PR #62 closure points to #204/#205. Exact tip is contained by listing-buy. |
feat/protected-content-listing-buy |
d181ffd2 | 67b50eed95f593a99dcfd3b8bdd89edfae37d9cb |
11 | PR #70 closure points to #206. This is the final history anchor for the older stack; keep pending disposition. |
fix/0.7.3-complete-release |
66331ea0 | dcd5161b0fe0ea6eb92f38517836f30412301a10 |
1 | PR #161 closure points to merged #244/#246. Verify adoption and decide original history. |
fix/0.7.3-update-admission |
c278540e | 6b39162dae3c09a7895f160cf37cbf8156f41bd2 |
2 | PR #160 closure points to merged #248. Verify adoption and decide original history. |
fix/167-installed-home-proof |
3add99b7 | 5b79da5fd41055329fa7431af3798973389fee1d |
6 | Compare with #167/#170 and later installed CI proof. Source history alone does not settle installed acceptance. |
fix/alignment-two-platform-installer |
7285cba1 | 233191a6b03cdbba92fb506cbd0d6378ebd850c8 |
1 | PR #69 closure points to 0947d02. Confirm the current installer under #88 and decide original history. |
Three exact history relationships allow intermediate labels to be considered after the final anchor is retained:
feat/0.7-product-documentationis an ancestor ofdocs/weekly-2026-09-25(exact comparison).feat/protected-content-atomic-cutoveris an ancestor offeat/protected-content-0.7.1-followup(exact comparison).- Both older protected-content tips are ancestors of
feat/protected-content-listing-buy(followup comparison).
Confirm these relationships with git merge-base --is-ancestor <listed-head> <protecting-head> before any retirement. A later replacement PR can carry equivalent content while leaving the original history outside the canonical line.
For each decision, record the live head, tree, branch owner, related issue or PR, and reason. Retained refs need a review or cleanup condition. Retirement needs owner agreement and an exact protecting GitHub ref, or an explicit decision to release unique history. A matching tree or adopted patch alone does not preserve the original commit history.
Completion criteria:
- For each candidate, identify the current replacement, remaining useful work, and original-history disposition.
- Record source comparisons and relevant acceptance evidence in the existing owning issue.
- Retain the final protecting refs until each intermediate-ref decision is approved.
- Each owner approves keep, transfer/review, preserve history, or retire, with a reason and review/cleanup condition.
- Complete approved retirements or link the existing issue that owns the remaining work.
CI implementation stays in #194/#150. Protected-content implementation and installed acceptance stay in #91 and #44-#47. Release and installer work stay in #93/#88. #167 is a historical implementation record; #170 and the current installed-proof tasks retain their open acceptance.
The full published audit covers 131 refs, with each ref listed in one group: #300 (73 integrated refs), #301 (7 legacy review refs), #302 (14 superseded candidates), #303 (9 research refs), #304 (28 canonical, active and context refs). Counts describe the snapshot above; refresh them when GitHub changes.
Activity