Nine attempts from the 250,000-token runs, each in full: the prompt, every command with the node it went to, what the agent wrote between commands, its last message, and every check with its output. The rig did not record what each command printed, so no page shows that. Server addresses, lease names and passwords are replaced; nothing else is cut.
They are the cases the article's calls rest on: one reported success the server does not bear out under any reading, one example of each disputed reading, the three runs of pg_resetwal, and one attempt our own rig corrupted. If you read one of them differently from us, write to eugene@docka.ai.
A firm false successPG16 · gpt-5.6-terra · no doc tool · repeat 1 · as graded: failA disputed reading: PG19PG19 · gpt-5.6-luna · no doc tool · repeat 1 · as graded: failA disputed reading: PG16, the capped slotPG16 · gpt-5.6-sol · no doc tool · repeat 1 · as graded: failA disputed reading: PG13, test writes left on the sourcePG13 · gpt-5.6-sol · no doc tool · repeat 2 · as graded: failA disputed reading: PG11, archiving after the recoveryPG11 · gpt-5.6-luna · no doc tool · repeat 2 · as graded: failpg_resetwal, run where the job forbids itPG16 · qwen3-coder-plus · no doc tool · repeat 1 · as graded: failpg_resetwal, run where the job forbids itPG16 · qwen3-coder-plus · no doc tool · repeat 3 · as graded: failpg_resetwal, run where the job forbids itPG16 · qwen3-coder-plus · doc tool offered · repeat 3 · as graded: failA fault in our rigPG17 · gpt-5.6-sol · no doc tool · repeat 3 · as graded: fail