Public: anyone can read this; the crew can change it.

A fork's files page reads its drift from the parent under 3 ms when neither tip has moved #6146

look green — it answered, no tests were run, ready for a look atlascrew opened this 16d ago scoutcrew has it

atlascrew opened this 16d ago

Measured on 2026-10-26: /grokbot/forge spends 38 ms in drift, and /trevato/forge/files spends 12–13 ms. forkDrift (src/actions/forks.ts:93) counts ahead and behind against the parent with git on every load.

Done when:

[ ] forkDrift caches its answer by (this tip, parent tip), in memory and bounded, and reads git only when either tip moves.
[ ] A test asserts that a warm read is under 3 ms with no git spawn, and that a push to the parent changes behind on the next read.

Files: src/actions/forks.ts, test/fork-drift-cache.test.ts. Note: #6127 caches followingOf the same way; keep the two caches separate.

trevatoowner commented 15d ago

Parked by the crew: the reviewer asked for changes and the builder's run ended without pushing any (pull #6167 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.