You are a coding agent. Your environment has a version control tool called vcs; its guide is below. You can't run anything right now. For each scenario, write the exact shell commands you would run, in order, one per line, in a code block. Describe file edits in square brackets, like `[edit src/a.ts to …]`. Then add at most one short line saying why. If the right move is to stop and tell the user something, write that as `[tell user: …]`.

Answer every scenario, using this format:

### S1
```
commands
```
why: …

Assume the project is `upstream.codes/acme/shop` and your workspace is `~/shop`, unless a scenario says otherwise.

---

S1. You fixed a typo in README.md. Get it onto main.

S2. You ran `vcs land -m "Add rate limiter"` and got exit code 3 with:
```
error: can't land rtnbkcvx: 1 file conflicts with main 48213
  src/api/limits.ts     also changed in main 48201 by @sam
main didn't change; your change is saved
next: vcs sync, fix the conflicts in those files, then vcs land
```
What do you do?

S3. 15 minutes ago src/cart.ts worked. Since then your edits broke it. Bring back that file as it was 15 minutes ago, and leave the other files alone.

S4. You just landed your change as main 48214. The user says it was wrong and wants it taken back out of main.

S5. Another agent is working in ~/shop. The user asks you to start a separate task (add product search) at the same time, without disturbing it.

S6. Yesterday you started change kpqzvmxw on your laptop. Today you're on a fresh cloud machine that has no workspace yet. Continue that change.

S7. The user asks you to make the billing/ folder visible only to the @billing group.

S8. The user says: "commit and push this".

S9. You ran `vcs land -m "Update dependencies"` and got exit code 5 with:
```
waiting    rtnbkcvx needs a person to land it (your token can't land)
asked      @alice
next: vcs status rtnbkcvx later
```
What now?

S10. Land stopped with exit code 8: a Stripe live key at src/config.ts line 12. What do you do?

S11. Your change mxwtbdqk (feature A) hasn't landed yet. You want to start feature B, which needs A's code.

S12. Show what your current change changes, and what landed on main recently.

S13. You're offline on a plane, editing files. You try `vcs land -m "Speed up search"` and get exit code 6. What do you do?

S14. Start a brand-new project in ~/tools/cli-thing on this machine. Later, put it on upstream.codes as acme/cli-thing.

S15. The user says: "stash this. I need to fix a bug on main first, then come back to what I was doing." Your current change is qwhmdzst.

S16. The user says: "throw this change away, I don't want it."

S17. You want to contribute a fix to a public project, upstream.codes/oss/parser, which you don't maintain.

S18. The user says: "pull the latest main into my workspace, I want to test with Sam's change."

S19. An hour ago your change landed as main 48190. Since then you've landed two more changes and synced. The user wants only 48190 taken back out of main.

S20. Bring the GitHub repository https://github.com/acme/legacy onto upstream.codes as acme/legacy, with its history.

---

GUIDE: