Documented runs with public evidence. These are not benchmarks and ticks are not treated as proof; each receipt separates the agent's work from the owner's review and links to the permanent result.
One AdaptTable contract ran for 45 elapsed hours, survived a Claude Code → Cursor handoff, and finished as a human-reviewed 67-commit PR spanning six roadmap phases and 57 closed issues.
Use this receipt to understand what durable on-disk state makes possible when a shift outlives one conversation, one allowance and one coding agent.
Nine focused items landed in four hours as unsquashed per-item commits, closed four issues on merge, and shipped AdaptTable v1.2.0 to npm the same day.
Use this receipt as the smaller model for a first attended or overnight shift.
The plugin's own build sessions used an enforced punch list, conventional item commits and the same stop gate it gives users.
An 11-item Codex maintenance shift stayed on one branch, passed the repository gates and became Nightshift v0.9.2.
Use the bad-night template for an interrupted, stalled, owner-stopped or incorrectly completed run. Good and bad nights are both useful when facts, interpretation and public evidence remain separate.
Share a public receipt on #22. The contribution map lists the disclosure checks for run receipts.