Track every Mortal Shell II missable before it disappears.

Open the attributed trophy record before entering the encounter or transition named by the requirement. Confirm that the source date and evidence label match the route you intend to follow, then leave the target incomplete until the action is visible in the game. A missable label from one captured roadmap is a warning to prepare; it is not independent proof that every release build has the same lockout.

Export the companion profile and create a game-save backup through the platform as two separate actions. The JSON export preserves this site's route and target states. It contains no game inventory, checkpoint, platform trophy, or save file. Only the platform's save process can protect gameplay progress. Name the artifacts clearly so restoring the checklist is never mistaken for restoring the encounter.

During the attempt, solve the specific requirement rather than every nearby optional task. If the game confirms the condition, update the shared trophy target and check that the walkthrough and tracker reflect the same state. If the condition is uncertain, keep it open. A percentage below one hundred is more accurate than a manual check added only to make the route appear complete.

If the opportunity is missed, record what happened before restoring anything. Note the game build, route point, source used, and whether the platform already synchronized the save. This helps distinguish a misunderstood requirement from a version change or known issue. Do not present a single failed attempt as proof that the captured source is wrong for every player.

Before NG+ or another irreversible transition, filter the tracker to incomplete trophy and story targets, review the known-issues page, and repeat the backup check. Optional skips must remain different from confirmed completion. The final receipt should show which missables were verified, which were deliberately skipped, and which still need a source or release-version review.

The closeout record needs four separate answers: whether the requirement appeared, whether the action was performed, whether the game or platform confirmed the result, and whether the local target was updated. Keep an unknown answer open instead of collapsing it into failure or completion. If a backup is restored, record which artifact was restored and whether cloud synchronization occurred before the attempt. Then recheck the exact target rather than assuming adjacent progress survived. This separation prevents a checklist export, save backup, platform trophy, and in-game state from being treated as interchangeable proof.