Artifacts, integrity and release preparation

Keep build evidence separate from store release confirmation.

Read the manifest

A completed build is archived with a manifest listing its files, sizes and SHA-256 hashes. Check the archive against that manifest after a handoff. A hash describes file integrity, not signing, gameplay correctness or store acceptance.

Keep the raw log

frameDock keeps raw engine output beside human-readable diagnostics. Use the original log to inspect the build failure and the missing requirement rather than treating a summarized message as the complete evidence.

Prepare a destination

Configure the publisher account, app, depots and private branch, or the corresponding itch.io destination. Review the selected artifact before uploading. A configured profile is not proof that your account is authorized.

Confirm the actual release

An upload finishing is a separate state from the intended store branch being available. Live provider uploads remain unverified in the current pilot, and console SDK packaging is not supported by this release.