@serfab/cadre-core 1.5.0 → 1.6.0

package/src/relay-reservation.ts

@@ -143,12 +143,12 @@ export interface RelayReservationState {
 /**
  * How long {@link driveRelayReservation} waits for a reservation to appear, at the DEFAULT
  * declared link round trip: `RELAY_RESERVATION_ROUND_TRIPS` (4) x `DECLARED_LINK_ROUND_TRIP_MS`
- * (2000 ms) = 8000 ms, where it was a fixed 10_000 before.
+ * (3500 ms) = 14 000 ms, where it was a fixed 10_000 before it was derived.
  *
  * Counted rather than chosen because this one deadline bounds the whole drive — dial the relay,
  * request the reservation, wait — and each of those costs a fixed number of exchanges, not a
  * fixed number of milliseconds. `link-budget.ts` carries the counts, the measurement behind
- * them, and the ceiling above which no relayed connection can be established whatever this says.
+ * them, and what still fails at the supported link whatever this says.
  *
  * A host on a slower link moves it by declaring `NetworkConfig.linkRoundTripMs`, which both
  * call sites thread in (`CadreNode.reserveRelays` for the control node,

package/src/seed-bootstrap.ts

@@ -811,7 +811,7 @@ export class SeedBootstrapService {
     // (`dialPeerAddrs`), so an owner whose first address never answers neither
     // stalls seed application nor goes undialed at its other addresses.
     // NOTE: `handleSeedStream` acks only after this loop, so an unreachable owner
-    // can hold the ack for up to `dialBudget.totalMs` each — 32 s at the default declared link
+    // can hold the ack for up to `dialBudget.totalMs` each — 56 s at the default declared link
     // round trip, more on a host that declared a slower one (`link-budget.ts`) — past a sender's
     // 10 s `seedDeliverTimeoutMs`; the seed is still applied. If senders start
     // reporting accepted seeds as timed out, ack before dialing.