What "undo" actually means when the target is a real repo, not a fixture

Description and use

Demonstration that the gx tool can perform a four‑stage walk (break, prove, restore, verify) on a real left‑pad repository, restoring the original state and completing within 30 seconds.

Problem

Validate that the gx tool can perform a four‑stage walk (break, prove, restore, verify) on a real public git repository within a 30‑second budget, ensuring the change and undo are correctly recorded and verified.

Outcome

All three runs succeeded: git four‑stage time 2.454–2.662s, fs four‑stage 2.321–2.441s, total incl. clone 5.706–6.057s, all under the 30‑second budget.

Workflow

• Clone left‑pad at commit 2fca615
• Run gx four‑stage walk on git substrate: break (commit), prove, restore (undo), verify
• Run gx four‑stage walk on fs substrate: break (file rewrite), prove, restore (undo), verify
• Record timings and receipts for each stage
• Verify that all stages succeed and total time <30s

Evidence

T_git_four_stages=2.662 ... T_fs_four_stages=2.441 ... T_total_incl_clone=6.057 FAILURES=0 P4_RESULT=PASS

Source

Worst single observation across all three runs was 6.057 seconds against a 30-second budget

Source

We ran the checks that matter for the claim above and stopped there. Here's what's still open

Source