2 Commits

Include renames

Author	SHA1	Message	Date
Vito	5ded3cfd39	test(history): prove bounded close with events, not wall-clock bounds (#261) ... The real-clock subtest of the bounded-close test asserted close(0.02) returned in under 0.2 s; a slow macOS runner took 0.26 s. The failed subtest then skipped its release and join, so its worker stayed blocked holding a charge on the process-wide SHARED_CONTEXT_BUDGET, and the next subtest saw 621 != 0. Not a production race: close(2) only returns True once the worker has exited and released its leases. Prove boundedness with events instead: close() must return False while the in-flight write is still blocked (it has not left its fake write). Keep the exact upper bound only under the manual clock, where it is deterministic. Release and join each subtest's worker in a finally so a failure cannot leak a charge into the next subtest. The commit-gate test gets the same treatment: submit() and close(0) must return before the blocked invalidation and commit finish, instead of a 0.1 s bound.	2026-10-20 18:01:34 -07:00
Vito	4ef236aaf7	feat(history): persist exact run output references (#214) ... * feat(history): define bounded output reference contracts * feat(database): migrate execution output evidence to schema v3 * feat(history): persist immutable run output references * test(history): isolate mocked node gallery monitor * feat(history): capture bounded output descriptors with shared leases * fix(history): authenticate payload owners and release failed captures * feat(history): attach output evidence to exact finalized attempts * test(history): verify run output evidence on real ComfyUI * fix(history): release idle worker payload references * docs(history): clarify defensive lease cleanup * test(history): align output fixtures with native path styles * test(history): separate restore completion from writer drain * test(history): bound batch drains by progress and total time	2026-10-17 23:26:37 -07:00