diff --git a/docs/screenshots/replay-663/after-misprint-1440x900.png b/docs/screenshots/replay-663/after-misprint-1440x900.png
new file mode 100644
index 00000000..8ac7a743
Binary files /dev/null and b/docs/screenshots/replay-663/after-misprint-1440x900.png differ
diff --git a/docs/screenshots/replay-663/after-press-1440x900-step-1.png b/docs/screenshots/replay-663/after-press-1440x900-step-1.png
new file mode 100644
index 00000000..4730d5ca
Binary files /dev/null and b/docs/screenshots/replay-663/after-press-1440x900-step-1.png differ
diff --git a/docs/screenshots/replay-663/after-press-1440x900-step-4.png b/docs/screenshots/replay-663/after-press-1440x900-step-4.png
new file mode 100644
index 00000000..70745ce8
Binary files /dev/null and b/docs/screenshots/replay-663/after-press-1440x900-step-4.png differ
diff --git a/docs/screenshots/replay-663/after-press-390x844-step-4.png b/docs/screenshots/replay-663/after-press-390x844-step-4.png
new file mode 100644
index 00000000..c3c59de1
Binary files /dev/null and b/docs/screenshots/replay-663/after-press-390x844-step-4.png differ
diff --git a/docs/screenshots/replay-663/after-proofs-1440x900.png b/docs/screenshots/replay-663/after-proofs-1440x900.png
new file mode 100644
index 00000000..9c788d53
Binary files /dev/null and b/docs/screenshots/replay-663/after-proofs-1440x900.png differ
diff --git a/docs/screenshots/replay-663/before-misprint-1440x900.png b/docs/screenshots/replay-663/before-misprint-1440x900.png
new file mode 100644
index 00000000..07e11553
Binary files /dev/null and b/docs/screenshots/replay-663/before-misprint-1440x900.png differ
diff --git a/docs/screenshots/replay-663/before-press-1440x900-step-1.png b/docs/screenshots/replay-663/before-press-1440x900-step-1.png
new file mode 100644
index 00000000..9d3a7b78
Binary files /dev/null and b/docs/screenshots/replay-663/before-press-1440x900-step-1.png differ
diff --git a/docs/screenshots/replay-663/before-press-1440x900-step-4.png b/docs/screenshots/replay-663/before-press-1440x900-step-4.png
new file mode 100644
index 00000000..6ceae09a
Binary files /dev/null and b/docs/screenshots/replay-663/before-press-1440x900-step-4.png differ
diff --git a/docs/screenshots/replay-663/before-press-390x844-step-4.png b/docs/screenshots/replay-663/before-press-390x844-step-4.png
new file mode 100644
index 00000000..f7385ac6
Binary files /dev/null and b/docs/screenshots/replay-663/before-press-390x844-step-4.png differ
diff --git a/docs/screenshots/replay-663/before-proofs-1440x900.png b/docs/screenshots/replay-663/before-proofs-1440x900.png
new file mode 100644
index 00000000..d61eb60e
Binary files /dev/null and b/docs/screenshots/replay-663/before-proofs-1440x900.png differ
diff --git a/site/index.html b/site/index.html
index 0054ff4e..9c5899f8 100644
--- a/site/index.html
+++ b/site/index.html
@@ -15,12 +15,12 @@
-
+
-
+
@@ -90,7 +90,7 @@
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 in the Harness you choose. This replay is a historical example, recorded before the newer workflows below. Under each unit are the lines thirdshift printed on stderr during a real Run: issue #24, which produced pull request #25. Click a unit to see what it does. Every prompt and skill it sends is on the Prompts and skills page.
+
A Run feeds one issue through four units and delivers a pull request that is ready for review, or merged in a Merge run. Units 2 and 3 are one agent session in the Harness you choose. Under each unit are lines thirdshift printed on stderr during a real Run, overnight on 12 October 2026. A scheduled Pickup run took issue #663 at 00:21, and its Merge run merged pull request #665 at 01:22. That pull request refreshed the floor plan further down this page. Click a unit to see what it does. Every prompt and skill it sends is on the Prompts and skills page.
@@ -100,7 +100,7 @@
One issue in, one pull request out.
@@ -189,29 +189,41 @@
One issue in, one pull request out.
1 · C · Prepare
-
Pre-flight checks the Origin match, the open issue, the Base branch and the selected Harness, plus Git’s commit identity. thirdshift picks the Issue branch, fresh or a Continuation, claims the issue with in-progress, and creates a worktree next to your clone. This older replay predates Claims.
+
Pre-flight checks the Origin match, the open issue, the Base branch and the selected Harness, plus Git’s commit identity. thirdshift picks the Issue branch, fresh or a Continuation, claims the issue with in-progress, and creates a worktree next to your clone. Here a scheduled Pickup run took the issue.
-
thirdshift: creating worktree /home/jacob/repos/thirdshift-issue-24 on issue-24 from origin/main
+
thirdshift: 00:21:01 Pickup run starting, 2026-10-12 -0400
+
thirdshift: 00:21:05 taking Ready issue #663 "update https://thirdshift.app/ based on the latest which is part of thirdshift", as thirdshift https://github.com/JacobStephens2/thirdshift/issues/663 would
+
thirdshift: 00:21:05 checking the Model and Effort against codex debug models
+
thirdshift: 00:21:06 logging this command to /home/jacob/.thirdshift/logs/JacobStephens2/thirdshift/commands/pickup/663-20261012T002101-0400.log
+
thirdshift: 00:21:06 sessions run on codex · gpt-6.1-sol · high
+
thirdshift: 00:21:08 updating main in the Launch directory from origin/main
+
thirdshift: 00:21:08 labelling #663 in-progress, in place of ready-for-agent
+
thirdshift: 00:21:10 creating worktree /home/jacob/repos/thirdshift-issue-663 on issue-663 from origin/main
2 · M · Implement
-
A headless session in the selected Harness, with the Factory skills loaded, implements the issue in the worktree, test-first where it can, and commits. The recorded Run used Claude Code.
+
A headless session in the selected Harness, with the Factory skills loaded, implements the issue in the worktree, test-first where it can, and commits. The recorded Run used Codex.
thirdshift: implement: $ sed -i 's/ends, including by Ctrl-C, without/ends, including by Ctrl-C or a closed terminal, without…
-
thirdshift: implement: commit
+
thirdshift: 00:21:10 logging the session to /home/jacob/.thirdshift/logs/JacobStephens2/thirdshift/commands/pickup/663-20261012T002101-0400-implement.jsonl
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. Behavior findings need a test or command that exercises them before the agent decides. It fixes reproduced failures and keeps the test. Then it opens the pull request, ready for review.
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 5. 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. An optional Security review checks the change before Delivery. With thirdshift merge <Issue URL>, thirdshift also merges the reviewed head once its checks pass. This recorded Run needed no Repair and left its pull request for review.
+
An optional Security review checks the change first. Then 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 5. 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. A Merge run, from thirdshift merge <Issue URL> or the User config, then merges it. Here the Security review found nothing, main moved during CI and was merged in again, and no Repair was needed.
thirdshift: 00:47:13 logging the session to /home/jacob/.thirdshift/logs/JacobStephens2/thirdshift/commands/pickup/663-20261012T002101-0400-security-review.jsonl
+
thirdshift: 00:47:14 security-review: session started
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.
+
The lines are copied, timestamps and all, from the Pickup run's Command log, which keeps everything thirdshift printed. Each cut for length says how many lines it left out; there are 139 lines on stderr in all.
@@ -422,18 +455,18 @@
The factory grows
Proof sheets
Pulled from the press
Real pull requests thirdshift made on its own repository. Judge the work yourself.
Every check that runs before a Run creates anything, each with a clear message, including the Origin match.
+
From the factory's first day: a careful change to branch selection, where the agent flags a new error the issue didn't ask for, so a human can decide on it.
Does a second reviewer catch what thirdshift's own review lets through? 183 replayed reviews, Codex against a fresh Claude session: Fresh Eyes Beat a Second Family.