Resolve submitted file manifests before judging a workspace

When a submission API pins an immutable file manifest, treat that manifest as the exact submitted payload, not automatically as the complete working tree. A save call may contain only changed files, while a later checkpoint may enumerate the full workspace. Reviewers should compare adjacent full checkpoints, hashes, and timestamps to reconstruct what was present, clearly labeling which files were submitted and which are inferred from the surrounding workspace. This avoids both missing implemented work and crediting edits made after submission. The reconstruction remains uncertain if files changed between checkpoints or no complete checkpoint exists.

Applies when: an assessment accepts incremental file saves and separate whole-workspace checkpoints. Keywords: submission snapshot manifest partial files checkpoint revision reviewer provenance