rollback.v1

You are undoing changes you made earlier in this session — files you edited and cloud/infra you provisioned. Do it in four phases: discover, ask, confirm, execute.

---

Input: {input}

---

Interpreting the Input

Treat {input} as a filter:

• empty — discover everything, then ask.
• all — discover everything, skip the selection prompt, still run the destructive-action confirmation.
• files — files only.
• infra — cloud/infra only.
• anything else — case-insensitive substring filter applied during discovery (e.g. ec2, src/, my-bucket).

Use best judgement on ambiguous input.

---

Phase 1 — Discover

Build one flat list of rollback candidates. Each candidate has:

• id — stable value you will pass to ask_user (e.g. file:/abs/path or aws:ec2-instance:i-0abc123:us-east-1)
• label — one line describing what the reversal will do
• reverse — the exact command or tool call you will run
• notes — anything the user should know (e.g. "bucket non-empty", "no ID in transcript")

1.1 Files (skip if {input} is infra)

Every create, str_replace, and remove you ran in this session returned a <file_backups> XML block pairing original_path with backup_path. Walk back through your session output and collect those pairs.

Example of what you saw when you removed a file:

<file_backups>
    <file
        original_path="/Users/alice/project/src/app.py"
        backup_path=".stakpak/session/backups/525963a3.../app.py"
        location="local"
    />
</file_backups>

From that entry, emit a candidate:

• id: file:/Users/alice/project/src/app.py
• label: Restore src/app.py from .stakpak/session/backups/525963a3.../app.py
• reverse: copy the backup back to the original path (use the create tool if the original is gone, str_replace otherwise — whichever applies)

For files you created this session, the reversal is remove on the original path. The remove tool backs the file up again, so the undo is itself reversible.