I read this as a read-only QA investigation - I’ll verify the sealed profile, run only focused local tests, inspect the runtime-facing clone, and report whether the prior receipt error can recur.


I found the active worktree is dirty and not byte-identical to r16, so I’m isolating the sealed r16 runtime and test fixtures in tmpfs rather than exercising any live-facing path.


I identified the complete sealed-controller support tree and will rerun the requested suites only against a tmpfs composition: r16’s installed wheels plus its overlay and baseline test harness, with no service unit invocation.


I isolated the V14 failure to the staged child smoke process lacking its source gateway module; the migration suite is clean, and I’m correcting only that test harness dependency before the final V14 run.


I read the repeated V14 failures as an unresolved isolated-runtime mismatch, not a product result; I’m capturing the child smoke error directly so the final status is evidence-based.


type: cancelled

previous_status: running

reason: r16 was rejected; fresh r17 audit replaces it