Outcome#
You can make one bounded change manually, inspect it, verify it, commit it with a Conventional Commit, publish it, and inspect the resulting practice pull request.
Concept#
Agents and IDE buttons are safer after you understand the underlying branch, working tree, staged diff, commit, remote branch, and review boundary.
Worked Example#
The personal practice PR contains only the intended file, a Conventional Commit, and an honest verification record.
A correct example uses these decisions:
- Which PR do you create manually in this mission? The personal practice PR shown by the mission.
- What must happen immediately before committing? Inspect git diff --cached and confirm every staged change.
Common Trap#
Using the background transport PR as the exercise, or staging every file with git add . before reviewing status.
If Blocked#
Do not use git reset --hard, broad deletion, or force push as a first repair.
Preserve git status, the current branch, and the diff, then use the
first safe PR lab recovery section or ask
for help through the non-secret dashboard issue form.
Useful references:
Understand Before Accepting AI Output#
This mission is deliberately manual. An agent may explain a Git concept but must not perform the change, invent test output, or choose files to stage.