pub struct RemoteSeq {
pub observed_seq: u64,
pub observed_etag: Option<String>,
pub integrated_seq: u64,
pub updated_unix: u64,
pub sync_requested_unix: Option<u64>,
pub sync_requested_by: Option<String>,
pub sync_requested_at_seq: Option<u64>,
}Expand description
.flint/remote.seq — the news ticker (D5).
observed_seq > integrated_seq means “there is news you have not
integrated — consider dropping a .flint/sync at your next safe
point”. The agent polls one LOCAL file: no network, no client, no
credentials, and N agents cost zero bucket requests rather than
N×HEAD.
Fields§
§observed_seq: u64§observed_etag: Option<String>§integrated_seq: u64§updated_unix: u64Refreshed on EVERY successful HEAD tick — a local rename, zero bucket cost. Without the heartbeat an agent cannot distinguish “no news” from “syncer dead” on an idle-but-healthy workspace. Contract: older than 3×floor ⇒ syncer or proxy problem.
sync_requested_unix: Option<u64>Advisory news from the gateway (D14): a HITL/CI party asked this workspace to pull. The syncer performs NO tree mutation on receipt — it moves the ticker and stops.
sync_requested_by: Option<String>§sync_requested_at_seq: Option<u64>integrated_seq at the moment the request was carried. Once the
workspace integrates past it the request is stale and clears
itself — the agent pulled, whether or not it did so on account
of the request.