docs(remote-workrooms): date the gate removal to PR #375's merge

docs/designs/oq8-cross-machine-reattach.md

@@ -172,7 +172,7 @@ Codex (gpt-6.1-sol, cold read of the repo):
   the agent's version at the handshake it already performs. An older agent means today's per-Mac
   behaviour for that workroom: no host layout, no second-Mac restore, nothing shown to the user
   (the bootstrap pushes the new agent on the next connect and hands off to it, #231, in every
-  build since 2026-10-07).
+  build since PR #375, 2026-10-08).
 - **Lifecycle:** a remote workroom's layout lives on that workroom's own host, so deleting the
   workroom destroys the host and its layout with it. No delete request is needed in #255.
 - **Session metadata:** the workroom ID, initial title and creation order travel in the attach
@@ -277,7 +277,7 @@ Codex (gpt-6.1-sol, cold read of the repo):
 
 No new artifact. The agent ships inside the app (Mac and static Linux builds) and is pushed to a
 host on a version mismatch (#231), so a new protocol version reaches hosts through the existing
-bootstrap. The remote UI stayed behind `remoteWorkroomsPreview` in Nightly and Dev until 2026-10-07, when
+bootstrap. The remote UI stayed behind `remoteWorkroomsPreview` in Nightly and Dev until PR #375 (2026-10-08), when
 the owner removed that gate.
 
 ## Next Steps

docs/designs/remote-workrooms.md

@@ -9,11 +9,12 @@ Mode: Builder
 > **Note:** Workroom dropped Jujutsu (jj) support in #266. Passages here that describe jj
 > behaviour are a record of the design as it stood then, not of the current code.
 
-## Current Status — 2026-10-06
+## Current Status — 2026-10-08
 
-**Phase 4 is under way, and the app can now create, open and delete remote workrooms.** Since
-2026-10-07 that works in every build, stable included: the owner removed the Nightly-only gate and
-the hidden `remoteWorkroomsPreview` setting before #260's success criteria were run. At #253 it
+**Phase 4 is under way, and the app can now create, open and delete remote workrooms.** Since PR
+#375 (merged 2026-10-08) that works in every build, stable included: the owner removed the
+Nightly-only gate and the hidden `remoteWorkroomsPreview` setting before #260's success criteria
+were run. No release carries it yet; v2.1.0 predates it. At #253 it
 worked only on the container driver (the Mac's own Docker, from the `workroom-host` image). Merged
 so far: host
 descriptors in config (#249, PR #275, 2026-10-01); the credential broker service (#250, in
@@ -26,7 +27,7 @@ the agent, not a shim. Follow-ups from #253's reviews are #283 to #288; #283 (cl
 ends its session on the host) is merged (PR #306, 2026-10-03), with its own follow-ups in #293, #297
 and #304. The rest of Phase 4 is open: the second real provider, exe.dev (#259), and boxd live fork
 (#258), which is deferred to a later release and does not gate #260. #260 is the gate: it runs the
-Success Criteria on two real providers; the remote UI already left Nightly, ahead of it (2026-10-07). The
+Success Criteria on two real providers; the remote UI already left Nightly, ahead of it (PR #375, 2026-10-08). The
 first Nightly DMG with the Linux agent inside (#227) still has to be checked, and that check is part
 of #260. Each merged item has its "As built" entry under Phase 4, except #255, which is recorded as
 the answer to open question 8.
@@ -3347,7 +3348,7 @@ disagreement passes every test on either side alone while presenting as an empty
       reattach in `wr-agent attach` (the same ssh and pty, ~100 ms, local too) is the upgrade,
       and needs the stdin and resize relays re-plumbed onto a swappable stream.
     - *Gated as the local hand-off is* (`AgentHandOff.isEnabled`, Nightly and Dev): one
-      older-agent policy on both hosts. **Changed 2026-10-07:** remote hand-off is on in every
+      older-agent policy on both hosts. **Changed by PR #375 (2026-10-08):** remote hand-off is on in every
       build, stable included, when remote workrooms left Nightly; the local one stays gated. A
       remote agent runs under a supervisor with no idle exit, so without it a stable host would
       keep its first agent until the box restarts. Off, the scripts skip the hand-off and the install still
@@ -3909,7 +3910,7 @@ service milestones below so each layer can be reviewed and landed independently.
    failure. Apply the measured wakefulness policy through the far-side shim (#257: through the
    agent's own heartbeat instead). Add boxd's fast
    derivation only after the portable path passes. ~~Remote UI remains Nightly-only until the success
-   criteria pass~~ — the owner lifted that gate on 2026-10-07, ahead of #260, which now verifies
+   criteria pass~~ — the owner lifted that gate in PR #375 (2026-10-08), ahead of #260, which now verifies
    the criteria after the fact; the container fixture alone does not establish parity across two
    real providers.
    **Filed 2026-09-27** as #249 (host descriptors; built 2026-10-01, PR #275), #250 (broker service;