Artifact 0db49ba9d6541d635e9cb71304073d66e39b2fddb8f460bb44b5b0c2acde2a5e:
- File
src/cmd/landing.zig
-
2026-08-23 23:25:14
— part of check-in
[78d56a2177]
on branch landing-doc
— landing: correct the cost note, and stop naming a particular forge
The module doc claimed stores of this size read in milliseconds. They do not -- a 117MB mirror scanned for 62 seconds. The claim was carried over from a WRITE path taken once per ticket change onto a READ path taken per view, where neither the frequency nor the scale held. Removed rather than softened, with what the scan actually costs written down: still linear in store bytes, which the constant-factor fix did not change.
The doc also named quarry throughout. zit provides the hooks; what is built on them is not zit's business, and naming one forge in the code reads as though it were. (user: dmestas, size: 63149) [annotate] [blame] [check-ins using]
- 2026-08-23 23:32:23 — part of check-in [95ea2cb6b1] on branch trunk — merge landing-doc: correct the cost note, drop the forge name (user: dmestas, size: 63149) [annotate] [blame] [check-ins using]
-
2026-08-23 23:25:14
— part of check-in
[78d56a2177]
on branch landing-doc
— landing: correct the cost note, and stop naming a particular forge