Block a user
1c38abe1d0
Fallback coverage: colour the wait, group by tier, and lock the stacks the partner already runs
5d42a28d34
Each assistant card remembers its own conversation instead of every card resuming the newest one
e5f4ede3f2
Coverage and settings above the chat, tier delays and the probe target alongside them, coverage in three columns
ce613bcf9d
Rehome the failover coverage picker on the Fallback tab, five days after it was dropped from Partnership for belonging here
8ce8f0dfbe
The Monitor fallback card described a state file without saying whether anything still writes it
13c221244e
A partner's conf is in the RAM cache, not CONF_DIR, and a commented-out template entry is not configuration
a89b704fa1
Watchdog and Monitor looked the partner up by exact key, and the remote probe passed a quote to cut as a filename
0f228020ef
State-file age is time since the last transition, not staleness, and a preview's state is the one being decided
da15cc7531
Rebuild the Fallback tab around what the daemon is actually doing, not what its last state file said
5924aae1c0
Fallback read the peer list by exact key, so a partner whose tailnet name differs by one character rendered as UNREACHABLE
f8119f3786
Give the test harness a stop that cannot strand its iptables rule, and clean up the dry-run state copy
41c0598220
A fallback dry run wrote real reboot-surviving state, and a failed tier writeback reported itself as a dry run
387382ec9f
Media Stack called every node local, and a host whose watchdogs never ran reported all clear
20998c8c31
The Streams scope was reset to this host on every page load, on a dashboard that is never reloaded by choice
f5d6edd9d0
The mirrored folder layout never reached the container card, which reads Varaverk's own store and not folder.view3's
4808a57289
Monitor's partner card read phase flags that only ever describe the mirror, so the owner rendered as not provisioned on the mirror