456c4c43e7
Break the stage+commit window into sub-phases (FAT working-tree walk vs object writes) via `commit split —` log lines, and add two micro-benchmarks (sd_bench for SD/FAT primitive ops, git_bench for libgit2 object overhead) with justfile recipes. Documents the walk-vs-writes cost model in tradeoff-curves/sync-commit-staging.md to decide whether explicit-path staging over the editor's dirty set is worth replacing add_all(["*"]).
Tradeoff curves
Where a design knob has a cost that bends — energy, latency, memory — against an interval or size, the curve and its knee live here, so the chosen default is traceable to a shape rather than a guess.
Docs index:
../README.md. Project overview:../../README.md.
| Curve | What it decides |
|---|---|
wifi-auto-sync.md |
auto_sync interval vs Wi-Fi energy (a 1/T hyperbola) — why the default is 10 min and opportunistic, not a wall-clock timer. |
epd-refresh-latency.md |
E-ink refresh latency vs rows driven — the full / full-area-partial / windowed-Y cost model behind typing responsiveness and the boot splash→editor swap. |
sync-commit-staging.md |
Commit-staging strategy vs working-tree size — add_all(["*"]) (O(tree) FAT walk) vs explicit-path (O(churn)); the walk-vs-writes split that decides whether explicit staging is worth it. |