Change 33454
ReleaseProcessOverview.md: fix Step 20's wrong cd path and add explicit -t binary+F to prevent a real mistyping bug.
Found by actually executing Step 20: the doc said 'cd $WSRoot/tools' but
downloads/ is at the stream root, not inside tools/ -- an easy mistake
since Step 19 leaves you sitting in tools/. Following that wrong path led
to a real, non-obvious failure mode: 'p4 add' against a not-yet-existing
destination silently falls back to guessing filetype 'text' instead of
failing loudly, and correcting the path afterward does NOT fix the
already-wrong type on the pending add. Both submitted tarball/zip files
had to be fixed post-hoc with 'p4 edit -t binary+F' (change 33453,
content verified via md5 as never actually corrupted, only the stored
type was wrong). Now the doc's own command passes -t binary+F explicitly
so this can't recur silently.
Agent: Claude Code, Model: Claude Sonnet 5 (claude-sonnet-5), operating as bot_Claude_Anthropic.
Found by actually executing Step 20: the doc said 'cd $WSRoot/tools' but
downloads/ is at the stream root, not inside tools/ -- an easy mistake
since Step 19 leaves you sitting in tools/. Following that wrong path led
to a real, non-obvious failure mode: 'p4 add' against a not-yet-existing
destination silently falls back to guessing filetype 'text' instead of
failing loudly, and correcting the path afterward does NOT fix the
already-wrong type on the pending add. Both submitted tarball/zip files
had to be fixed post-hoc with 'p4 edit -t binary+F' (change 33453,
content verified via md5 as never actually corrupted, only the stored
type was wrong). Now the doc's own command passes -t binary+F explicitly
so this can't recur silently.
Agent: Claude Code, Model: Claude Sonnet 5 (claude-sonnet-5), operating as bot_Claude_Anthropic.