What
If the server replies 404 to the bridge's work poll, meaning it no longer knows this machine, the bridge now re-registers itself and resumes instead of shutting down, re-attaching every live session. It is controlled remotely by tengu_glimmering_glade, which is on when the server says nothing.
Details
- Re-registration asks to reuse the same environment id, up to 3 attempts; if the server hands back a different id, the replacement is deregistered and the bridge gives up.
- On success it adopts the new environment secret and re-queues each active session.
- Verbose output shows
Environment re-registered; resuming poll.orRe-registration failed; retrying after backoff. - New event
tengu_bridge_env_reregisterwith outcomes register_rejected, register_transient, replaced, reregistered, recovered, requeue_dropped, gave_up, plus abridge_env_reregisteredlog line.
Evidence
tengu_bridge_env_reregister
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: tengu_glimmering_glade