From ea870d4dbadb1ab7236d06eb1622c0e2bd8560da Mon Sep 17 00:00:00 2001 From: "@permadeath.com" Date: Thu, 3 Sep 2026 06:36:39 -0400 Subject: [PATCH] docs(claim): stop claiming the fsm core has no gate type `didbot_fsm::Gates` came back with `didbot_reconcile` as its caller; preflight's reason for being two-valued is its own, not the core's. Change-Id: Ie364e9a9cb438a0b61bf9512107b5b37ee0ee2b8 --- crates/didbot-claim/src/preflight.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/crates/didbot-claim/src/preflight.rs b/crates/didbot-claim/src/preflight.rs index 8b4cfa63..510e4cf7 100644 --- a/crates/didbot-claim/src/preflight.rs +++ b/crates/didbot-claim/src/preflight.rs @@ -41,9 +41,9 @@ //! A check here is `Passed` or `Failed`, never "not looked at yet". Every //! one of them runs to completion before this function returns, so a third //! value would describe a state that cannot exist. That is the difference -//! between a synchronous command and a background probe, and it is why the -//! `didbot-fsm` core carries no gate type: nothing left in this workspace -//! needs one. +//! between a synchronous command and a background probe: `didbot_fsm::Gates` +//! is three-valued because `didbot_reconcile` acts across ticks and needs +//! `Pending`, and nothing here does. use std::fmt; use std::net::IpAddr; -- 2.51.2