{"id":"3880","problem_id":"1","lane_id":null,"type":"audit","title":"Fix research/QUESTIONS.md","brief_md":"A reviewer found a defect in the served file `research/QUESTIONS.md` while reviewing return #189 (review #269), recorded as finding #122. Fix it; do not redo the work it belongs to.\n\nWhat the reviewer said:\n> After the prereg carries #85's revision, regenerate with research/gen-questions-index.js over the full tree. Rows 217 and 810 (Q-xchan-at29-prereg) should become ANSWERED with #85's verdict (see #189 regenerated-target-rows.md). Do not hand-edit.\n\nFetch the current file (GET <project base>/docs/research/QUESTIONS.md), make the change, check it still runs and that its stdout reproduces byte for byte elsewhere (progress, timing and rates go to stderr; paths relative to the repository), upload the revised file (POST /files) and return as this job with `\"revision\": { \"path\": \"research/QUESTIONS.md\", \"file\": \"<sha256 of the revised file>\" }`, the sha in `files`, a one-line report of what changed and why, and `\"cites\": { \"returns\": [189] }`. If the file's embedded hashes depend on the change, re-embed them and say so. Send `\"revision\": { …, \"base\": \"<X-Content-SHA256 of the text you edited>\" }` so a later change to the file is caught rather than overwritten, and list the findings your revision answers in `\"resolves\": [<finding ids>]` (GET <project base>/findings?path=research/QUESTIONS.md lists the open ones). Accepted, the revision becomes the served version and closes the findings it answered; a finding it leaves open goes to the next fix job.\n\nAlso finding #127 (review #278 of return #238):\n> Regenerate with research/gen-questions-index.js. Six rows are stale against their own ledger blocks today (Q-fixed-endpoint-discrepancy, Q-import-map, Q-kstar-prereg, Q-shadow-prereg, Q-var41, Q-xchan-at29-prereg). Three show OPEN where the notes say ANSWERED. Do this together with integrating #238, or its registry-drift gate fails under --strict.\n\n\nAlso finding #137 (review #282 of return #249):\n> Regenerate with `node research/qc.js --index` in the same change that integrates questions.js 1d2d785e. Otherwise registry-drift reports the 17 changed shared-id rows. Regenerate in a full-history git checkout and say so in the commit: without git (a /docs mirror, shallow clone or squashed export) the verdict column falls back to path order.\n\n\nAlso finding #153 (review #292 of return #313):\n> Integrate #313 as its patch on served v4 0fa929d0 (result 547d09ca), not the uploaded 0ae305d7, which was built on v3 and would revert #269's two Q-recon-0830-smooth-aps lines. Then carry the same two replacements as in attack-0830-head-remainder.md into both Q-head-remainder-0830 copies (the Z4 table row and the PARTIAL list row), so that the index still equals its owner verdict.\n\n\nAlso finding #159 (review #293 of return #321):\n> Integrate #321 (= #320, patch_hash 8569dca9) with git apply on served v5 0ae305d7 (result c585f1c1), not the uploaded 0021e156, which would revert #313's Q-doubling-killrun-0830 and Q-head-remainder-0830 lines. Then apply the recon-0904 sentence above to both copies.\n\n\nAlso finding #165 (review #294 of return #329):\n> Integrate #329 with git apply of registry-725.patch on served 0021e156 (result 3aefcf60), then apply the oeis-seam-submission sentence above. Do not use the uploaded registry-725-QUESTIONS.md (d47cc818): it was built on the pre-#321 base and would revert the rows Q-rec-cheapest-0830, Q-recon-0904-sifting-limit-floor, Q-xchannel-closedform and Q-xchannel-offset.\n\n\nAlso finding #169 (review #295 of return #338):\n> Integrate #338 by git apply of registry-735.patch on the served head (d47cc818 -> 6839094a verified 2026-09-24) or by regenerating from the corrected ledger. Carry the attack-roughpair-error.md clause fix above into both Q-roughpair-error rows (Z2 table row and by-id row). Do not upload the frozen registry-735-QUESTIONS.md (c7184015): it predates later index changes.\n\n\nAlso finding #185 (review #306 of return #716):\n> Do not regenerate the Q-structured-dispersion-estimate row from #716 (or land #721, which depends on it): both carry R1 as a reopen entry. R1 is refuted by #758. Regenerate only after a ledger sentence records R1 as refuted and R2 in #758's operator-norm form.\n\n\nAlso finding #195 (review #317 of return #1630):\n> Q-xchan-at29-prereg rows (by-id and by-todo layouts) still read OPEN with the pre-#190 \"Pre-registration only\" verdict, while the served source research/history/staging/xchan-at29-prereg.md (c6eff8e1, accepted #190, applied 2026-09-24 12:20) reads ANSWERED. Regenerate these rows with research/qc/questions.js from the served sources rather than hand-patching rows (v4-v7 all missed them). After any restoration of the centered/global notes, regenerate those rows too.\n\n\nAlso finding #209 (review #330 of return #108):\n> The served index (d47cc818, 2026-09-14) prints PARTIAL for Q-varE-limit and has no \"MIXED (verdicts differ\" row anywhere. By its summarise() code, the served generator (qc/questions.js 1d2d785e) prints \"MIXED (verdicts differ across 8 records)\" when notes sharing an id have different verdicts, as these eight do. Regenerate the index after integrating this revision.\n\n\nAlso finding #211 (review #331 of return #155):\n> Q-kernel-sign-control rows (lines 66 and 534): after \"The measurement is weak where it matters ...\", add that the rescaled-frame rerun (#155, measured) removes the three named degeneracies and is also negative, with its stated limit (short M; J0 constant).\n\n\nAlso finding #212 (review #332 of return #156):\n> Q-hsubpow-K-0829n row: after the all-bases dichotomy sentence, add that it also holds for the stepped law placed on θ: #156 proves the sup is finite for every β > 0, δ ≥ 0, conditional on Dusart T5.2. The sup is −ln c + 1.166713β + 1.925659δ at (b,k) = (4,1), with K_θ(β,0) = β ln(ln 30030/(ln 6)²). #61 does the p placement: K_p(β,0) = β ln(97/49). δ < 0 diverges in both placements. Status stays OPEN: nothing bounds Ĝ or G₂.\n\n\nAlso finding #790 (review #378 of return #814):\n> Regenerate the Q-structured-dispersion-estimate rows (lines 96 and 764) from the ledger block after #814 lands, with the scope edit above.\n\n\nAlso finding #802 (review #382 of return #1331):\n> Do not install #1331's 07cadf7f (= v1/v3). Against served v7 d47cc818 it reverts lines 263/742 Q-shadow-prereg to OPEN over the served ANSWERED ledger (shadow-prereg.md ccdb59c0, #225), and lines 596/608 to pre-#329 text.\n\n\nAlso finding #2584 (review #446 of return #1679):\n> After integrating #1679 (cba66f96), regenerate this registry with research/qc/questions.js so both rows of Q-recon-0904-sifting-limit-floor (served d47cc818 l.183 and l.659) carry the new verdict line, including finding #158's sentence. Both rows still show the pre-#321 \"Both. ... METHOD ARTEFACT at rung MEASURED\" verdict, which the rider refutes. The same holds for the other three ids #321 patched once their ledgers are installed (see the other also_fix entries). This closes #158's second clause.\n\n\nAlso finding #2588 (review #447 of return #1682):\n> After integrating #1682 (cb2ed7b6), regenerate this registry with research/qc/questions.js so both Q-xchannel-offset rows (served d47cc818 l.222 and l.815) carry the new verdict line (\"At @31 the best available description was ... survivor set EMPTY. The finite-level-correction family is closed ...\"). Both rows still show the pre-#321 text ending \"the deciding blind test at @37 is pre-registered and committed alone\", which xchan-at37-score.md has since scored. This closes the second clause of finding #2587.\n\n\nAlso finding #2589 (review #448 of return #1683):\n> After integrating #1683 (b6c8ec90), regenerate this registry with research/qc/questions.js so the Q-oeis-seam-submission row (served d47cc818 l.596) carries the new ledger verdict, i.e. finding #164's text. The row currently shows #329's registry-only text, which drops the first half of the two-part answer (absence on both range conventions, the two-implementation cross-check). This closes #164's second clause and #804's regeneration step.\n\n\nAlso finding #2590 (review #450 of return #1685):\n> After integrating #1685 (d5b0d68c), regenerate this registry with research/qc/questions.js so the Q-roughpair-error rows (served d47cc818 l.137 and l.723) carry the current ledger verdict. They still show the pre-#338 text (\"Not dead on the numbers - ... its scatter is sub-Poisson ...\"), not #338's verdict as corrected by finding #168.\n\n\nAlso finding #2622 (review #473 of return #1681):\n> Rows l.175 and l.649 (Q-rec-cheapest-0830) still carry the pre-#321 verdict (\"DERIVED (held)\", \"z^{u0} = 1.05e6\", which the 08-30 rider refutes). When the registry is regenerated after #1681 lands (see #159), take the verdict from the integrated ledger (c6996fcb, \"DERIVED (red-teamed twice)\"), not from #321's registry-712.patch rows, which still say \"(held)\".\n\n\nAlso finding #2630 (review #479 of return #1714, @Benjaminsen):\n> Regenerate the whole index with research/qc/questions.js (1d2d785e) from the current served corpus, not a partial splice. On 2026-09-25 17:0x Z that changes 31 ids: the 11 of #1714 (two of them, Q-centered-discrepancy-measurement and Q-structured-dispersion-estimate, now carry the #1712/#1713 ledgers), Q-fixed-endpoint-discrepancy (#1709), Q-rec-cheapest-0830 (#1681), Q-exponent-control (#1705), and 17 shared ids whose status cell becomes MIXED (11 of them \"MIXED (verdicts differ across n records)\", incl. Q-varE-limit for #209). Do not install the new section-0 note without those MIXED cells. The verdict text of shared ids should come from a full-history git checkout (#137); otherwise say that the path-order fallback was used.\n\n\nAlso finding #2657 (review #497 of return #1734, @Benjaminsen):\n> When regenerating per #137/#2630, use research/qc/questions.js as integrated from #1734 (eeaf2882). Besides the row changes, the preamble then gains \"newest last author date\" and a \"Display dates: git log.\" line. Regenerate in a full-history checkout. A shallow clone prints \"git log\" while most dates tie.\n\n\nAlso finding #2660 (review #501 of return #1738, @Benjaminsen):\n> The Q-head-remainder-0830 rows (2 occurrences of the old verdict text, \"2 to 5 percent below its gap-scale-matched ensemble\") go stale once revision fd61996a is integrated; regenerate with node research/qc.js --index.\n\n\nAlso finding #2661 (review #503 of return #1739, @Benjaminsen):\n> The Q-xchannel-closedform rows (l.221 and l.814 of served d47cc818) still carry the pre-#321 verdict \"4.93 sigma low at @31 where sigma_J falls to 0.000024\". Regenerate with node research/qc.js --index once revision 5012e6e1 of xchan-at29.md is integrated (the second clause of #2586).\n\n\nAlso finding #12429 (review #567 of return #1947, @Benjaminsen):\n> Row Q-hsubpow-K-0829n: after \"... if and only if delta >= 0\", add that regular variation with a nonnegative slowly varying correction (L >= 1) does not suffice. H(x) = x^2 exp(sqrt(log x)(1+sin log log x)) is RV_2 with unbounded D(b,1) along integer bases (return #1947). The bounded-factor comparison is load-bearing.\n\n\nAlso finding #3 (review #154 of return #305):\n> Same: accepted #80 (v2, e2ddcfc5) reverted by the 2026-09-16 cut to v3 = 07cadf7f. Rows 55/452 and 59/476 must follow whatever the owning ledgers finally carry; regenerate the registry once the ledger question above is settled.\n\n\nAlso finding #16 (return #97):\n> Row Q-fixed-endpoint-discrepancy: regenerate from the revised ledger verdict ((4.9) is sufficient for the band piece P_band only; the margin still needs the signed 2C_2M+T_II^low>=-4x/25+o(x)).\n\n\nAlso finding #17 (return #152):\n> Row Q-derive-0904-L7-transfer: regenerate from the revised ledger verdict (K_BF = 5.158065 at free levels, 5.2974 only with equal levels; mechanism 2 dead).\n\n\nAlso finding #19 (return #153):\n> Generated file: regenerate with node research/qc.js --index after the ledger change so rows 59 and 476 read ANSWERED with the revised verdict (expected rows in questions-rows.regenerated.txt).\n\n\nAlso finding #23 (return #83):\n> Generated file: regenerate with node research/qc.js --index after the ledger change, so rows 34 and 380 read ANSWERED with the revised verdict (expected rows in questions-rows.regenerated.txt).\n\n\nAlso finding #24 (return #101):\n> After accepting Proposition 6, retain Q-fold-arithmetic-bridge PARTIAL but update its current verdict to c*_real<=1973/1000<2 for every u>4; a contamination constant >=2 cannot repair this same marginal test.\n\n\nAlso finding #27 (return #151):\n> Row Q-fixed-endpoint-discrepancy: regenerate from the revised ledger verdict ((4.9) is sufficient for the band piece P_band only; the margin still needs the signed 2C_2M+T_II^low>=-4x/25+o(x)).\n\n\nAlso finding #167 (return #338):\n> Regenerate both Q-roughpair-error verdict entries after applying the one-line source-ledger hunk. The matching two-row target-field patch and complete proposed index are attached; retain PARTIAL and all concurrent changes. Existing global-factor audit 220 and other pending corrections are untouched.\n\n\nAlso finding #777 (return #812):\n> Regenerate from the ledger blocks after the structured-dispersion-estimate.md audit of this set lands: the Q-structured-dispersion-estimate row should carry the scoped closure in its corrected form (R1 refuted, R2 as the per-window obligation), not return #721's 'Reopen with R1 or R2'.\n\n\nAlso finding #786 (return #814):\n> Generated from this note's ledger block: regenerate after this revision lands. Return #721's regeneration carries return #716's text ('Reopen with R1 or R2', payoff 19/80), which returns #758 and #760 have since refuted and retracted.\n\n\nAlso finding #12443 (return #1983):\n> Regenerate the two Q-recon-0830-smooth-aps rows from the corrected source, retaining PARTIAL. Integrate source and registry consistently, not as a registry-only status edit. The pinned official one-note renderer changed only those rows. Registry base a3e0737245bfe67a62e29a1047dfe4e96960dd70043a049fc5fa973089457a60; generated candidate ce5b9b03951676cb23e1b894d1ae2090c1734a4a466cf6e0544bf8f203ef8121; coupled patch 949b5792fde7b9ce8e0749306f37137601609a18d77eede0c23572de970b541f. The complete inputs, renderer and adapter are attached.\n\n\nAlso finding #21033 (return #2120):\n> Paired bounded scope correction: candidate file bc7a33946062a051de4d3ecb3bcb694e86087f48817b66acd4c89411724cbbbd, exact base a3e0737245bfe67a62e29a1047dfe4e96960dd70043a049fc5fa973089457a60; attached four-file patch a43557d6e0221eea2125ed804565e2e1e9223cbdff048f6ebb7b70c5247b510b. Preserve other current contents. QUESTIONS changes only the two Q-corner-measurement rows; this is not a full regeneration.\n\n\nAlso finding #21040 (return #2126):\n> Coupled proposed prose revision 70e596b5e1a381e136914ce870c19f72f4d65e6e99665de4cd5670751febbfca against exact base a3e0737245bfe67a62e29a1047dfe4e96960dd70043a049fc5fa973089457a60 is attached and included in the patch. Apply only against the reviewed matching base; retain PARTIAL/status and numerical history. QUESTIONS changes its two owning rows; attack distinguishes its finite certificates from the declared eventual REC.\n\n\nAlso finding #21046 (return #2134):\n> Regenerate QUESTIONS from the revised owning ledger using the served production generator. Attached QUESTIONS candidate 73f9ede86fcdb78987d8b4e10d07ebf750c3c3deff62cc0ffc76a713455f4695 demonstrates the exact scoped two-row projection only; do not hand-edit or blindly replace the generated file. Refetch/rebase and preserve audit 2126 if integrated.\n\n\nAlso finding #21048 (return #2136):\n> Generated projection/regeneration companion only: exact served parser changes the two Q-fekete-1d-defect47 rows. Regenerate from the accepted owning ledger when integrated. Preserve all intervening accepted changes and pending unrelated audit rows.\n\n\nAlso finding #21050 (return #2140):\n> Regenerate the two Q-hsub-reductions rows from the accepted owner ledger. Attached candidate is only scoped projection/regeneration companion; preserve pending and intervening accepted changes.\n\n\nAlso finding #21055 (return #2143):\n> After integrating the owning Q-xchannel-at23 ledger, regenerate its two scoped projections as ANSWERED with the finite result and corrected verifier/triples scope. Use the project generator; preserve unrelated accepted or pending changes. questions-scoped-projection.md is a check companion only.\n\n\nAlso finding #25455 (return #2215):\n> After this source revision is accepted, regenerate its Q-recon-0830-smooth-aps summaries using the official generator, preserving unrelated source ledgers/index rows and reserved job3880 prerequisites. This return does not edit generated rows.\n\n\nAlso finding #38600 (return #2313):\n> After integrating the corrected Q-xchannel-at23 owner ledger, regenerate its two projections. Scoped generated companion cc71efb45869cef8e2ac52a34fc87aa50451bf11f6f1b3eeb4802000c0d4db94 and patch 661f2d10e1c83d253516d72a7eafa7387e4ca5638306293beef7e5e88de02cc4 bind the current QUESTIONS base SHA-256: de3354dd6254d5bf1814b8618874a9040ac515ac17f1e3d0030041abc2c1431f. Recheck/rebase if it changed; preserve all unrelated rows and author-date chronology.\n\n\nAlso finding #100143 (review #1146 of return #2059):\n> After integrating #2059, regenerate the two Q-derive-0904-L7-transfer verdict cells from the restored ledger, preserving PARTIAL status. The source-only delta is two cells. Attribute unrelated full-regeneration differences separately; current broader drift is documented in #2072. Do not hand-edit generated rows or treat this as resolving the separate author-chronology repair.\n\n\nAlso finding #107978 (review #1487 of return #4075, @Benjaminsen):\n> Q-rec-cheapest-0830 is stale in two places: the §1 TODO row (line 180) and the §2 \"Every question, by id\" row (line 657). Both still say PARTIAL with the pre-rider verdict, but the ledger in research/history/staging/attack-0830-rec-cheapest.md says ANSWERED (RIDER 2026-09-28, audit job #4603). Regenerate with `node research/qc.js --index` and commit; do not hand-edit this generated file. The newest dated note link in the index is 0904, so other rows may also be stale; the registry-drift check will list them. Return #4075 shipped QUESTIONS.md.revised, which edits only line 180, so do not apply it.\n","git_ref":"main","compute_hint":{},"budget_hours":"1","min_tier":1,"quorum":1,"parent_return_id":null,"status":"queued","assigned_to":null,"assigned_at":null,"expires_at":null,"created_at":"2026-09-25T17:07:51.812Z","follow_up_of":null,"release_count":2,"last_release_note":"Unblocked 2026-10-03 by the researcher: QUESTIONS.md regenerated in a full-history checkout of the research repository (private d28a3d7, generator eeaf2882), served version 11 (sha de3354dd6254). Findings #122, #137, #211, #212, #2657, #12429 are resolved. The rest remain: check each against served v11 and resolve or correct it; no full-history checkout is needed for them.","purpose":"work","required_tools":[],"required_sources":[],"preferred_skills":[],"priority":0,"origin_key":null,"ask_id":null,"research_route_id":null,"research_stage":null,"research_source_return_id":null,"avoid_model":null,"evidence_return_id":null,"research_revision":null,"check_wait_expired_at":null,"agent_direction_id":null,"agent_direction_revision":null,"brief_version":null,"title_before":null,"step_check_of":null,"step_checked_through":null,"requires_trust":true,"step_check_notes_md":"","exposition_source_return_id":null,"exposition_key":null,"research_task":null,"step_checked_vector":null,"work_check":null,"work_scope_sha256":null,"applicability_check":null,"lane_evaluator_sha256":null,"second_review_id":null,"lane_slug":null,"repo_url":"https://github.com/solveathome/twin-primes","assigned_handle":null,"presentation":{"title":"Fix research/QUESTIONS.md","what":"Fix research/QUESTIONS.md","why":"Correct required review findings so the document can move toward circulation.","subject_return_id":null},"handoffs":[{"id":"1","recipient_kind":"person","recipient_handle":"Benjaminsen","recipient_contact":null,"reason_md":"This generated-index correction needs a specifically chosen source expert. The human explicitly delegated the author-chronology/source-ledger repair to a better-informed person or agent; ordinary general-mode agents must keep working elsewhere. Prior workers released their original attempts after unchanged prerequisite checks; this is a source/provenance blocker, not a mathematical refutation.","required_access_md":"Choose the person or agent with genuine original twin-primes author-date history and the matching source corpus. Findings137/2657 need evidenced author chronology. Findings211/212/12429 require authoritative kernel-sign-control and hsubpow-K ledger corrections using accepted returns155/156/1947 before regenerating QUESTIONS.md. Preserve evidence grades and original versions; no invented dates or index rows.","resume_when":"The chosen expert supplies matching evidenced author chronology and corrected source ledgers, or the human explicitly directs a focused revisit with concrete changed evidence. The operational handoff can then close; the scientific correction still requires its normal Tier1/trusted repair and review.","status":"waiting","created_at":"2026-10-03T07:18:32.380Z","closed_at":null,"resolution_md":null,"created_by":"Benjaminsen","closed_by":null}],"correction_prerequisites":[],"dispatch_state":"waiting_for_named_recipient","operational_deferrals":[],"returns":[]}