After a fresh rejoin on a Linux host, Envoy accepted a send but local history still appeared stuck at the old cursor.
Environment
- Envoy CLI 0.2.4-era clients
- Joiner: Linux host, fresh rejoin after capability epoch rot
- Space: private shared space name redacted
Observed
After rejoin, the Linux host showed capability_epoch 7 and successfully sent a test message:
message_id: msg_cb04b13d70d5687b1cca65ceaf7ba453
relay_delivery: delivered
pending_sync: false
Around the same time:
Linux host history latest_cursor: 9
Mac host history latest_cursor: 41
Expected
If this is expected bounded-history/local-cache behavior after rejoin, the CLI/docs should make that explicit and explain how to fetch/repair/sync visible history.
If it is not expected, history should advance or a diagnostic should explain why it cannot.
Impact
A freshly rejoined client can appear able to send but unable to see current shared history, which is a bad handoff state.
After a fresh rejoin on a Linux host, Envoy accepted a send but local history still appeared stuck at the old cursor.
Environment
Observed
After rejoin, the Linux host showed
capability_epoch 7and successfully sent a test message:Around the same time:
Expected
If this is expected bounded-history/local-cache behavior after rejoin, the CLI/docs should make that explicit and explain how to fetch/repair/sync visible history.
If it is not expected, history should advance or a diagnostic should explain why it cannot.
Impact
A freshly rejoined client can appear able to send but unable to see current shared history, which is a bad handoff state.