@@ -99,9 +99,12 @@ the selected `.py` files sequentially to the current board directory.**
 7. **One connection session owns the commit.** The action captures the stable
    `Connection` facade's opaque local session stamp with `cwd`. The stamp must
    still be current before every board preflight and immediately before each
-   `putFile`; attach or detach advances it, including reconnecting the same
-   board. A mismatch stops the batch before the next board verb. This stamp is
-   in-memory action consistency only—not identity, authentication, persisted
+   `putFile`; attach or detach advances it. The facade also advances it once
+   when an attached live connection leaves an established `ready`/`running`
+   state for `connecting` or `disconnected`, so an in-place reconnect to the
+   same board is a successor session; ordinary `ready` ↔ `running` transitions
+   retain it. A mismatch stops the batch before the next board verb. This stamp
+   is in-memory action consistency only—not identity, authentication, persisted
    provenance, or PBLE/1 wire data.
 
 8. **The commit is sequential and honestly non-atomic.** After the entire
@@ -128,6 +131,9 @@ the selected `.py` files sequentially to the current board directory.**
    no tight or unbounded automatic retry. A positive supplied retry delay gates
    every network-producing action on the surface until its deadline; local
    navigation, selection, and review transitions cannot clear or bypass it.
+   Every individual REST GET has one absolute wall-clock deadline spanning
+   request send, response headers, and the complete bounded response body;
+   arriving chunks do not extend it, and expiry aborts the request.
    Header-rejected HTTP responses have their body streams cancelled before the
    typed failure is returned so repeated failures do not strand resources.
 
 
@@ -769,7 +769,10 @@ does not follow `download_url`, HTML links, or any arbitrary URL returned in a
 response. A response rejected from headers alone (including status or declared
 body length) has its body stream cancelled before the adapter publishes the
 typed failure, so repeated hostile responses cannot strand transport resources
-(SEC-10).
+(SEC-10). Each REST GET also owns one non-extending absolute wall-clock
+deadline that starts before the request is sent and covers both headers and the
+complete bounded body. Receiving a slow trickle never extends that deadline;
+expiry asks the transport to abort and maps to the neutral offline failure.
 
 Resolution is a two-step logical operation:
 
@@ -878,6 +881,12 @@ type-changed conflict invalidates consent and returns to review. This
 conservative recheck prevents the general Import tap or stale confirmation
 from authorizing an overwrite.
 
+The stable facade rotates its opaque session stamp on attach/detach and once
+when an attached live connection leaves an established `ready`/`running`
+session for `connecting` or `disconnected`. A later in-place reconnect therefore
+uses the rotated successor stamp. Ordinary `ready` ↔ `running` transitions do
+not rotate it.
+
 ### 10.5 All-fetch validation and sequential commit
 
 `GithubBoardImporter` constructs a candidate in two phases with a hard