Packaging cook result needs follow-up

The latest recorded Windows packaging attempt completed a substantial cook pass but did not produce a successful build.

The commandlet ran for roughly thirteen minutes and reached the cook and derived-data statistics. The log recorded package, shader, material, mesh, texture, animation, and audio work before reporting that the cook was done.

The recorded result

Despite reaching those statistics, the Unreal commandlet exited with code 1. AutomationTool then exited with code 25 and reported Error_UnknownCookFailure, followed by the final PackagingResults: Error: Unknown Cook Failure message.

That output establishes the result, but not the underlying exception. The log points to the fuller AutomationTool trace for the missing detail, so the next production pass needs to diagnose that trace rather than treating the completed asset statistics as a successful package.

The packaging path remains part of the vertical-slice work. It needs to prove that the hub and explicitly cooked maps can load, levels can be completed, and saved progression survives in a packaged build—not only in the editor.