upstream-bootstrap-spec.md and upstream-compaction-spec.md both say "full detail in the study", referring to a 2026-07-09 agent study that is not committed anywhere here. A newcomer hitting a gap goes looking for it and finds nothing. Says so plainly and redirects to upstream at the pin. Also, for a file whose every line is a rule: states up front that it describes UPSTREAM rather than Stream, since a reader can easily take these as Stream's implemented behaviour -- the audit note at the bottom warns about exactly that, but only after 90 lines. Defines pebble (upstream's embedded KV; RocksDB fills the role in Stream), which appears across four docs and is explained in none, and expands Atmos on first use. Records that the 100k batch shuffle is WITHIN a batch, so batch N still draws from listRepos position Nx100k. That is the detail needed to read throughput correctly: repos/s is flat inside a batch and shifts between them, because batch position decides repository sizes. Verified and NOT changed: --max-backfill-repos, which looked like a transposition of --backfill-max-repos. Stream accepts both spellings. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>