reap.py --quiet-for: 30 minutes before a live session counts archived? nf-fnp ← Beads

Twinned from https://github.com/cfsh/ninefold/issues/652 by tools/beads/import_github.py's reconcile pass.

./tools/office/reap.py (PR #647) refuses to reap a session whose transcript was touched inside --quiet-for. Too low and it can take a session that is merely between turns — measured, two were reapable on every GitHub proof seven minutes after merging, mid-wrap-up. Too high and a finished box waits before it can be tidied.

Live data from nf-dev-sg: the four hand-reaped sessions had been silent for *hours*, and a working session's transcript is touched every few seconds — so anything from 10 to 60 minutes would have been right that day.

• A — 30 minutes. ⭐ Recommended default, shipping now. Wide margin over the seconds-scale write cadence; a box is tidyable half an hour after its last session finishes.
• B — 10 minutes. Faster turnaround, still ~100× the observed write gap.
• C — 60 minutes. Most conservative; a CTO tick an hour after the archive still reaps.

One number: QUIET_FOR_DEFAULT in tools/nflib/sessions.py. --quiet-for N overrides it per run either way.

Default ships if unanswered — nothing is blocked on this.