When an Orbit workspace audit pauses and resumes, the final result now carries the original call's timestamp — not the resume moment. A cosmetic fix that closes the last parity gap between uninterrupted and resumed runs.
What shipped
•Instance audits that resume from a checkpoint now return the timestamp from when you originally asked, not when the resume landed. Previously a resumed audit picked up a fresh wall-clock timestamp at completion, so the same result looked slightly different depending on whether it paused — now the two are byte-for-byte equivalent.
•Added a continuation parity test suite (4 scenarios across audit, content-blocks, and performance pulls) that deep-equals resumed output against uninterrupted output. Resumed calls must be indistinguishable from clean runs; the suite locks that contract on every build.