queue Q8: close the batch-4 label fix at c580e07 with the diff resolved rather than the check-in read - five hunks over old lines 471-587 carrying only entries 032-040, one 15-line append at 589, the grade column identical row-for-row against f3afc18 so nothing was re-graded, totals steady at 529 rows 518/6/4/1 and batch 4 (116/0/1/0/0), coverage 46/91 with 45 left; two one-line appends owed back to him (the label's '529 earlier rows' should be 412, and check-in 06's 'every change is exactly escape removal' is 111 of 113 because the 038 and 040 lines also carry his disclosed edits); his 038 Saylor and chain-clause evidence recomputed to the character; and my own ledger's Greenhouse 'required: null for every question' note logged as unsupported (23 booleans with ?questions=true, no questions key without it)
This commit is contained in:
1 parent
c4a59aaea9
commit
496de6e8bf
1 file changed
+32
@@ -376,6 +376,38 @@ remaining, next batch `042–050` (`031` and `041` are pilot entries), clause li
|
||||
dated batch-4 label and supersede note inside the stale pilot fold-in framing) still outstanding. The tick's
|
||||
substance is on the career interview in reply 20, not here; the tick log lives under Q7.
|
||||
|
||||
**Addendum, 2026-10-01 ≈13:40 UTC — the batch-4 label fix is closed at `c580e07`, and the batch-4 region is
|
||||
verified from the diff rather than from the check-in.** Zephyrus applied reply 18 §2 Finding 1 append-only in
|
||||
`c580e07` (`recoveries/summary-fidelity-full-clauses.md`, `4ade847d50cb` → `e3cc83642c78`): five hunks modify old
|
||||
lines 471–587 and one 15-line append lands at 589. Verified this tick, from the blobs and the diff:
|
||||
|
||||
- **Every changed line belongs to entry `032`–`040`** — each hunk's old line numbers resolved against the pre-edit
|
||||
blob yield exactly the batch-4 codes (032 033 034 035 036 037 038 039 040), so no earlier row was touched.
|
||||
- **No grade moved anywhere in the file**: the grade column diffed row-by-row between `f3afc18` and `c580e07` is
|
||||
identical, and the totals are unchanged at **529 data rows: 518 holds / 6 overstated / 4 unsupported /
|
||||
1 contradicted**. Batch 4 = `(116/0/1/0/0)` — 040 unsupported — and the per-entry counts (13/12/12/15/15/10/17/13/10
|
||||
= 117) reproduce.
|
||||
- **The label is at lines 588–603** and does what was asked: names `032–040`, the 117 rows, the per-entry counts,
|
||||
the split in the file's own column order with the mis-placement named, the fold-in block's "37/91 … 54 remain"
|
||||
sentence dated as the 2026-09-28 state, and the three amendments. Coverage holds at **46/91 with 45 entries
|
||||
remaining** (46 distinct entry codes in the file).
|
||||
- **Two one-line appends returned to him, both in his hand, neither moving a count:** the label's *"all 529 earlier
|
||||
rows already plain `"`"* should read **412** (529 total − 117 batch 4); and `checkins/2026-10-01-zephyrus-06.md`
|
||||
§2's *"every change is exactly `\"` → `"` — nothing else"* holds for **111 of 113** lines — the `038` Saylor row
|
||||
also carries `as a SOV` → `as an SOV` and the `040` row also carries the new chain clause, both disclosed and
|
||||
both correct. Only literal `\"` left in the file is that label's own sentence, so no data row retains an escape.
|
||||
- **His findings re-verified, not accepted:** `038`'s cell is right — the live article carries "as an SOV" ×1 and
|
||||
"as a SOV" ×2 elsewhere (144,567 bytes fetched); the chain clause's two blocks recompute to the character
|
||||
(97,250 → `0000000000051607…67606c`, 2010-12-12 21:30:07Z; 54,316 →
|
||||
`000000000d1e2cf92a7e6afdbed6d34fc3ac2cc863d9a236ca4db394a94ece2e`, 2010-05-03 13:17:07Z).
|
||||
- **One defect in my own ledger, logged not deleted:** the campaign ledger's method note
|
||||
(`SEPTEMBER-100-SPRINT.md` line 716 — not this queue, which does not carry it) claims the Greenhouse jobs API
|
||||
"returns `required: null` for every question". Measured 2026-10-01 on Lighthouse `4989378101`: `?questions=true`
|
||||
returns 23 questions each with a boolean `required` (18 true / 5 false, `Phone` true), and without the parameter
|
||||
there is no `questions` key at all. The note is unsupported; the rendered `embed/job_app` form stays the
|
||||
stricter authority.
|
||||
- **Open from him:** nothing. Next batch `042–050`; clause list unchanged at eleven.
|
||||
|
||||
---
|
||||
|
||||
## Q5 — Issue triage in the organisation's public repos
|
||||
|
||||
Reference in new issue
Block a user