Update code sync procedure with clearer steps

[shenkeyao]

Closes https://app.asana.com/1/1208976916964769/project/1209976130071762/task/1214168385664108?focus=true.

This PR:

• Updates branch naming procedures for upstreams.

[claude]

Claude finished @shenkeyao's task in 44s —— View job

---

Review: Update code sync procedure with clearer steps

• Gather context and read changed files
• Review PR diff against base branch
• Check for existing review comments (none found)
• Provide review feedback

Review Summary

This is a clean documentation improvement to espresso/docs/README_ESPRESSO_CODE_SYNC_PROCEDURE.md. The changes are consistent and well-structured. LGTM.

What changed: The PR clarifies the branch naming convention across three sync sections (Kona Fork, Celo-Kona Fork, and Succinct) by:

1. Clearer branch naming rule — The old wording ("where y is the commit on Celo's branch") was ambiguous about how to derive y. The new wording ("if the default branch is espresso-integration-x, create espresso-integration-y where y = x + 1") makes the sequential increment explicit.

2. Consistent cherry-pick descriptions — References to "original ... branch espresso-integration-x" are replaced with "default ... fork branch", which is cleaner since espresso-integration-x is already defined in the preceding bullet and used in the git commands below.

3. Trailing whitespace cleanup — Minor whitespace fix at line 261.

All three sync sections (1.1, 1.2, 1.3) are updated with the same pattern, keeping the document internally consistent. The git commands themselves are unchanged and still correctly reference espresso-integration-x and espresso-integration-y as defined by the surrounding prose. No issues found.

[gemini-code-assist]

Code Review

This pull request updates the code sync procedure documentation to standardize branching and cherry-picking instructions across Kona, Celo-Kona, and Succinct repositories, introducing an incremental versioning scheme for integration branches. The review feedback identifies several opportunities to improve consistency by updating the terminology and repository overview sections to match these changes, and suggests more precise wording for cherry-picking steps to clarify that commits are moved onto the new integration branches.