The Forensic Audit

📁 Files

src/app.ts

src/auth.ts

src/dashboard.ts

src/router.ts

A NewM Modified

JJ Log

◆ zzzzzzzz Learner 2026-06-17 08:35:07 00000000 root()

○ wrev01 Learner 2026-06-17 08:35:17 rev11111

│ Initial setup

○ wrev02 Learner 2026-06-17 08:35:27 rev22222

│ Add authentication

○ wrev03 Learner 2026-06-17 08:35:37 rev33333

│ Add routing

○ wrev04 Learner 2026-06-17 08:35:47 rev44444

│ Fix auth token

○ wrev05 Learner 2026-06-17 08:35:57 rev55555 (conflict)

│ Add dashboard (conflict)

@ wrev06 Learner 2026-06-17 08:36:07 rev66666 (empty)

│ (no description set)

JJ Graph@ wrev06

🧪 The Experiment0/5

📖 Story

You're about to try something scary with jj rebase. But here's the secret — jj remembers EVERYTHING. Every operation is recorded. Even if you mess up the graph, one command takes you back. Let's prove it.

Note your current state: jj log

You have a stack of changes. Note how they look. In the next step, you'll mess things up — don't worry, jj has your back.

● Note your current state: `jj log`

○ Do something destructive: `jj rebase -s @ -d wexp01`

○ Undo it: `jj undo`

○ View the operation log: `jj op log`

○ Redo the rebase: `jj redo`

🧩 The Forensic AuditUnsolved

📖 Story

Something broke in production. Your job is to find out what and when. You have a busy repository with many changes from multiple authors. You need to answer these questions using only jj log revsets — no scrolling through history manually: 1. Find all changes that touched src/auth.ts 2. Find any changes that currently have conflicts 3. Find all changes between main and your working copy Answer each by running the right revset. The goal is complete when all three queries return results.

Goal

jj log -r 'all()' must:

jj Terminal

🧩 Problem: The Forensic Audit

Use revsets to answer three questions about a messy repository history.

Use the terminal to solve the problem. jj log -r 'all()' will be checked automatically.