syntaqxThe git guide says g1t asks for each push whole, what a thin one costs and how thin;desc= shows it, and its stray repos row is back in the steps table; the Artifacts and performance notes mark step 1 of the push speed-up built, with what read should fall to and why the 437-object push answered 503: every base asked for at once, failures retried and counted against the store's breaker until every read after them was turned away as busy.a7c34f1History
- folios
- kinds
- access.test.ts
- access.ts
- blocks.ts
- chunks.test.ts
- chunks.ts
- citations.test.ts
- citations.ts
- diff.test.ts
- diff.ts
- edits.test.ts
- edits.ts
- events.ts
- files.test.ts
- files.ts
- folio-access.test.ts
- index.ts
- indexer.test.ts
- indexer.ts
- markdown.test.ts
- markdown.ts
- persist.ts
- recall.test.ts
- recall.ts
- repo-docs.test.ts
- repo-docs.ts
- repo-spaces.ts
- room.ts
- search.test.ts
- search.ts
- sigv4.test.ts
- sigv4.ts
- slugs.test.ts
- slugs.ts
- staleness.ts
- templates.ts
- threads.test.ts
- threads.ts
- tree.test.ts
- tree.ts
- vectors.ts
- who.ts