diff --git a/docs/screenshots/issue-64/press-1440x900-no-js.png b/docs/screenshots/issue-64/press-1440x900-no-js.png
new file mode 100644
index 000000000..2ecac69ed
Binary files /dev/null and b/docs/screenshots/issue-64/press-1440x900-no-js.png differ
diff --git a/docs/screenshots/issue-64/press-390x844-no-js.png b/docs/screenshots/issue-64/press-390x844-no-js.png
new file mode 100644
index 000000000..349a2ea84
Binary files /dev/null and b/docs/screenshots/issue-64/press-390x844-no-js.png differ
diff --git a/site/index.html b/site/index.html
index 6554d38f6..09ba3f775 100644
--- a/site/index.html
+++ b/site/index.html
@@ -66,7 +66,183 @@
Your issues go to press overnight.
-
+
+
+
+
+
How a Run works
+
One issue in, one pull request out.
+
A Run feeds one issue through four units and delivers a pull request that is ready for review. Units 2 and 3 are one agent session. Under each unit are the lines thirdshift printed on stderr during a real Run: issue #24, which produced pull request #25.
+
+
+
+
+
+
+
+
+
1 · C · Prepare
+
Pre-flight checks the Origin match, that the issue is open and that git has a name and email to commit with. thirdshift then picks the Issue branch, fresh or a Continuation, and creates a worktree next to your clone. Pre-flight prints nothing when it passes, so the first line is the worktree.
+
+
thirdshift: creating worktree /home/jacob/repos/thirdshift-issue-24 on issue-24 from origin/main
+
+
+
+
2 · M · Implement
+
A headless Claude Code session, with the Factory skills loaded, implements the issue in the worktree, test-first where it can, and commits.
+
implement
tdd
+
+
thirdshift: logging the session to /home/jacob/.thirdshift/logs/JacobStephens2-thirdshift-issue-24-20260925T134143Z-implement.jsonl
+
thirdshift: implement: session started
+
thirdshift: implement: $ gh issue view 24 --comments && ls && cat CONTEXT.md | head -80 && ls docs docs/adr
+
thirdshift: implement: $ gh issue view 24 --json title,body,comments,labels && ls && ls docs docs/adr 2>/dev/null; git log --…
thirdshift: implement: $ sed -i 's/ends, including by Ctrl-C, without/ends, including by Ctrl-C or a closed terminal, without…
+
thirdshift: implement: commit
+
+
+
+
3 · Y · Review
+
The same session reviews its work against the Base branch, fixes the Standards findings and Spec findings it agrees with, and lists the rest as Unaddressed findings in the pull request body. Then it opens the pull request, ready for review.
thirdshift: implement: session ended after 3m 40s: 5 turns, $1.06 at API prices
+
+
+
+
4 · K · Finish
+
thirdshift pushes, checks the pull request, merges the Base branch in and watches CI. A merge conflict or failing CI starts a Repair, at most 3. A Resume can happen in any session and isn't a Repair. The Run ends once the pull request is open, ready, mergeable and passing CI. This Run needed no Repair.
+
resolving-merge-conflicts in a Repair
+
+
thirdshift: pushing issue-24
+
thirdshift: checking the PR
+
thirdshift: merging origin/main into issue-24
+
thirdshift: pushing issue-24
+
thirdshift: waiting up to 60s for CI on f32bc95
+
thirdshift: CI on f32bc95: 1 of 1 checks still running
+
thirdshift: CI passed on f32bc95
+
thirdshift: checking the PR is open, ready and mergeable
+
thirdshift: cleaning up the worktree and local branch issue-24
+
thirdshift: PR https://github.com/JacobStephens2/thirdshift/pull/25 is ready for review
+
+
+
+
The implement: lines are the Run's session log passed through thirdshift's own progress condensing. The other lines are thirdshift's progress messages, filled in with pull request #25's branch, commit and CI result. The session's duration is rebuilt from its log file's timestamps, so thirdshift may have printed 3m 41s.