The keyboard takes Ctrl, the browser takes drags, and the arrangement is Custom Eight pages caught up with the app: every shortcut is a combination now and is recorded by pressing it; a file row can be dragged onto a folder or the other pane and carries copy, rename and delete on itself; Settings has chips and a filter, a way to empty the journal, and the pause before the Enter; the prompts window opens shut, counts what it holds, sends to several sessions at once and no longer reorders anything; Keep and Mine are one Custom control with saving inside it. Plus the turn marker in the bridge is @END, which is what the prompts have said for a while.
The turn format, the sixth status, and the other pattern Catching the page up with three changes it did not describe: turns are sentinels with the metadata inside the opening one rather than a markdown heading; ASK exists, because a review that was misread becomes a REDO for something that is not broken; and the together pattern runs on the same bridge, with the statuses that make sense between peers. Plus the question the page ought to have answered from the start — what happens when both of them write at once — and the reason each pattern is now a single prompt.
The bridge, and what Argus does and does not do The page described Argus watching two terminals and passing prompts between them. It reads a file now, like everybody else in the arrangement, and the page says what the file looks like, what the five statuses mean, why a turn has an end line, and where the idea comes from. Also: there is no "answer the review" prompt any more and the page says why — the worker is already looping on the file. And a warning worth having in writing, since it cost two invented turns: never put a runnable command at the start of a line in a prompt, because Argus types prompts into terminals and a shell will run it.
Both halves of the loop, and who goes first
Say where the review is written and where it is read The page described the pattern as it was, and as it was the two agents could not actually exchange a review: the reviewer printed into its own pane and the builder was told to read something it had no way to reach. The review is a file now, one writer and one reader, and the page says so with the ownership table that goes with it.
Two agents on one job: the patterns, the plan file, and the review loop The wiki said, in as many words, that there is deliberately no loop. There is one now — one switch, one desk, and a count of rounds — so the page that said otherwise now points at the page that explains it, and the new page says plainly what the loop will not do and why each of those refusals is there. Also brings Home into line with the landing page's opening, and adds the question to the FAQ, since that is where somebody looks before reading a feature page.