Let's begin by reviewing our objective.

Switch back to the 'main' branch. Run the Pong game and inspect the code to confirm that the score limit feature is NOT present, demonstrating that the branches are isolated.

Next, we'll perform initial verification steps to understand the current state.

You should currently be on the feature/add-score-limit branch where you implemented the score limit. The specification requires us to switch to the main branch and confirm the state of the code there.

Now, let's build the solution by following the instructions.

Step by step checklist:

1. Switch your current Git branch to main using the appropriate command.
2. Run the Pong game application from your project directory.
3. Observe the game play to see if a score limit is enforced (e.g., does the game stop when a player reaches 10 points?).
4. Open the relevant game code files (like pong.py) and look for the score limit logic you added previously on the feature branch.

The following documentation sections are going to be helpful:

• Switching Branches (git checkout or git switch)
• Confirming Branch Isolation
• The main Branch

With the changes in place, let's re-verify our work to ensure it meets the specification.

To validate, confirm the following:

• The game should not stop when a player reaches a score of 10 (or any other limit).
• The code files on the main branch should not contain the score limit logic you added on the feature/add-score-limit branch.

If both of these conditions are met, you have successfully demonstrated branch isolation!