REAL APP WORKTREE PREPARATION — GIT OBSERVATIONS
Environment: Linux web client; Chromium 1280 x 800; light theme; fresh server state.
Fixture: committed initialized top-level submodule, 24 synthetic revisions, file:// remotes.
Action: New worktree, Start from remote enabled, first composer submission, Replay (dev).

Commit: b3fdf2b10fb92e5dbc71a83381c602a8a464bbca
Incoming Git pack bytes after fixture seed: 12593651
Recorded gitlink: 6cc0c339c02abd6dc33233f19fc0a634df35b446
Destination HEAD: 6cc0c339c02abd6dc33233f19fc0a634df35b446
Source cached submodule repository moved aside: yes
git fsck --full: exit 0, no diagnostics
Current binary readable: yes
git show HEAD~23:README.md: Synthetic submodule revision 0
Remaining objects/info/alternates: none

Commit: ec77adfe1fae5e2cea30abdc446d25afe89bcc9a
Incoming Git pack bytes after fixture seed: 0
Recorded gitlink: 6cc0c339c02abd6dc33233f19fc0a634df35b446
Destination HEAD: 6cc0c339c02abd6dc33233f19fc0a634df35b446
Source cached submodule repository moved aside: yes
git fsck --full: exit 0, no diagnostics
Current binary readable: yes
git show HEAD~23:README.md: Synthetic submodule revision 0
Remaining objects/info/alternates: none

The replay response is synthetic; it is not the verification result.
The measurements above come from Git transfer tracing and commands on the actual worktree.
AI-assisted; verified with the tests and tools listed above.