docs: handoff for the 2026-07-21/22 session (release point + method findings)#662
Closed
ligon wants to merge 1 commit into
Closed
docs: handoff for the 2026-07-21/22 session (release point + method findings)#662ligon wants to merge 1 commit into
ligon wants to merge 1 commit into
Conversation
`development` is at fb749f0, CI green, 135 commits / 45 merges ahead of `master` -- a release point. Records what landed, what is waiting on a human decision, what is still open, and the method findings. The method section is the part worth reading before dispatching agents. Every item in it made a failure look like a success at least once today: - the cache hides the bug it caused (five times; LSMS_NO_CACHE=1 is soft for script-path parquets); - WHICH CONFIG TREE you measured matters as much as the cache -- countries_root() follows the main checkout's branch, and two "bugs" reported today were master's config rather than stale data; - a negative control must actually REMOVE the change (git stash does nothing to a committed change and silently reports "no difference"); - a test that passes before AND after is not evidence; - zero can mean UNMEASURED rather than clean -- and a BROKEN KEY produces zero duplicates; - never trust a PR body's status table (three agents redid merged work); - put CONTENTS.org in the agent's BRIEF, not just in a rule it may skim. And the through-line: of seven PRs held by adversarial review, NONE had incorrect code. Every one had a false claim -- a measurement that did not reproduce, a test that discriminated nothing, a stale duplicate, a comment asserting cleanliness. That class is invisible to CI and outlives the PR. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Owner
Author
|
Closing — a handoff is a working note, not a reviewed artifact, and it does not belong in the review queue. The file now lives in the working tree at Note the TL;DR is now one step stale in a good way: it said " |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Session handoff.
developmentis at fb749f0, CI green, 135 commits / 45 merges ahead ofmaster— a release point.Covers:
LSMS_CACHE_SCHEMA4→5) and fix(#323) Site 4: the dfs: merge MANUFACTURES the duplicates — 4.9M phantom rows (UNBLOCKED: Ethiopia/Niger/Nigeria configs merged) #627 (grab_datafingerprint) had to ship together so users rebuild once;mastertoday;shockswas keyed on the panel LINE, not the household #651’sUPHIvsr_hhidgrain (a 41% change to Tanzania shock counts), and the Guinea-Bissaudf_geohook;3488b791cleared those cells;The method section is the part worth reading before dispatching agents. Each item made a failure look like a success at least once today, and the through-line is this: of seven PRs held by adversarial review, none had incorrect code. Every one had a false claim — a measurement that did not reproduce, a test that discriminated nothing, a stale duplicate, a comment asserting cleanliness. That class is invisible to CI and outlives the PR that introduced it.
Docs only.