|
| 1 | +# 260831 — bug triage round: everything the priority-70 train does not own |
| 2 | + |
| 3 | +A concurrent session owns the >=70 train (`devlog/_plan/260831_prio70_train_round2/`): |
| 4 | +issues #3071, #3032, #3026, #3029, #3008, #3019 and their PRs #3069, #3056, #3040, |
| 5 | +#3020. This unit owns the rest of the open bug surface and drives it to zero, keeping |
| 6 | +only the handful that genuinely cannot be resolved from this tree. |
| 7 | + |
| 8 | +## Frozen snapshot |
| 9 | + |
| 10 | +Taken 2026-08-31T15:45:55Z against `dev` = `b4303bb9e`. Anything opened after that |
| 11 | +timestamp is queued for the next round and does not change this round's acceptance |
| 12 | +scope. |
| 13 | + |
| 14 | +**Bug issues (11):** #3070 #3068 #3064 #3059 #3051 #3024 #3021 #2999 #2813 #1527 #1419 |
| 15 | +**Bug-labelled PRs (13):** #3078 #3067 #3066 #3063 #3053 #3052 #3041 #3039 #3038 #3034 |
| 16 | +#3003 #3000 #2989 |
| 17 | +**Also in scope, not bug-labelled:** #3030 (`chore`), carried only as a wrong-branch |
| 18 | +janitorial closure. Audit round 1 caught this misclassification; see `002`. |
| 19 | + |
| 20 | +Issue #3009 and PR #3039 are in scope. They are easy to confuse with the train's #3008 |
| 21 | +and PR #3040 — different defect, different file, different lane. |
| 22 | + |
| 23 | +## Why this roadmap is deliberately shallow |
| 24 | + |
| 25 | +The prio-70 unit wrote six diff-level decade docs before implementing anything. That |
| 26 | +worked for six deep defects. This round has twenty-five items whose correct |
| 27 | +disposition is mostly *closure*, and pre-writing a diff for an item that turns out to |
| 28 | +be already fixed is wasted precision that then has to be un-written. |
| 29 | + |
| 30 | +So this document locks only what a roadmap must lock: the scope, the cluster |
| 31 | +partition, the order, and the candidate disposition per item. **The diff-level design |
| 32 | +for each cluster is produced in that work-phase's own A phase**, against the tree as |
| 33 | +it stands when that phase starts, and recorded in the phase's own decade doc. This is |
| 34 | +an explicit, user-directed deviation from DIFFLEVEL-ROADMAP-01. |
| 35 | + |
| 36 | +## Disposition vocabulary |
| 37 | + |
| 38 | +Every item leaves this round through exactly one of: |
| 39 | + |
| 40 | +| verdict | meaning | |
| 41 | +| --- | --- | |
| 42 | +| `MERGE` | the PR is correct and complete; squash after exact-head CI | |
| 43 | +| `CHERRY_PICK` | only part of the PR is correct; take those hunks | |
| 44 | +| `REIMPLEMENT` | the diagnosis is right and the remedy is wrong; rewrite on `dev` with a red-then-green regression | |
| 45 | +| `CLOSE_FIXED` | already fixed on `dev`; cite the commit | |
| 46 | +| `CLOSE_INVALID` | the claimed code path contradicts the tree | |
| 47 | +| `CLOSE_DUPLICATE` | name the survivor | |
| 48 | +| `CLOSE_NOT_REPRO` | no reproduction is possible against current `dev` | |
| 49 | +| `UNSOLVABLE` | stays open; name exactly what external input is missing | |
| 50 | + |
| 51 | +A closure without a `file:line` or commit SHA in its comment does not count. |
| 52 | + |
| 53 | +## Work-phase map |
| 54 | + |
| 55 | +The order below is the audited order, not the original one. Audit round 1 found three |
| 56 | +file collisions the first ordering ignored, two of them with the concurrent >=70 train |
| 57 | +(`002`, findings 5-7). Train-blocked phases run late so an external dependency never |
| 58 | +stalls the round. |
| 59 | + |
| 60 | +| # | wp | cluster | items | candidate disposition | blocked by | |
| 61 | +| --- | --- | --- | --- | --- | --- | |
| 62 | +| 0 | wp0 | this roadmap + live rescan | all of scope | — | — | |
| 63 | +| 1 | wp1 | closes with no code | #3068, PR #3030 | duplicate; wrong-branch | — | |
| 64 | +| 2 | wp2 | model catalog dated variants | #3024, PR #3034, PR #3041 | widen the suffix one-way; cherry-pick the merge tests | — | |
| 65 | +| 3 | wp3 | cursor discovery transport | #3051, PR #3052 | merge after rebase | — | |
| 66 | +| 4 | wp4 | windows service and scheduler | #3064 + PR #3067, #3009 + PR #3039 | one reimplement, one merge-after-fix | — | |
| 67 | +| 5 | wp7 | residual bug PRs | PR #3078, PR #3053 | reimplement on dev; merge | #3053 needs wp2 | |
| 68 | +| 6 | wp6 | account-pool auth and quota | PR #2989, then #2999 + PR #3000, then PR #3003 | merge; portable rewrite; merge | #2999 rewrite needs #2989 first (same file); #3003 needs train #3020 | |
| 69 | +| 7 | wp5 | upstream request and compact metadata | PR #3066, then PR #3063, then PR #3038 | merge; merge; close the duplicate | #3066 and #3063 share `openai-responses.ts`, so #3066 lands first and #3063 rebases onto it. Train #3089 merged at `a0d386b49`, so the external blocker is gone (`004`) | |
| 70 | +| 8 | wp9 | residual issue fixes | #3070, #1527, #3021, #3059 | four bounded reimplementations | — | |
| 71 | +| 9 | wp8 | closeout | — | receipts, residual set, final audit | all | |
| 72 | + |
| 73 | +Each row is one full PABCD cycle. The candidate column is what this round's four |
| 74 | +read-only `xai/grok-4.6` lanes concluded; none of it is binding until that phase's own |
| 75 | +A phase confirms it against the tree as it stands then. |
| 76 | + |
| 77 | +**Every phase re-reads `gh pr diff --name-only` for its own PRs before merging, and pairs |
| 78 | +that list against every other PR it is about to touch.** #3063 grew from two files to |
| 79 | +five during wp0 and picked up two train-owned files, which moved it from wp7 to wp5 |
| 80 | +(`003`); pairing then exposed that it also collides with #3066 (`004`). A file list |
| 81 | +captured at scan time is not a fact about merge time, and neither is a blocker — train |
| 82 | +#3089 merged at `a0d386b49` while this roadmap was being audited. |
| 83 | + |
| 84 | +## Declared unsolvable |
| 85 | + |
| 86 | +#2813 (needs a live Luna Reserve account's `/v1/models` and `/api/models` dumps) and |
| 87 | +#1419 (needs macOS `.ips` crash frames on Bun 1.4.0, which the maintainer already |
| 88 | +declined to claim was fixed). Both are argued in `002`. Two of the allowed three-to-four |
| 89 | +slots are spent; the rest stay unspent until a phase earns one. |
| 90 | + |
| 91 | +## Constraints this round runs under |
| 92 | + |
| 93 | +- No local full suite. Focused `bun test tests/<file>.test.ts` or `bun run test:changed` |
| 94 | + only; whole-suite evidence comes from hosted exact-head CI or `ssh lidge`. |
| 95 | +- Every commit and push uses `--no-verify`. `dev` is protected, so every change lands |
| 96 | + through a branch and a PR, merged after exact-head CI is green. |
| 97 | +- Read-only `xai/grok-4.6` lanes, unlimited, for investigation and audit. |
| 98 | +- No file owned by the >=70 train is touched. |
| 99 | + |
| 100 | +## Terminal outcome |
| 101 | + |
| 102 | +`DONE` requires every scoped item terminal, at most four left open, each with a |
| 103 | +recorded reason. Receipts land in `070_outcome.md`. |
0 commit comments